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
Query, being inspired from JQ, allows the program to be
applied on one or more input document, where document can be
any json encoded value (or encoded in json equivalent format).
While this is useful to process JSON value in sed and awk like fashion, it has some serious short-comings
when used in SQL fashion.
Key, big data systems are predominanty based on {key,value}
document storage as its primary storage. To that extent we need
to include key as part of the query-program.
Metadata, at big data scale, documents are predominantly
distributed. This along with features like, append only values,
create-modify-read timestamps, uuid, document versioning etc..
adds one or more metadata fields to the actual document-value.
The solution we are proposing is:
To keep metadata separate from actual document value.
To include both document and metadata as inputs to query program.
Right now query programs can access the document value using . (dot) syntax, here after we can allow query programs to use # (hash)
syntax to access the documents metadata.
Key can be made available via metadata, like #_key.
While document (.) can be any JSON value, metadata is always
a set of {key,value} pairs, where Key is of string-type and value
can be any valid JSON value.
The text was updated successfully, but these errors were encountered:
prataprc
changed the title
query: enhance query syntax to include metadata as part of the language.
query: syntax to include metadata as part of the language.
Aug 6, 2018
prataprc
changed the title
query: syntax to include metadata as part of the language.
query: syntax to include metadata as part of the program.
Aug 6, 2018
Query, being inspired from JQ, allows the program to be
applied on one or more input document, where document can be
any json encoded value (or encoded in json equivalent format).
While this is useful to process JSON value in sed and
awk like fashion, it has some serious short-comings
when used in SQL fashion.
Key, big data systems are predominanty based on {key,value}
document storage as its primary storage. To that extent we need
to include key as part of the query-program.
Metadata, at big data scale, documents are predominantly
distributed. This along with features like, append only values,
create-modify-read timestamps, uuid, document versioning etc..
adds one or more metadata fields to the actual document-value.
The solution we are proposing is:
. (dot) syntax, here after we can allow query programs to use # (hash)
syntax to access the documents metadata.
a set of {key,value} pairs, where Key is of string-type and value
can be any valid JSON value.
The text was updated successfully, but these errors were encountered: