Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[BUG] Lookup command throw AMBIGUOUS_REFERENCE exception when lookupMappingField is duplicated in source side and lookup table #1078

Open
LantaoJin opened this issue Mar 4, 2025 · 1 comment
Open

[BUG] Lookup command throw AMBIGUOUS_REFERENCE exception when lookupMappingField is duplicated in source side and lookup table #1078

LantaoJin opened this issue Mar 4, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@LantaoJin
Copy link
Member

LantaoJin commented Mar 4, 2025 •
edited
Loading

What is the bug?
Assuming the tableA contains fields id, uid, a_name and the tableB contains id, b_name. PPL

source = tableA | lookup tableB id as uid replace b_name as a_name

will failed with [AMBIGUOUS_REFERENCE] Reference id is ambiguous
@LantaoJin LantaoJin added bug Something isn't working untriaged and removed untriaged labels Mar 4, 2025
@LantaoJin
Copy link
Member Author

LantaoJin commented Mar 4, 2025 •
edited
Loading

The current workaround could be

source = tableA | rename id as a_id | lookup tableB id as uid replace b_name as a_name | rename a_id as id

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@LantaoJin