-
Notifications
You must be signed in to change notification settings - Fork 265
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
Drop quotes for UDF metadata #1010
Comments
Hi can I take this up? |
Sure! |
Hi regarding this issue. I went through files in the parser as well as the final statement_binder evadb/binder/statement_binder.py . I see that predict right now is being added in UDF metadata
My question is whether I need to move PREDICT to a predicate or let it be in the metadata |
Hi Hersh, the |
Hi came across this line in the lark file Line 38 in 94e17a9
Where udf_metadata is described as
I don't think changing the
I am thinking I need to create a different expression for this and not define PREDICT and TIME_LIMIT as string literals. Can you give me a few pointers here @xzdandy |
I saw in your pr you have used |
No no, I just wanted to link the issue to the PR. That's it. Making it a UID solves the problem |
Replacing udf_metadata_key from string_literal to ID_LITERAL ` modified: evadb/parser/evadb.lark` Removed .value from key_value_pair[0] post the change in type ` modified: evadb/parser/lark_visitor/_functions.py` Replaced string key to ID_LITERAL in test query ` modified: test/unit_tests/parser/test_parser.py` Solves #1010 --------- Co-authored-by: xzdandy <[email protected]>
Closed as #1026 has been merged into staging |
Replacing udf_metadata_key from string_literal to ID_LITERAL ` modified: evadb/parser/evadb.lark` Removed .value from key_value_pair[0] post the change in type ` modified: evadb/parser/lark_visitor/_functions.py` Replaced string key to ID_LITERAL in test query ` modified: test/unit_tests/parser/test_parser.py` Solves #1010 --------- Co-authored-by: xzdandy <[email protected]>
Search before asking
Description
Instead of currently
We'd like to move to
Use case
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: