mirror of
https://github.com/ClickHouse/ClickHouse.git
synced 2024-11-19 14:11:58 +00:00
8623cb232c
* CLICKHOUSE-4063: less manual html @ index.md * CLICKHOUSE-4063: recommend markdown="1" in README.md * CLICKHOUSE-4003: manually purge custom.css for now * CLICKHOUSE-4064: expand <details> before any print (including to pdf) * CLICKHOUSE-3927: rearrange interfaces/formats.md a bit * CLICKHOUSE-3306: add few http headers * Remove copy-paste introduced in #3392 * Hopefully better chinese fonts #3392 * get rid of tabs @ custom.css * Apply comments and patch from #3384 * Add jdbc.md to ToC and some translation, though it still looks badly incomplete * minor punctuation * Add some backlinks to official website from mirrors that just blindly take markdown sources * Do not make fonts extra light * find . -name '*.md' -type f | xargs -I{} perl -pi -e 's//g' {} * find . -name '*.md' -type f | xargs -I{} perl -pi -e 's/ sql/g' {} * Remove outdated stuff from roadmap.md * Not so light font on front page too * Refactor Chinese formats.md to match recent changes in other languages
60 lines
2.4 KiB
Markdown
60 lines
2.4 KiB
Markdown
# Functions for working with JSON
|
|
|
|
In Yandex.Metrica, JSON is transmitted by users as session parameters. There are some special functions for working with this JSON. (Although in most of the cases, the JSONs are additionally pre-processed, and the resulting values are put in separate columns in their processed format.) All these functions are based on strong assumptions about what the JSON can be, but they try to do as little as possible to get the job done.
|
|
|
|
The following assumptions are made:
|
|
|
|
1. The field name (function argument) must be a constant.
|
|
2. The field name is somehow canonically encoded in JSON. For example: `visitParamHas('{"abc":"def"}', 'abc') = 1`, but `visitParamHas('{"\\u0061\\u0062\\u0063":"def"}', 'abc') = 0`
|
|
3. Fields are searched for on any nesting level, indiscriminately. If there are multiple matching fields, the first occurrence is used.
|
|
4. The JSON doesn't have space characters outside of string literals.
|
|
|
|
## visitParamHas(params, name)
|
|
|
|
Checks whether there is a field with the 'name' name.
|
|
|
|
## visitParamExtractUInt(params, name)
|
|
|
|
Parses UInt64 from the value of the field named 'name'. If this is a string field, it tries to parse a number from the beginning of the string. If the field doesn't exist, or it exists but doesn't contain a number, it returns 0.
|
|
|
|
## visitParamExtractInt(params, name)
|
|
|
|
The same as for Int64.
|
|
|
|
## visitParamExtractFloat(params, name)
|
|
|
|
The same as for Float64.
|
|
|
|
## visitParamExtractBool(params, name)
|
|
|
|
Parses a true/false value. The result is UInt8.
|
|
|
|
## visitParamExtractRaw(params, name)
|
|
|
|
Returns the value of a field, including separators.
|
|
|
|
Examples:
|
|
|
|
```
|
|
visitParamExtractRaw('{"abc":"\\n\\u0000"}', 'abc') = '"\\n\\u0000"'
|
|
visitParamExtractRaw('{"abc":{"def":[1,2,3]}}', 'abc') = '{"def":[1,2,3]}'
|
|
```
|
|
|
|
## visitParamExtractString(params, name)
|
|
|
|
Parses the string in double quotes. The value is unescaped. If unescaping failed, it returns an empty string.
|
|
|
|
Examples:
|
|
|
|
```
|
|
visitParamExtractString('{"abc":"\\n\\u0000"}', 'abc') = '\n\0'
|
|
visitParamExtractString('{"abc":"\\u263a"}', 'abc') = '☺'
|
|
visitParamExtractString('{"abc":"\\u263"}', 'abc') = ''
|
|
visitParamExtractString('{"abc":"hello}', 'abc') = ''
|
|
```
|
|
|
|
There is currently no support for code points in the format `\uXXXX\uYYYY` that are not from the basic multilingual plane (they are converted to CESU-8 instead of UTF-8).
|
|
|
|
|
|
[Original article](https://clickhouse.yandex/docs/en/query_language/functions/json_functions/) <!--hide-->
|