ClickHouse/docs/en/formats/jsoneachrow.rst

JSONEachRow
-----------

If put in SELECT query, displays data in newline delimited JSON (JSON objects separated by \\n character) format.
If put in INSERT query, expects this kind of data as input.

.. code-block:: text

  {"SearchPhrase":"","count()":"8267016"}
  {"SearchPhrase":"bathroom interior","count()":"2166"}
  {"SearchPhrase":"yandex","count()":"1655"}
  {"SearchPhrase":"spring 2014 fashion","count()":"1549"}
  {"SearchPhrase":"free-form photo","count()":"1480"}
  {"SearchPhrase":"Angelina Jolie","count()":"1245"}
  {"SearchPhrase":"omsk","count()":"1112"}
  {"SearchPhrase":"photos of dog breeds","count()":"1091"}
  {"SearchPhrase":"curtain design","count()":"1064"}
  {"SearchPhrase":"baku","count()":"1000"}

Unlike JSON format, there are no replacements of invalid UTF-8 sequences. There can be arbitrary amount of bytes in a line.
This is done in order to avoid data loss during formatting. Values are displayed analogous to JSON format.

In INSERT queries JSON data can be supplied with arbitrary order of columns (JSON key-value pairs). It is also possible to omit values in which case the default value of the column is inserted. N.B. when using JSONEachRow format, complex default values are not supported, so when omitting a column its value will be zeros or empty string depending on its type.

Space characters between JSON objects are skipped. Between objects there can be a comma which is ignored. Newline character is not a mandatory separator for objects.
Initial commit if EN docs 2017-04-03 19:49:50 +00:00			`JSONEachRow`
			`-----------`

Formats 2017-04-26 18:02:30 +00:00			`If put in SELECT query, displays data in newline delimited JSON (JSON objects separated by \\n character) format.`
			`If put in INSERT query, expects this kind of data as input.`
CLICKHOUSE-2720: progress on website (#865) * update presentations * CLICKHOUSE-2936: redirect from clickhouse.yandex.ru and clickhouse.yandex.com * update submodule * lost files * CLICKHOUSE-2981: prefer sphinx docs over original reference * CLICKHOUSE-2981: docs styles more similar to main website + add flags to switch language links * update presentations * Less confusing directory structure (docs -> doc/reference/) * Minify sphinx docs too * Website release script: fail fast + pass docker hash on deploy * Do not underline links in docs * shorter * cleanup docker images * tune nginx config * CLICKHOUSE-3043: get rid of habrastorage links * Lost translation * CLICKHOUSE-2936: temporary client-side redirect * behaves weird in test * put redirect back * CLICKHOUSE-3047: copy docs txts to public too * move to proper file * remove old pages to avoid confusion * Remove reference redirect warning for now * Refresh README.md * Yellow buttons in docs * Use svg flags instead of unicode ones in docs * fix test website instance * Put flags to separate files * wrong flag * Copy Yandex.Metrica introduction from main page to docs * Yet another home page structure change, couple new blocks (CLICKHOUSE-3045) * Update Contacts section * CLICKHOUSE-2849: more detailed legal information * CLICKHOUSE-2978 preparation - split by files * More changes in Contacts block * Tune texts on index page * update presentations * One more benchmark * Add usage sections to index page, adapted from slides * Get the roadmap started, based on slides from last ClickHouse Meetup * CLICKHOUSE-2977: some rendering tuning * Get rid of excessive section in the end of getting started * Make headers linkable * CLICKHOUSE-2981: links to editing reference - https://github.com/yandex/ClickHouse/issues/849 * CLICKHOUSE-2981: fix mobile styles in docs * Ban crawling of duplicating docs * Open some external links in new tab * Ban old docs too * Lots of trivial fixes in english docs * Lots of trivial fixes in russian docs * Remove getting started copies in markdown * Add Yandex.Webmaster * Fix some sphinx warnings * More warnings fixed in english docs * More sphinx warnings fixed * Add code-block:: text * More code-block:: text * These headers look not that well * Better switch between documentation languages * merge use_case.rst into ya_metrika_task.rst * Edit the agg_functions.rst texts * Add lost empty lines 2017-06-13 04:15:47 +00:00
			`.. code-block:: text`

Initial commit if EN docs 2017-04-03 19:49:50 +00:00			`{"SearchPhrase":"","count()":"8267016"}`
Formats 2017-04-26 18:02:30 +00:00			`{"SearchPhrase":"bathroom interior","count()":"2166"}`
			`{"SearchPhrase":"yandex","count()":"1655"}`
			`{"SearchPhrase":"spring 2014 fashion","count()":"1549"}`
			`{"SearchPhrase":"free-form photo","count()":"1480"}`
			`{"SearchPhrase":"Angelina Jolie","count()":"1245"}`
			`{"SearchPhrase":"omsk","count()":"1112"}`
			`{"SearchPhrase":"photos of dog breeds","count()":"1091"}`
			`{"SearchPhrase":"curtain design","count()":"1064"}`
			`{"SearchPhrase":"baku","count()":"1000"}`
Initial commit if EN docs 2017-04-03 19:49:50 +00:00
Formats 2017-04-26 18:02:30 +00:00			`Unlike JSON format, there are no replacements of invalid UTF-8 sequences. There can be arbitrary amount of bytes in a line.`
			`This is done in order to avoid data loss during formatting. Values are displayed analogous to JSON format.`
Initial commit if EN docs 2017-04-03 19:49:50 +00:00
Formats 2017-04-26 18:02:30 +00:00			`In INSERT queries JSON data can be supplied with arbitrary order of columns (JSON key-value pairs). It is also possible to omit values in which case the default value of the column is inserted. N.B. when using JSONEachRow format, complex default values are not supported, so when omitting a column its value will be zeros or empty string depending on its type.`

			`Space characters between JSON objects are skipped. Between objects there can be a comma which is ignored. Newline character is not a mandatory separator for objects.`