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

No cluster name filtering when sniffing is not enabled #637

Closed
ppearcy opened this issue Jan 19, 2011 · 1 comment
Closed

No cluster name filtering when sniffing is not enabled #637

ppearcy opened this issue Jan 19, 2011 · 1 comment
Labels
>bug v0.15.0

Comments

@ppearcy
Copy link
Contributor

ppearcy commented Jan 19, 2011

The cluster name is no longer honored via the TransportClient unless sniffing is enable don 0.14.2. See this discussion for more details:
http://elasticsearch-users.115913.n3.nabble.com/0-14-2-TransportClient-does-not-appear-to-be-honoring-cluster-name-tp2289073p2289073.html

Thanks!
@kimchy
Copy link
Member

kimchy commented Jan 20, 2011

No cluster name filtering when sniffing is not enabled, closed by 545d8f3.

tallpsmith pushed a commit to tallpsmith/elasticsearch that referenced this issue May 5, 2011
@kimchy
No cluster name filtering when sniffing is not enabled, closes elasti…
545d8f3 
…c#637.
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
@salvatore-campagna
feature: include the nyc_taxis aggs challenge to nightly benchmarks (e…
46f9fa7 
…lastic#634) (elastic#637)

Both the noaa and nyc_taxis tracks include new plots. Here we update
dashboard ids for nightly benchmarks.
emilykmarx pushed a commit to emilykmarx/elasticsearch that referenced this issue Dec 26, 2023
@andrewvc
Fix error in instantiating bad response code exceptions
5b1e53d 
Fixes elastic#637
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
>bug v0.15.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kimchy @ppearcy