mustafasrepo opened a new pull request, #7755: URL: https://github.com/apache/arrow-datafusion/pull/7755
## 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 [#7154](https://github.com/apache/arrow-datafusion/issues/7154). Thanks @parkma99 for the initial work in [#7161](https://github.com/apache/arrow-datafusion/pull/7161) ## Rationale for this change With the changes in this PR, we can use use primary key information in the external tables also. <!-- 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? <!-- 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? Yes new tests are added to show that, primary key information is used during planning. With these changes query below can run ```sql SELECT c, b, SUM(d) FROM multiple_ordered_table2 GROUP BY c; ``` even if column `b` is not among the group by expressions, when it is known that column `c` is primary key. In this case we are sure that, for each unique `c` value, there will be corresponding `b` value (`b` is functionally dependent on the `c`). Hence, above query can run successfully. <!-- 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 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]
