-
Notifications
You must be signed in to change notification settings - Fork 33
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
Fix ppl describe bug #612 #656
Fix ppl describe bug #612 #656
Conversation
…es schema.catalog.table Signed-off-by: YANGDB <[email protected]>
…es schema.catalog.table Signed-off-by: YANGDB <[email protected]>
* fix describe ppl command to be aware of 3 parts FQN table that includes schema.catalog.table Signed-off-by: YANGDB <[email protected]> * fix describe ppl command to be aware of 3 parts FQN table that includes schema.catalog.table Signed-off-by: YANGDB <[email protected]> --------- Signed-off-by: YANGDB <[email protected]> (cherry picked from commit 0be5697) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
The backport to
To backport manually, run these commands in your terminal: # Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/opensearch-spark/backport-0.5-nexus 0.5-nexus
# Navigate to the new working tree
pushd ../.worktrees/opensearch-spark/backport-0.5-nexus
# Create a new branch
git switch --create backport/backport-656-to-0.5-nexus
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 0be56974238ef2f7d88f21fed4ce4fd40681d756
# Push it to GitHub
git push --set-upstream origin backport/backport-656-to-0.5-nexus
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/opensearch-spark/backport-0.5-nexus Then, create a pull request where the |
@@ -132,6 +132,11 @@ public LogicalPlan visitRelation(Relation node, CatalystPlanContext context) { | |||
identifier = new TableIdentifier( | |||
node.getTableQualifiedName().getParts().get(1), | |||
Option$.MODULE$.apply(node.getTableQualifiedName().getParts().get(0))); | |||
} else if (node.getTableQualifiedName().getParts().size() == 3) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems the assumption here is relation names cannot contain .
. But unfortunately, index name can contain .
, ref https://opensearch.org/docs/latest/api-reference/index-apis/create-index/
* fix describe ppl command to be aware of 3 parts FQN table that includes schema.catalog.table * fix describe ppl command to be aware of 3 parts FQN table that includes schema.catalog.table --------- (cherry picked from commit 0be5697) Signed-off-by: YANGDB <[email protected]> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Description
fix describe ppl command to be aware of 3 parts FQN table that includes
schema.catalog.table
Issues Resolved
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.