PartiQL: One query language for all your data
aws.amazon.com
PartiQL: One query language for all your data
1–10 of 88 posts
Re: PartiQL: One query language for all your data
#2That is the most important thing for my uses. I deal mostly in time series data, SQL windowing queries are too slow. Turning the set into an array to allow indexing and support easy time series queries is enough for me the use it.
Re: PartiQL: One query language for all your data
#3 PartiQL> SELECT * FROM [1,2,3]
|
==='
>
---
OK! (86 ms)
Jeez. 86ms for this query on this data set? Hope that's not representative of the general performance!Re: PartiQL: One query language for all your data
#4PartiQL> SELECT * FROM [1,2,3] | ===' > --- OK! (86 ms) Jeez. 86ms for this query on this data set? Hope that's not representative of the general performance!
Re: PartiQL: One query language for all your data
#5Re: PartiQL: One query language for all your data
#6Re: PartiQL: One query language for all your data
#7Re: PartiQL: One query language for all your data
#8I wonder how this deals with nested parquet data, and whether it's able to optimise on the things parquet provides.
Here is an example of integrating PartiQL with CSV files. https://github.com/partiql/partiql-lang-kotlin/blob/master/e.... Integrating with Parquet would of course be more complex then that.
Re: PartiQL: One query language for all your data
#9Anyone know how this compares to Presto and zetasql?
ZetaSQL is a custom SQL dialect, along with parser and analyzer, that Google uses for products like BigQuery and Spanner.
PartiQL is a new query language extended from SQL to work with various non-relational data sources and schemaless data formats in a more natural and idiomatic way.
Re: PartiQL: One query language for all your data
#10Interesting that they opted for a relational rather than a categorical one; the latter is proving to be more flexible [0]. [0] https://www.categoricaldata.net/