-
Notifications
You must be signed in to change notification settings - Fork 176
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
Improve coverage of tests for array expressions #1269
Comments
We should also start testing with all supported data types for the array expressions. |
Here is an example of an issue that we should have been able to catch using fuzz testing: |
Would it help to extend makeParquetFileAllTypes or create a new method which creates a parquet file that contains more complex structures like lists (with all datatypes and structs because the current tests usually test the implementation with arrays only containing 1-3 elements) and structs to improve the tests with additional test cases? However I think that requires complex type support for the comet native parquet reader. |
Yes, exactly. I have started down this path in #1308 As you said, until we have complex type support we cannot generate Parquet files containing complex types. For now I had to work around this by generating a Parquet file with primitive types and then use the Complex type support for Parquet is coming very soon though. I did try disabling native Parquet scans and use the |
What is the problem the feature request solves?
I would like to start implementing some shared test code for array expressions to make it easier to test for edge cases such as null or empty arrays.
The following functions need improved tests:
Describe the potential solution
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: