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

HPCC-33155 Revisit Parquet Test Suite #19405

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

jackdelv
Copy link
Contributor

Change the plugin to throw an error if a file is not found when opening a file for reading

Change output filename of partitioned file parts. part_00_0.parquet -> part_0_of_table_0_from_worker_0.parquet
These files aren't meant to be read directly, but I think the new format makes more sense when trying to debug.

Update tests so that they are all being run and are able to use external files in testing/regress/download

Remove parquetString test and key file and move testing to parquetTypes.ecl

Update test cases in parquetTypes.ecl

Type of change:

  • This change is a bug fix (non-breaking change which fixes an issue).
  • This change is a new feature (non-breaking change which adds functionality).
  • This change improves the code (refactor or other change that does not change the functionality)
  • This change fixes warnings (the fix does not alter the functionality or the generated code)
  • This change is a breaking change (fix or feature that will cause existing behavior to change).
  • This change alters the query API (existing queries will have to be recompiled)

Checklist:

  • My code follows the code style of this project.
    • My code does not create any new warnings from compiler, build system, or lint.
  • The commit message is properly formatted and free of typos.
    • The commit message title makes sense in a changelog, by itself.
    • The commit is signed.
  • My change requires a change to the documentation.
    • I have updated the documentation accordingly, or...
    • I have created a JIRA ticket to update the documentation.
    • Any new interfaces or exported functions are appropriately commented.
  • I have read the CONTRIBUTORS document.
  • The change has been fully tested:
    • I have added tests to cover my changes.
    • All new and existing tests passed.
    • I have checked that this change does not introduce memory leaks.
    • I have used Valgrind or similar tools to check for potential issues.
  • I have given due consideration to all of the following potential concerns:
    • Scalability
    • Performance
    • Security
    • Thread-safety
    • Cloud-compatibility
    • Premature optimization
    • Existing deployed queries will not be broken
    • This change fixes the problem, not just the symptom
    • The target branch of this pull request is appropriate for such a change.
  • There are no similar instances of the same problem that should be addressed
    • I have addressed them here
    • I have raised JIRA issues to address them separately
  • This is a user interface / front-end modification
    • I have tested my changes in multiple modern browsers
    • The component(s) render as expected

Smoketest:

  • Send notifications about my Pull Request position in Smoketest queue.
  • Test my draft Pull Request.

Testing:

@jackdelv jackdelv requested a review from dcamper January 13, 2025 15:39
Copy link

Jira Issue: https://hpccsystems.atlassian.net//browse/HPCC-33155

Jirabot Action Result:
Workflow Transition To: Merge Pending
Updated PR

Copy link
Contributor

@dcamper dcamper left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just one question about the contents of a comment block.

* ├── district=1
* │ ├── firstname=Alice
* │ │ └── city=New%20York
* │ │ └── part_0_of_table_0_from_worker_0.parquet
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These part... names are files? If so, they are all the same for every value combination. Is that correct?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, that is correct.

@dcamper dcamper self-requested a review January 13, 2025 16:01
Copy link
Contributor

@dcamper dcamper left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

Copy link
Member

@ghalliday ghalliday left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See comments/questions.

DATASET([{0, 'Corrupt Parquet File', ''}], RECORDDEF),
CORRUPT_PARQUET);

OUTPUT(CORRUPT_RESULT);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Without the output this workunit will not do anything.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed.

@@ -31,6 +36,3 @@ EMPTY_PARQUET := DATASET([], RECORDDEF);
ParquetIO.Write(EMPTY_PARQUET, filePath, TRUE);

read_data := ParquetIO.Read(RECORDDEF, filePath);

OUTPUT(read_data);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With this deleted it will not read the file.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed.

- createDirectoryIterator is used to list all matching Parquet files and the order is not guarenteed
- Fix parquetEmpty.ecl and parquetCorrupt.ecl by adding the OUTPUT statements back
@jackdelv jackdelv requested review from ghalliday and dcamper January 15, 2025 19:01
Copy link
Contributor

@dcamper dcamper left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved.

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

Successfully merging this pull request may close these issues.

3 participants