JSON Format conditionally shows number values as strings about clickhouse HOT 2 CLOSED

In ClickHouse, when using JSON* family formats, numbers larger than Int32 are represented as strings, as Int64+ types maximum values are larger than Number.MAX_SAFE_INTEGER. This is to avoid integer overflow as max values for these types are bigger than Number.MAX_SAFE_INTEGER. However, this behavior can be modified with output_format_json_quote_64bit_integers setting.

Here is an example of how to adjust the JSON output format for 64-bit numbers:

const resultSet = await client.query({  
 query: 'SELECT * from system.numbers LIMIT 1',  
 format: 'JSONEachRow',  
})  
  
expect(await resultSet.json()).toEqual([ { number: '0' } ])  

const resultSet = await client.query({  
 query: 'SELECT * from system.numbers LIMIT 1',  
 format: 'JSONEachRow',  
 clickhouse_settings: { output_format_json_quote_64bit_integers: 0 },  
})  
  
expect(await resultSet.json()).toEqual([ { number: 0 } ])  

In the first query, the number is returned as a string, while in the second query, with the output_format_json_quote_64bit_integers setting set to 0, the number is returned as a number.

However, it's important to note that there are some known limitations when using ClickHouse with Node.js/Web. For instance, when using JSON* family formats, numbers larger than Int32 are represented as strings, as Int64+ types maximum values are larger than Number.MAX_SAFE_INTEGER.

For more details, you can refer to the following documentation:

• Integral types: Int64, Int128, Int256, UInt64, UInt128, UInt256
• Known limitations (Node.js/Web)

from clickhouse.

Thanks for the thorough explanation! Apologies for missing this in the docs as well.

from clickhouse.