Interesting 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/
How is it proving to be more flexible?
PartiQL: One query language for all your data
21–30 of 88 posts
Re: PartiQL: One query language for all your data
#22Re: PartiQL: One query language for all your data
#23Will this be integrated into AWS Athena? The blog post doesn't mention it.
Re: PartiQL: One query language for all your data
#24So I assume this is a rebranding of some other open source project with the amazon brand stuck on it, or is it actually something distinct?
Re: PartiQL: One query language for all your data
#25Anyone know how this compares to Presto and zetasql?
One big difference is native support for nested data that's built right into the syntax of the language. Most other SQL implementations allow support for nested data through functions which have non-intuitive syntax.
We generally build views to unnest the arrays, maps, and structs and query from them (or build other tables from the views in hive) but something like this is certainly a bit easier
Re: PartiQL: One query language for all your data
#26PartiQL> 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!
Other queries involving joins, aggregates, unrolls, and pivots on schemaless, nested, multi-path documents performed way better than the example cherry-picked from the main blog post-- Queries completing between 5ms to 25ms, albeit on toy dataset.
Re: PartiQL: One query language for all your data
#27Interesting 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/
How is it proving to be more flexible?
I'd be happy to showcase our recent progress. But let's connect offline, so as not to hijack the conversation. Feel free to drop me a line at ryan@conexus.ai.
Re: PartiQL: One query language for all your data
#28This is neat. Anyone want to add support for TreeBase/Tree Notation? http://treenotation.org/treeBase/ . It's currently on the backburner to query TreeBases in SQL without having first to convert the TreeBase to sql. Seems like it would be relatively straightforward to use this to do that.
Most of your recent comments link to your project's website. Please stop with the abusive promotion.
Re: PartiQL: One query language for all your data
#29PartiQL> 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!
You missed the point. The modern infrastructure's primary value is scalability. This number is of course bad, for the data. But this number will be more impressive when the data is million time bigger.
Re: PartiQL: One query language for all your data
#30So I assume this is a rebranding of some other open source project with the amazon brand stuck on it, or is it actually something distinct?
[deleted]