-
Notifications
You must be signed in to change notification settings - Fork 101
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
IGNITE-24033 Sql schema. Extend Compute API with supporting qualified names #5102
base: main
Are you sure you want to change the base?
Conversation
@@ -215,9 +216,11 @@ private <T, R> CompletableFuture<SubmitResult> submit0(JobTarget target, JobDesc | |||
var mapper = (Mapper<? super Object>) colocatedTarget.keyMapper(); | |||
|
|||
if (mapper != null) { | |||
return doExecuteColocatedAsync(colocatedTarget.tableName(), colocatedTarget.key(), mapper, descriptor, arg); | |||
// need to be fixed after: https://issues.apache.org/jira/browse/IGNITE-24301 Fix Thin client protocol to use schema name | |||
return doExecuteColocatedAsync(quoteIfNeeded(colocatedTarget.tableName()), colocatedTarget.key(), mapper, descriptor, arg); |
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.
can`t use "quote" here cause this method processed recursively and appends additional quotation in such a case
this.key = key; | ||
this.keyMapper = keyMapper; | ||
} | ||
|
||
public String tableName() { | ||
return tableName; | ||
return name.objectName(); |
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.
Here schema name is lost, so can't be used in embedded Compute API.
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.
fixed, refactored
Thank you for submitting the pull request.
To streamline the review process of the patch and ensure better code quality
we ask both an author and a reviewer to verify the following:
The Review Checklist
- There is a single JIRA ticket related to the pull request.
- The web-link to the pull request is attached to the JIRA ticket.
- The JIRA ticket has the Patch Available state.
- The description of the JIRA ticket explains WHAT was made, WHY and HOW.
- The pull request title is treated as the final commit message. The following pattern must be used: IGNITE-XXXX Change summary where XXXX - number of JIRA issue.
Notes