PLUGIN-1833: fix: Use unique aliases in MERGE statements to avoid conflicts with column names #274
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use unique aliases in MERGE statements to avoid conflicts with column names
Jira : PLUGIN-1833
Description
This update resolves an issue where the MERGE operation was failing if the user's table contained columns A, B, or D. The failure occurred because these column names were being used as table aliases in the code, causing conflicts.
Code change
BigQueryEventConsumer.java
Tested
(Same configurations used in both cases)
Before changes:
After changes: