Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

SQL Query with Different Mappings #445

Closed
KentonParton opened this issue Apr 28, 2020 · 2 comments · Fixed by #470
Closed

SQL Query with Different Mappings #445

KentonParton opened this issue Apr 28, 2020 · 2 comments · Fixed by #470
Assignees
@penghuo
Labels
bug Something isn't working duplicate This issue or pull request already exists

Comments

@KentonParton
Copy link

When performing a SQL select query such as SELECT callId FROM txn-* LIMIT 50 the following “Invalid SQL Query” is received: “Different mappings are not allowed for the same field[msg]…”.

My question is, shouldn’t only the selected fields mappings be compared?

When the above query is executed, I would expect the mapping for “callId” across all indices matching “txn-" to be compared; however, it appears that all field mappings are being compared that match "txn-”.

Would it be possible to only compare mapping types for the selected field/s?
@abbashus
Copy link
Contributor

Similar issue as #348. Don't have an ETA on this, but plan to prioritize this fix soon.

@zhongnansu zhongnansu added the duplicate This issue or pull request already exists label Apr 29, 2020
@penghuo penghuo self-assigned this Apr 30, 2020
@penghuo penghuo added the bug Something isn't working label Apr 30, 2020
@yangjiajun2014
Copy link

I am facing same issue too.Hope u can fix soon.Thanks a lot.

@penghuo penghuo mentioned this issue May 15, 2020
Merged
@chloe-zh chloe-zh linked a pull request May 15, 2020 that will close this issue
Enhancement, add the field type conflict check in semantic check #470
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@penghuo penghuo

Labels
bug Something isn't working duplicate This issue or pull request already exists
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Enhancement, add the field type conflict check in semantic check penghuo/sql
5 participants
@penghuo @yangjiajun2014 @KentonParton @zhongnansu @abbashus