Skip to content
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

Nullity Error When Querying MAX On Non-Numeric Column #14459

Open
ashishjayamohan opened this issue Nov 14, 2024 · 3 comments
Open

Nullity Error When Querying MAX On Non-Numeric Column #14459

ashishjayamohan opened this issue Nov 14, 2024 · 3 comments

Comments

@ashishjayamohan
Copy link
Contributor

ashishjayamohan commented Nov 14, 2024

When querying the MAX of a column, we use NonScanBasedAggregationOperator to use the stored metadata. This produces a nullity error on non-numeric columns as these columns do not have a stored max value. Ideally, this should produce a more informative error that states this aforementioned reason.
Screenshot 2024-11-14 at 2 50 11 PM

@ashishjayamohan ashishjayamohan changed the title NPE When Querying MAX On Non-Numeric Column Nullity Error When Querying MAX On Non-Numeric Column Nov 14, 2024
@Jackie-Jiang
Copy link
Contributor

Hmm, it is actually a NumberFormatException which is expected because MAX only works on numbers as of now

@ashishjayamohan
Copy link
Contributor Author

Correct, I updated to not be NPE. I think it would be better to state this error more informatively (rather than "null," state type)

@Jackie-Jiang
Copy link
Contributor

"null" is the actual string value, which cannot be parsed as number

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants