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

Populate indexName for BatchQuery #2956

Merged
merged 3 commits into from
Sep 6, 2024

Conversation

ykmr1224
Copy link
Collaborator

Description

  • Populate indexName for BatchQuery
  • Create Index query with manual refresh now executed as Batch query, but batch query didn't populate indexName in AsyncQueryJobMetadata.

Related Issues

n/a

Check List

  • New functionality includes testing.
  • New functionality has been documented.
  • New functionality has javadoc added.
  • New functionality has a user manual doc added.
  • API changes companion pull request created.
  • Commits are signed per the DCO using --signoff.
  • Public documentation issue/PR created.

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.

Signed-off-by: Tomoyuki Morita <[email protected]>
@ykmr1224 ykmr1224 marked this pull request as ready for review August 30, 2024 21:31
@ykmr1224 ykmr1224 added bug Something isn't working maintenance Improves code quality, but not the product labels Sep 3, 2024
@vamsi-amazon
Copy link
Member

How are we executing create manual indices earlier?

@@ -106,6 +106,13 @@ public DispatchQueryResponse submit(
.resultIndex(dataSourceMetadata.getResultIndex())
.datasourceName(dataSourceMetadata.getName())
.jobType(JobType.INTERACTIVE)
.indexName(getIndexName(context))
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As mentioned below, we can't have name in all kinds of flint index queries? What is the indexName used for?

Copy link
Collaborator Author

@ykmr1224 ykmr1224 Sep 4, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

DQS uses index name to populate their database to find the query where the index is created. For other query, it would become null, and that should be fine.

@ykmr1224
Copy link
Collaborator Author

ykmr1224 commented Sep 4, 2024

How are we executing create manual indices earlier?

It used to be handled by interactive job. It did not populate indexName as well.

seankao-az
seankao-az previously approved these changes Sep 4, 2024
Copy link
Collaborator

@seankao-az seankao-az left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Signed-off-by: Tomoyuki Morita <[email protected]>
@ykmr1224 ykmr1224 merged commit b76aa65 into opensearch-project:main Sep 6, 2024
13 of 14 checks passed
opensearch-trigger-bot bot pushed a commit that referenced this pull request Sep 6, 2024
* Populate indexName for BatchQuery

Signed-off-by: Tomoyuki Morita <[email protected]>

* Fix test failure due to rebase

Signed-off-by: Tomoyuki Morita <[email protected]>

---------

Signed-off-by: Tomoyuki Morita <[email protected]>
Signed-off-by: Tomoyuki MORITA <[email protected]>
(cherry picked from commit b76aa65)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
ykmr1224 pushed a commit that referenced this pull request Sep 9, 2024
* Populate indexName for BatchQuery



* Fix test failure due to rebase



---------



(cherry picked from commit b76aa65)

Signed-off-by: Tomoyuki Morita <[email protected]>
Signed-off-by: Tomoyuki MORITA <[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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport 2.x bug Something isn't working maintenance Improves code quality, but not the product
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants