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.

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

[Coral-Hive] Create new object for ShiftArrayIndexTransformer #494

Merged

Conversation

ljfgem
Copy link
Collaborator

@ljfgem ljfgem commented Mar 1, 2024

What changes are proposed in this pull request, and why are they necessary?

Prior to this PR, ShiftArrayIndexTransformer modifies the index of the SqlCall directly, which might transform the same object multiple times if it appears multiple times in SqlNode and generate the wrong index. This PR fixes this issue by creating new object for ShiftArrayIndexTransformer.

How was this patch tested?

  1. Tested on the affected prod view, worked as expected
  2. Regression test on all prod views, no regression
  3. Note: I couldn't reproduce the issue by UT somehow, still investigating the reason. If it still can't be reproduced by UT locally after spending much time, the PR can be merged and we can make UT as a follow-up work.

@wmoustafa
Copy link
Contributor

Could you add a test that fails when this patch is not applied?

@ljfgem
Copy link
Collaborator Author

ljfgem commented Mar 4, 2024

Could you add a test that fails when this patch is not applied?

@wmoustafa As I mentioned in the description, I couldn't reproduce the issue by UT somehow, still investigating the reason. I have added a TODO item in the comment, can merge it first if it's urgent to unblock the release.

@ljfgem ljfgem merged commit 44f4f58 into linkedin:li-trino-hotfix Mar 4, 2024
1 check passed
KevinGe00 pushed a commit to KevinGe00/coral that referenced this pull request Mar 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants