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

[DOC] No documentation present on how to use rescore using Opensearch #8163

Open
1 of 4 tasks
navneet1v opened this issue Sep 3, 2024 · 1 comment
Open
1 of 4 tasks
Assignees
Labels
1 - Backlog - DEV Developer assigned to issue is responsible for creating PR. Sev3 Medium priority. Content that's missing, driven by dev, PM or the community.

Comments

@navneet1v
Copy link
Contributor

What do you want to do?

  • Request a change to existing documentation
  • Add new documentation
  • Report a technical problem with the documentation
  • Other

Tell us about your request. Provide a summary of the request.
Opensearch since the fork supports doing rescore of the results using rescore queries. But in the current documentation there is no documentation present for doing the rescore. Creating this GH issue so that rescore docs can be added in Opensearch documentation.

Refer below example:

POST my-index/_search
{
   "query" : {
      "match" : {
         "message" : {
            "operator" : "and",
            "query" : "Opensearch supports rescore"
         }
      }
   },
   "rescore" : {
      "window_size" : 50,
      "query" : {
         "rescore_query" : {
            "match_phrase" : {
               "message" : {
                  "query" : "rescore",
                  "slop" : 2
               }
            }
         },
         "query_weight" : 0.7,
         "rescore_query_weight" : 1.2
      }
   }
}

*Version: List the OpenSearch version to which this issue applies, e.g. 2.14, 2.12--2.14, or all.
all

What other resources are available? Provide links to related issues, POCs, steps for testing, etc.

@Naarcha-AWS Naarcha-AWS added 1 - Backlog - DEV Developer assigned to issue is responsible for creating PR. and removed untriaged labels Sep 5, 2024
@Naarcha-AWS Naarcha-AWS added the Sev3 Medium priority. Content that's missing, driven by dev, PM or the community. label Sep 5, 2024
@Naarcha-AWS Naarcha-AWS self-assigned this Sep 5, 2024
@navneet1v
Copy link
Contributor Author

navneet1v commented Sep 5, 2024

@Naarcha-AWS any reason for assigning this to me, as I don't own this feature? 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 - Backlog - DEV Developer assigned to issue is responsible for creating PR. Sev3 Medium priority. Content that's missing, driven by dev, PM or the community.
Projects
None yet
Development

No branches or pull requests

2 participants