Improve UDF Experience: Clearer Error Messages, New Pandas Column Definitions, and Enforce Input Column Arguments #1426
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
NewPandasDataFrame & PandasColumn
I created a new PandasDataFrame class aimed at replacing the original one.The new class abstracts away the different column definitions (shape, type, name, etc.) into single column objects instead of multiple arguments:
See: https://github.com/georgia-tech-db/evadb/compare/staging...Jjx003:functions?expand=1#diff-f096e708655c43345f3edfb4fdea7cf27e27ab8f29fe3d09d8223537247f85a6R96
New Error Messages for improper decorators:
See: https://github.com/georgia-tech-db/evadb/compare/staging...Jjx003:functions?expand=1#diff-1e9fbe4cbda64173cb3dd304d324d51f0245dd5d38c4fade971cb7eff8d7d862R49
Enforce PandasColumn Input_Signature
I also made it so that before evaluating a function, EVA first checks whether or not the input_signature columns are present in the input data. If not, an error is raised.
See: https://github.com/georgia-tech-db/evadb/compare/staging...Jjx003:functions?expand=1#diff-72d3ebebc4aa466ca53857a7827fb01f786d3725161c7826ad4df100966e9c69R134