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.

Sign up for GitHub

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

Jump to bottom

[CI] "vectors/20_dense_vector_special_cases/Documents missing a vector field" Failed #47743

Closed
Tim-Brooks opened this issue Oct 8, 2019 · 1 comment · Fixed by #49175
Closed

[CI] "vectors/20_dense_vector_special_cases/Documents missing a vector field" Failed #47743

Tim-Brooks opened this issue Oct 8, 2019 · 1 comment · Fixed by #49175
Assignees
@mayya-sharipova
Labels
:Search/Search Search-related issues that do not fall into other categories >test-failure Triaged test failures from CI

Comments

@Tim-Brooks
Copy link
Contributor

org.elasticsearch.xpack.test.rest.XPackRestIT.test {p0=vectors/20_dense_vector_special_cases/Documents missing a vector field} failed in:

Error was:

expected [400] status code but api [search] returned [200 OK]

It looks to me that the problem is that one of the shards indicated "success" on the search which prevented the expected 400 status code from being returned?

Reproduce (it does not):

/gradlew ':x-pack:plugin:integTestRunner' --tests "org.elasticsearch.xpack.test.rest.XPackRestIT.test {p0=vectors/20_dense_vector_special_cases/Documents missing a vector field}" -Dtests.seed=27C3B4D74327974E -Dtests.security.manager=true -Dtests.locale=es-GQ -Dtests.timezone=Africa/Sao_Tome -Dcompiler.java=12 -Druntime.java=11 -Dtests.rest.blacklist="getting_started/10_monitor_cluster_health/*"
@Tim-Brooks Tim-Brooks added :Search/Search Search-related issues that do not fall into other categories >test-failure Triaged test failures from CI labels Oct 8, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-search (:Search/Search)

@mayya-sharipova mayya-sharipova self-assigned this Oct 28, 2019
mayya-sharipova added a commit to mayya-sharipova/elasticsearch that referenced this issue Nov 15, 2019
@mayya-sharipova
Add index name to search requests
8f3db81 
We can't guarantee expected request failures if search request is across
many indexes, as if expected shards fail, some indexes may return 200.

closes elastic#47743
@mayya-sharipova mayya-sharipova mentioned this issue Nov 15, 2019
Merged
mayya-sharipova added a commit that referenced this issue Nov 15, 2019
@mayya-sharipova
Add index name to search requests (#49175)
730faa8 
We can't guarantee expected request failures if search request is across
many indexes, as if expected shards fail, some indexes may return 200.

closes #47743
mayya-sharipova added a commit that referenced this issue Nov 15, 2019
@mayya-sharipova
Add index name to search requests (#49175)
0e933a0 
We can't guarantee expected request failures if search request is across
many indexes, as if expected shards fail, some indexes may return 200.

closes #47743
mayya-sharipova added a commit that referenced this issue Nov 15, 2019
@mayya-sharipova
Add index name to search requests (#49175)
d5290f1 
We can't guarantee expected request failures if search request is across
many indexes, as if expected shards fail, some indexes may return 200.

closes #47743
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mayya-sharipova mayya-sharipova

Labels
:Search/Search Search-related issues that do not fall into other categories >test-failure Triaged test failures from CI
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add index name to search requests mayya-sharipova/elasticsearch
3 participants
@Tim-Brooks @mayya-sharipova @elasticmachine