You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As mentioned in apache/datafusion#7845 (comment), I was greatly inspired by JSONA and proposed a JSONA variant(Maybe we can call it JSONC, JSON for columnar storage formats😙) that may benefit from the high compression rates of columnar storage formats. BTW, If we decide to implement our own JSON storage implementation, It's definitely an excellent opportunity to evaluate various storage implementations of JSON in the OLAP scenario.
A naive proposal of JSONA variant.
For JSON [false, 10, {"k":"v"}, null] can be stored as the following struct.
The Struct data can be efficiently encoded into compact files using the underlying file format. In our scenario, we use the Parquet as the underlying file format. For instance, the Nodes field can be represented as UINT8 and efficiently encoded using default dictionary encoding.
What problem does the new feature solve?
Supports inserting/querying JSON data.
What does the feature do?
Support for JSON data format will be divided into several stages:
Implementation challenges
See also:
The text was updated successfully, but these errors were encountered: