-
Notifications
You must be signed in to change notification settings - Fork 191
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
[BUG] "Misspelling" on setting maxAnalyzedOffset from Highlight.Builder #553
Comments
schmittjoaopedro
added a commit
to schmittjoaopedro/opensearch-java
that referenced
this issue
Jul 5, 2023
… name to match with the one introduced in OpenSearch 2.2.0 Signed-off-by: Joao Pedro Schmitt <[email protected]>
schmittjoaopedro
added a commit
to schmittjoaopedro/opensearch-java
that referenced
this issue
Jul 5, 2023
… name to match with the one introduced in OpenSearch 2.2.0 Signed-off-by: Joao Schmitt <[email protected]>
schmittjoaopedro
added a commit
to schmittjoaopedro/opensearch-java
that referenced
this issue
Jul 5, 2023
… name to match with the one introduced in OpenSearch 2.2.0 Signed-off-by: Joao Schmitt <[email protected]>
schmittjoaopedro
added a commit
to schmittjoaopedro/opensearch-java
that referenced
this issue
Jul 5, 2023
… name to match with the one introduced in OpenSearch 2.2.0 Signed-off-by: Joao Schmitt <[email protected]>
schmittjoaopedro
added a commit
to schmittjoaopedro/opensearch-java
that referenced
this issue
Jul 5, 2023
… name to match with the one introduced in OpenSearch 2.2.0 Signed-off-by: Joao Schmitt <[email protected]>
schmittjoaopedro
added a commit
to schmittjoaopedro/opensearch-java
that referenced
this issue
Jul 5, 2023
… name to match with the one introduced in OpenSearch 2.2.0 Signed-off-by: Joao Schmitt <[email protected]>
schmittjoaopedro
added a commit
to schmittjoaopedro/opensearch-java
that referenced
this issue
Jul 5, 2023
… name to match with the one introduced in OpenSearch 2.2.0 Signed-off-by: Joao Schmitt <[email protected]>
reta
pushed a commit
that referenced
this issue
Jul 5, 2023
…h the one introduced in OpenSearch 2.2.0 (#557) Signed-off-by: Joao Schmitt <[email protected]>
@schmittjoaopedro You can use SNAPSHOT here: An example maven config:
|
Thanks |
Thank you |
Closed
9 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the bug?
We have a "misspelling" on the maxAnalyzedOffset setting from
Highlight.Builder
. hereWhen we set the
maxAnalyzedOffset
in theHighlight.Builder
the setting that is added on the json ismax_analyzed_offset
(looks right but it's not), when we execute this query we get the following error:The
max_analyzed_offset
setting is from ElasticSearch, on OpenSearch the correct setting ismax_analyzer_offset
.How can one reproduce the bug?
What is the expected behavior?
Update the api to match the OpenSearch Highlight setting
max_analyzer_offset
What is your host/environment?
Amazon OpenSearch service 2.5 managed by AWS.
Do you have any additional context?
StackTrace:
The text was updated successfully, but these errors were encountered: