(PartiQL team member)
AWS Redshift Spectrum supports PartiQL on parquet since last year. Except that the language had not had a name yet and was referred to as "SQL extensions for nested data.
(I'm a member of the PartiQL team.)
The language spec source will be open-sourced, as well, early next week (week of Aug 5).
As I said above, to @ahl:
Overall, we look forward to a community effort and participants that are interested in making significant investments to achieve the project's goals. We invite diverse opinions and viewpoints.
As PartiQL grows towards a diverse community, we expect to add maintainers (for code and spec) that have non-Amazon affiliations and explore more formalized methods of governance.
(I'm part of the PartiQL effort.)
You are right about the challenge you point out and we are realistic about it. Thus this line in the charter:
{{{
While the adopting query engines generally may not support all features of PartiQL, a database engine that “supports PartiQL” is expected to be consistent with the PartiQL specification in the syntax subset it supports.
}}}
hi @ahl,
I'm a member of PartiQL's steering committee and glad to see your interest to participate in PartiQL's evolution.
The language spec source will be open-sourced, as well, early next week (week of Aug 5).
Overall, we look forward to a community effort and participants that are interested in making significant investments to achieve the project's goals. Diverse opinions and viewpoints, both on the language and on the process, are very welcome.
At this point, the maintainers/committee is only Amazon members. As PartiQL grows towards a diverse community, we expect to add maintainers/committee (for code and spec) that have non-Amazon affiliations and explore more formalized methods of governance,as they will emerge from our community discussions.