Skip to content

Expose ReadPlan and ReadPlanBuilder#8399

Merged
mbrobbel merged 1 commit intoapache:mainfrom
yeya24:expose-read-plan
Sep 23, 2025
Merged

Expose ReadPlan and ReadPlanBuilder#8399
mbrobbel merged 1 commit intoapache:mainfrom
yeya24:expose-read-plan

Conversation

@yeya24
Copy link
Copy Markdown
Contributor

@yeya24 yeya24 commented Sep 21, 2025

Which issue does this PR close?

We generally require a GitHub issue to be filed for all bug fixes and enhancements and this helps us generate change logs for our releases. You can link an issue to this PR using the GitHub syntax.

Rationale for this change

Why are you proposing this change? If this is already explained clearly in the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand your changes and offer better suggestions for fixes.

What changes are included in this PR?

Expose relevant structs and methods for ReadPlan and ReadPlanBuilder which can be used to build customized reader.

Are these changes tested?

We typically require tests for all PRs in order to:

  1. Prevent the code from being accidentally broken by subsequent changes
  2. Serve as another way to document the expected behavior of the code

If tests are not included in your PR, please explain why (for example, are they covered by existing tests)?

Are there any user-facing changes?

Yes. Now ReadPlanBuilder, ReadPlan and relevant methods are exposed.

Signed-off-by: Ben Ye <benye@amazon.com>
@github-actions github-actions Bot added the parquet Changes to the parquet crate label Sep 21, 2025
Copy link
Copy Markdown
Contributor

@alamb alamb left a comment

Choose a reason for hiding this comment

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

@alamb alamb added this to the 57.0.0 milestone Sep 22, 2025
@mbrobbel mbrobbel merged commit cdd15b8 into apache:main Sep 23, 2025
16 checks passed
@mbrobbel
Copy link
Copy Markdown
Member

Thanks @yeya24

mbrobbel pushed a commit that referenced this pull request Sep 24, 2025
# Which issue does this PR close?

We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases.
You can link an issue to this PR using the GitHub syntax.

- Closes #NNN.

# Rationale for this change

Follow up with #8399. I forgot to
expose `ReadPlan` and `ReadPlanBuilder` via mod so they still cannot be
accessed publicly

# What changes are included in this PR?

There is no need to duplicate the description in the issue here but it
is sometimes worth providing a summary of the individual changes in this
PR.

# Are these changes tested?

We typically require tests for all PRs in order to:
1. Prevent the code from being accidentally broken by subsequent changes
2. Serve as another way to document the expected behavior of the code

If tests are not included in your PR, please explain why (for example,
are they covered by existing tests)?

# Are there any user-facing changes?

If there are user-facing changes then we may require documentation to be
updated before approving the PR.

If there are any breaking changes to public APIs, please call them out.

Signed-off-by: Ben Ye <benye@amazon.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

parquet Changes to the parquet crate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Parquet] Expose ReadPlan and ReadPlanBuilder

3 participants