Uh oh!
There was an error while loading. Please reload this page.
ARROW-11723: [Rust][DataFusion] Change SQL parser to use PostgreSQL dialect - #9541
ARROW-11723: [Rust][DataFusion] Change SQL parser to use PostgreSQL dialect#9541Dandandan wants to merge 1 commit into
Conversation
Thanks for opening a pull request! Could you open an issue for this pull request on JIRA? Then could you also rename pull request title in the following format? See also: |
andygrove
left a comment
There was a problem hiding this comment.
It would be worth updating the README or other documentation as well
alamb
commented
Apr 19, 2021
The Apache Arrow Rust community is moving the Rust implementation into its own dedicated github repositories arrow-rs and arrow-datafusion. It is likely we will not merge this PR into this repository Please see the mailing-list thread for more details We expect the process to take a few days and will follow up with a migration plan for the in-flight PRs. |
alamb
commented
May 3, 2021
#10096 has removed the arrow implementation from this repository (it now resides in https://github.com/apache/arrow-rs and https://github.com/apache/arrow-datafusion) in the hopes of streamlining the development process Please re-target this PR (let us know if you need help doing so) to one/both of the new repositories. Thank you for understanding and helping to make arrow-rs and datafusion better |
As suggested by @andygrove we should use the PostgreSQL dialect now (by default), now that we decided o be PostgreSQL-compatible.
Currently this makes the
VarProviderfail (introduced here: #8135), which depends on identifiers starting with@, and which is not supported in PostgreSQL. I am wondering if we should remove this feature or make it work in another way?