Skip to content

GH-112 Harden variant decoding: example data - #113

Open
steveloughran wants to merge 6 commits into
apache:masterfrom
steveloughran:pr/variant-hardening
Open

GH-112 Harden variant decoding: example data#113
steveloughran wants to merge 6 commits into
apache:masterfrom
steveloughran:pr/variant-hardening

Conversation

@steveloughran

@steveloughran steveloughran commented May 19, 2026

Copy link
Copy Markdown

Add parquet files with malformed variant data.

This is generated from the tests of apache/parquet-java#3562 when configured to not delete output during test runs

Test files are added to parquet-format project with commentary.
@steveloughran
steveloughran force-pushed the pr/variant-hardening branch from e1eff0f to 6333d3f Compare May 20, 2026 17:06
@steveloughran steveloughran changed the title GH-112 Harden variant decoding GH-112 Harden variant decoding: example data May 21, 2026
Comment thread bad_data/README.md
Robust implementations of variant decoders SHOULD reject these.

| File | Malformed Structure |
|---------------------------------------------------------------|----------------------------------------------------------------------------|

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Would be great to add the sample code that helped generate these individual cases in the README as well.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

until the relevant PR is merged, that code doesn't really exist, does it?

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Agreed but those are in the tests of the Java repo. The data/README here has a snippet of the code that was used to generate the files. I'd prefer that be here rather than link to another repo. I'm okay reusing the same code but having it here is better for users to reproduce the artifacts. If you are planning to do that after the code merges, that's great.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think it is ok not to include reproducer of malformed data -- a link to the relevant PR (or perhaps a gist) would be enough

@nssalian nssalian left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

nit: removing the GH-112 from the title and instead adding closes <link to 112> in the PR description to be consistent with other PRs

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.

4 participants