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

implement / endpoint without using cluster state #7899

Closed
kevinkluge opened this Issue Sep 26, 2014 · 0 comments

Comments

Projects
None yet
3 participants
@kevinkluge
Copy link
Member

kevinkluge commented Sep 26, 2014

The / endpoint is currently using cluster state to return its response. it may be better to get this information from the node info and/or define some new action to return this data.

@s1monw s1monw added v1.4.0 and removed v1.4.0.Beta1 labels Sep 30, 2014

uboness added a commit to uboness/elasticsearch that referenced this issue Sep 30, 2014

Changed the root rest endpoint ('/') to use cluster service
Instead of issuing a redundant cluster state request.

Closes elastic#7899

@clintongormley clintongormley removed the v1.4.0 label Sep 30, 2014

uboness added a commit that referenced this issue Sep 30, 2014

Changed the root rest endpoint ('/') to use cluster service
Instead of issuing a redundant cluster state request.

Closes #7899

uboness added a commit that referenced this issue Sep 30, 2014

Changed the root rest endpoint ('/') to use cluster service
Instead of issuing a redundant cluster state request.

Closes #7899

mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015

Changed the root rest endpoint ('/') to use cluster service
Instead of issuing a redundant cluster state request.

Closes elastic#7899
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.