Skip to content

Avoid writing empty row group in optimized parquet writer#13248

Merged
raunaqmorarka merged 1 commit intotrinodb:masterfrom
raunaqmorarka:empty-row-group
Jul 23, 2022
Merged

Avoid writing empty row group in optimized parquet writer#13248
raunaqmorarka merged 1 commit intotrinodb:masterfrom
raunaqmorarka:empty-row-group

Conversation

@raunaqmorarka
Copy link
Copy Markdown
Member

Is this change a fix, improvement, new feature, refactoring, or other?

improvement

Is this a change to the core query engine, a connector, client library, or the SPI interfaces? (be specific)

optimized parquet writer

How would you describe this change to a non-technical end user or system administrator?

Parquet file written by optimized parquet writer will not contain an extra empty row group

Documentation

(x) No documentation is needed.
( ) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.

Release notes

(x) No release notes entries required.
( ) Release notes entries required with the following suggested text:

@findepi findepi requested a review from alexjo2144 July 20, 2022 15:35
@raunaqmorarka raunaqmorarka requested a review from sopel39 July 20, 2022 16:42
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Is it possible to write a test?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

This is going to get tested via #13246 (validation fails because reader ignores empty row group and counts 1 fewer row group than what the writer wrote), that's how I noticed it.

@raunaqmorarka raunaqmorarka merged commit b60f388 into trinodb:master Jul 23, 2022
@raunaqmorarka raunaqmorarka deleted the empty-row-group branch July 23, 2022 07:44
@github-actions github-actions bot added this to the 392 milestone Jul 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

3 participants