-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rationalize/consolidate type grammar #686
Comments
There are also two in substrait-cpp.
|
This has support for types and parameterized types: There's a wrapper with slight improvements for text parsing here: |
Shouldn't we add the grammar definition to the core repo and keep the implementations in the language repos? |
Yes, this was what this ticket is trying to suggest. I'll update description make clearer. |
There are several grammars for the same thing in Substrait subprojects.
We need to rationalize these two parsers (and any others that exist) and create a single parser in the core substrait repository.
I have no idea if they agree in behavior. I believe the java one also supports parsing to the other proto type definitions that aren't used in plans today (were intended for consumers informing producers of UDF behavior).
It's reasonably for each language binding to have their own specific implementations using a common grammar but we should avoid having distinct grammars across subprojects.
The text was updated successfully, but these errors were encountered: