-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
[CCR] The stats for an unknown index return a 200 status #37021
Labels
Comments
sebelga
added
the
:Distributed Indexing/CCR
Issues around the Cross Cluster State Replication features
label
Dec 28, 2018
Pinging @elastic/es-distributed |
sebelga
changed the title
[CCR] The stats on an unknown index return a 200 status
[CCR] The stats for an unknown index return a 200 status
Dec 28, 2018
Hi,here is my question:
I try to use python to put data to es6.5.3, I found there is something different between 5.x and 6.x, When I try to put data with fixed “_id” item,I got the error msg:
[_id] is a metadata field and cannot be added inside a document
I want to fixed the id item to set the join relations parent and child.
Everyone knows the answer?
Waiting...
… 在 2018年12月28日,下午11:45,Elastic Machine ***@***.***> 写道:
Pinging @elastic/es-distributed
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@sebelga Makes sense, this should be fixed. |
martijnvg
added a commit
to martijnvg/elasticsearch
that referenced
this issue
Jan 8, 2019
non existing indices. Currently it returns an empty response with a 200 response code. Closes elastic#37021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
When we try to access the stats for a follower index that does not exist, we receive a
200
status with the following responseTo be consistent with other APIs and follow REST standards, it should return a
404
status.If we try the same with the
/_stats
API we do get the correct statusThe text was updated successfully, but these errors were encountered: