[Coral-Trino] Revert PR#434 - Do not increment substr starting index #492
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.
Previously a PR - PR#434 added a transformation in Coral-Trino to always increment the starting index for 'substr' operator by 1 based on the issue filed #433 which assumed that hive support 0 based indexing for this operator & Trino only supports 1 based indexing.
However, based on recent explorations, it seems that Trino does supports only 1 based indexing. However, hive also supports 1 based indexing and considers 0 to be 1:
Hence, PR#434 needs to be reverted. A follow up PR will modify the logic of PR#434 to only update the index when the index is 0.
What changes are proposed in this pull request, and why are they necessary?
How was this patch tested?
./gradlew build