jfahne opened a new pull request, #16082:
URL: https://github.com/apache/datafusion/pull/16082
## 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 #16017
## 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.
-->
The dataframe `describe` method serves as a tidier way to produce standard
summary statistics about a dataset via the dataframe API. The abstraction hides
an implicit normalization of column names performed by calls made to `col` from
within the method's definition. @johnkerl flagged that use of datasets with
non-normal column names (i.e. using uppercase or periods in the name) causes
unexpected failures. The method is leaking its implementation and the fix
provided properly seals it by escaping identifiers passed to `col`.
## 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.
-->
Calls to `col` in the `describe` method of dataframes to calculate summary
statistics are passed the escape-quoted identifier via a `format!` macro.
## 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, a test was added to the file: `datafusion/core/dataframe/tests/mod.rs`
## 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, the change ensures the dataframe API behaves as expected when using the
dataframe API.
<!--
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
