nseekhao opened a new pull request, #6135:
URL: https://github.com/apache/arrow-datafusion/pull/6135

   # 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 #.
   This is a patch on top of 
PR#[6059](https://github.com/apache/arrow-datafusion/pull/6059).
   
   # 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 PR#[6059](https://github.com/apache/arrow-datafusion/pull/6059) fixed 
duplicate schema error. However, after inspecting the generated plans, it 
turned out that since we use table/col name from DF to translate to Substrait's 
field index, the producer has no way of distinguishing between the same column 
name from `left` and `right` if the table name is also the same.
   
   # What changes are included in this PR?
   
   To fix the problem described, instead of constructing the join condition as 
one big expression then parse it, each side gets parsed separately so the 
producer can keep track of field index offset (based on number of columns from 
`left`) when it tries to parse the `right` part of the join condition.
   
   # Are these changes tested?
   
   Yes.
   
   <!--
   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?
   
   No
   <!--
   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]

Reply via email to