tz70s opened a new pull request, #6202:
URL: https://github.com/apache/arrow-datafusion/pull/6202
# 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. For example `Closes #123`
indicates that this PR will close issue #123.
-->
Closes #6194.
# 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.
-->
Implemented `Display` trait for `FileScanConfig` to be consistently applied
in all Exec plan block formatting process.
Only added those in-used fields.
Highlight:
* Add an extra materialization cost of `project` method while calling
`fmt_as` without introducing cyclic dependency, should be manageable as explain
is not critical.
* The fields are fixed (`file_groups`, `projection`, `limit`,
`output_ordering`) to make the output deterministic and consistent, e.g.
previously we print `limit=None`, keep this behaviour. The drawback of this
approach is each time we add a new field (even not appearing in plan) will make
massive change on test output, but even we omit the field many not fully solve
the problem for extending fields.
# 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.
-->
Implemented `Display` trait for `FileScanConfig` to be consistently applied
in all Exec plan block formatting process.
# 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)?
-->
Yes
# Are there any user-facing changes?
<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->
Yes (explain output)
<!--
If there are any breaking changes to public APIs, please add the `api
change` label.
-->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
