You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@arrow.apache.org by GitBox <gi...@apache.org> on 2022/03/04 15:32:55 UTC

[GitHub] [arrow-datafusion] jonmmease commented on pull request #1925: Towards fixing ambiguous reference error in filter plan

jonmmease commented on pull request #1925:
URL: https://github.com/apache/arrow-datafusion/pull/1925#issuecomment-1059266283


   unsurprisingly, this change causes a failure in the `execution::context::tests::unprojected_filter` test.
   
   I'm not sure what the correct behavior here is.  Should the projected schema take precedence to resolve ambiguity and then fall back to the combined schema if a column reference is not found?


-- 
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: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org