You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@arrow.apache.org by "alamb (via GitHub)" <gi...@apache.org> on 2023/07/19 11:25:24 UTC

[GitHub] [arrow-datafusion] alamb opened a new issue, #7027: Error on Join: Schema error: Schema contains duplicate unqualified field name

alamb opened a new issue, #7027:
URL: https://github.com/apache/arrow-datafusion/issues/7027

   ### Describe the bug
   
   When trying to join two relations that have a column with the same name, we see an error
   
   > Schema error: Schema contains duplicate unqualified field name cron_job_name
   
   ### To Reproduce
   
   ```
   DataFusion CLI v27.0.0
   ❯ SELECT *
   FROM (
   VALUES ('catan-prod1-daily', 'success')
   ) as jobs(cron_job_name, status)
   JOIN (
   VALUES ('catan-prod1-daily', 'high')
   ) as severity(cron_job_name, level) ON (severity.cron_job_name =
   jobs.cron_job_name);
   Schema error: Schema contains duplicate unqualified field name cron_job_name
   ❯
   ```
   
   ### Expected behavior
   
   Query should run
   
   
   ### Additional context
   
   _No response_


-- 
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.apache.org

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

[GitHub] [arrow-datafusion] alamb commented on issue #7027: Error on Join: Schema error: Schema contains duplicate unqualified field name

Posted by "alamb (via GitHub)" <gi...@apache.org>.
alamb commented on issue #7027:
URL: https://github.com/apache/arrow-datafusion/issues/7027#issuecomment-1664391960

   > @alamb Should this fix be applied to the customer's cluster environment or will it be applied sometime in the future? 
   
   I will answer this elsewhere via DM to you
   
   
   > Also should the query work if the customer used the INNER JOIN instead of just JOIN?
   
   I do not think this will make a difference -- `INNER JOIN` and `JOIN` are synonyms. 


-- 
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

[GitHub] [arrow-datafusion] alamb closed issue #7027: Error on Join: Schema error: Schema contains duplicate unqualified field name

Posted by "alamb (via GitHub)" <gi...@apache.org>.
alamb closed issue #7027: Error on Join: Schema error: Schema contains duplicate unqualified field name 
URL: https://github.com/apache/arrow-datafusion/issues/7027


-- 
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

[GitHub] [arrow-datafusion] dburton-influxdata commented on issue #7027: Error on Join: Schema error: Schema contains duplicate unqualified field name

Posted by "dburton-influxdata (via GitHub)" <gi...@apache.org>.
dburton-influxdata commented on issue #7027:
URL: https://github.com/apache/arrow-datafusion/issues/7027#issuecomment-1664365115

   @alamb Should this fix be applied to the customer's cluster environment or will it be applied sometime in the future? Also should the query work if the customer used the INNER JOIN instead of just JOIN? 


-- 
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