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

Add workloads for vector radial search #309

Merged
merged 5 commits into from
Aug 2, 2024

Conversation

junqiu-lei
Copy link
Member

Description

Add workloads for vector radial search support

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.

Comment on lines +12 to 21
{% if query_k is defined %}
"k": {{ query_k }},
{% endif %}
{% if query_max_distance is defined %}
"max_distance": {{ query_max_distance }},
{% endif %}
{% if query_min_score is defined %}
"min_score": {{ query_min_score }},
{% endif %}
"field" : "{{ target_field_name | default('target_field') }}",
Copy link
Member

Choose a reason for hiding this comment

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

what if none of them is defined or both is defined?

Copy link
Member Author

Choose a reason for hiding this comment

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

Not sure if we can have the logic check in here, but we can add in OSB params validation process

Copy link
Member

Choose a reason for hiding this comment

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

Let's call this out in README param section

Copy link
Collaborator

Choose a reason for hiding this comment

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

@junqiu-lei Please add this call out to the README

Copy link
Member Author

Choose a reason for hiding this comment

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

updated doc

@VijayanB
Copy link
Member

Do we have plan to support as corpus?

@junqiu-lei
Copy link
Member Author

Do we have plan to support as corpus?

Not yet, we can consider the support based on this workflow if needed

Signed-off-by: Junqiu Lei <[email protected]>
@junqiu-lei
Copy link
Member Author

@IanHoang @VijayanB

Verified CI test by https://github.com/junqiu-lei/opensearch-benchmark/actions/runs/10115991636/job/27979552454?pr=1, all tests passed except:

============= 1 failed, 18 passed, 1 warning in 578.14s (0:09:38) ==============
Error:  Cannot execute-test. Error in load generator [0]
	Cannot run task [multi_term_agg]: Request returned an error. Error type: transport, Description: parsing_exception ({'error': {'root_cause': [{'type': 'parsing_exception', 'reason': 'Unknown aggregation type [multi_terms] did you mean [rare_terms]?', 'line': 1, 'col': 135}], 'type': 'parsing_exception', 'reason': 'Unknown aggregation type [multi_terms] did you mean [rare_terms]?', 'line': 1, 'col': 135, 'caused_by': {'type': 'named_object_not_found_exception', 'reason': '[1:135] unknown field [multi_terms]'}}, 'status': 400})

I think it's know issue also occurred in @finnroblin 's test and opensearch-project/opensearch-benchmark#364 (comment)

@IanHoang
Copy link
Collaborator

IanHoang commented Aug 2, 2024

https://github.com/junqiu-lei/opensearch-benchmark/actions/runs/10115991636/job/27979552454?pr=1

Unknown aggregation type [multi_terms] did you mean [rare_terms]?

Issue is because multi_terms does not exist in earlier versions of OpenSearch that integ tests use. We can disregard for now.

@IanHoang IanHoang added backport 2 Backport to the "2" branch backport 3 Backport to the "3" branch labels Aug 2, 2024
@IanHoang IanHoang merged commit cf77622 into opensearch-project:main Aug 2, 2024
4 checks passed
opensearch-trigger-bot bot pushed a commit that referenced this pull request Aug 2, 2024
* Add workloads for vector radial search

Signed-off-by: Junqiu Lei <[email protected]>

* Add script to generate dataset for radial search

Signed-off-by: Junqiu Lei <[email protected]>

* Resolve feedback

Signed-off-by: Junqiu Lei <[email protected]>

* Move script to _tools folder

Signed-off-by: Junqiu Lei <[email protected]>

* update README.md

Signed-off-by: Junqiu Lei <[email protected]>

---------

Signed-off-by: Junqiu Lei <[email protected]>
(cherry picked from commit cf77622)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
@opensearch-trigger-bot
Copy link

The backport to 3 failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-3 3
# Navigate to the new working tree
pushd ../.worktrees/backport-3
# Create a new branch
git switch --create backport/backport-309-to-3
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 cf77622de87b6c0326fc83d758009af99d97923a
# Push it to GitHub
git push --set-upstream origin backport/backport-309-to-3
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-3

Then, create a pull request where the base branch is 3 and the compare/head branch is backport/backport-309-to-3.

gkamat pushed a commit that referenced this pull request Aug 12, 2024
* Add workloads for vector radial search



* Add script to generate dataset for radial search



* Resolve feedback



* Move script to _tools folder



* update README.md



---------


(cherry picked from commit cf77622)

Signed-off-by: Junqiu Lei <[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 Backport to the "2" branch backport 3 Backport to the "3" branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants