[minor] field query syntax appears to no longer work in ES 1.0.1

Elastic Stack Elasticsearch
1

just a heads-up for folks who've upgraded to 1.0.x from 0.9x (as did I). It
appears - and I could be wrong - that field queryhttp://www.elasticsearch.org/guide/en/elasticsearch/reference/0.90/query-dsl-field-query.htmlsyntax no longer works (while equivalent query_string query still does).
Has field query been deprecated?

this works for me:

{
"query": {
"query_string": {
"default_field": "name",
"query" : "foo"
}
}
}

this produces error:

{
"query": {
"field": {
"name": "foo"
}
}
}

[STARTED]: Failed to execute
[org.elasticsearch.action.search.SearchRequest@1dfcee26]
org.elasticsearch.search.SearchParseException: [admin_1395519377710][0]:
from[-1],size[-1]: Parse Failure [Failed to parse source [{
"query": {
"field": {
"name": "foo"
}
}
}]]
at
org.elasticsearch.search.SearchService.parseSource(SearchService.java:595)
at
org.elasticsearch.search.SearchService.createContext(SearchService.java:498)
at
org.elasticsearch.search.SearchService.createAndPutContext(SearchService.java:472)
at
org.elasticsearch.search.SearchService.executeFetchPhase(SearchService.java:316)
at
org.elasticsearch.search.action.SearchServiceTransportAction.sendExecuteFetch(SearchServiceTransportAction.java:304)
at
org.elasticsearch.action.search.type.TransportSearchQueryAndFetchAction$AsyncAction.sendExecuteFirstPhase(TransportSearchQueryAndFetchAction.java:71)
at
org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction.performFirstPhase(TransportSearchTypeAction.java:216)
at
org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction.performFirstPhase(TransportSearchTypeAction.java:203)
at
org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction$2.run(TransportSearchTypeAction.java:186)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: org.elasticsearch.index.query.QueryParsingException:
[admin_1395519377710] No query registered for [field]
at
org.elasticsearch.index.query.QueryParseContext.parseInnerQuery(QueryParseContext.java:221)

AFAIK the two are supposed to be identical queries.

-nikita

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/522d218d-312c-49b9-a1d1-912f4e5a7174%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

2

This is pretty helpful.

Josh

On Mon, Mar 24, 2014 at 6:11 PM, Nikita Tovstoles <
nikita.tovstoles@gmail.com> wrote:

just a heads-up for folks who've upgraded to 1.0.x from 0.9x (as did I).
It appears - and I could be wrong - that field queryhttp://www.elasticsearch.org/guide/en/elasticsearch/reference/0.90/query-dsl-field-query.htmlsyntax no longer works (while equivalent query_string query still does).
Has field query been deprecated?

this works for me:

{
"query": {
"query_string": {
"default_field": "name",
"query" : "foo"
}
}
}

this produces error:

{
"query": {
"field": {
"name": "foo"
}
}
}

[STARTED]: Failed to execute
[org.elasticsearch.action.search.SearchRequest@1dfcee26]
org.elasticsearch.search.SearchParseException: [admin_1395519377710][0]:
from[-1],size[-1]: Parse Failure [Failed to parse source [{
"query": {
"field": {
"name": "foo"
}
}
}]]
at
org.elasticsearch.search.SearchService.parseSource(SearchService.java:595)
at
org.elasticsearch.search.SearchService.createContext(SearchService.java:498)
at
org.elasticsearch.search.SearchService.createAndPutContext(SearchService.java:472)
at
org.elasticsearch.search.SearchService.executeFetchPhase(SearchService.java:316)
at
org.elasticsearch.search.action.SearchServiceTransportAction.sendExecuteFetch(SearchServiceTransportAction.java:304)
at
org.elasticsearch.action.search.type.TransportSearchQueryAndFetchAction$AsyncAction.sendExecuteFirstPhase(TransportSearchQueryAndFetchAction.java:71)
at
org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction.performFirstPhase(TransportSearchTypeAction.java:216)
at
org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction.performFirstPhase(TransportSearchTypeAction.java:203)
at
org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction$2.run(TransportSearchTypeAction.java:186)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: org.elasticsearch.index.query.QueryParsingException:
[admin_1395519377710] No query registered for [field]
at
org.elasticsearch.index.query.QueryParseContext.parseInnerQuery(QueryParseContext.java:221)

AFAIK the two are supposed to be identical queries.

-nikita

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/522d218d-312c-49b9-a1d1-912f4e5a7174%40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/522d218d-312c-49b9-a1d1-912f4e5a7174%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAFaqXJtws7MRnVHkvm572zvH5COoMFjYchKX88e%2BFBWmXZyx2Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

3

Indeed docs appear up to date

Although depreciation warning in these cases would be useful.

On Tuesday, March 25, 2014 2:07:28 AM UTC, Josh Canfield wrote:

This is pretty helpful.

Elasticsearch Platform — Find real-time answers at scale | Elastic

Josh

On Mon, Mar 24, 2014 at 6:11 PM, Nikita Tovstoles <nikita.t...@gmail.com<javascript:>

wrote:

just a heads-up for folks who've upgraded to 1.0.x from 0.9x (as did I).
It appears - and I could be wrong - that field queryhttp://www.elasticsearch.org/guide/en/elasticsearch/reference/0.90/query-dsl-field-query.htmlsyntax no longer works (while equivalent query_string query still does).
Has field query been deprecated?

this works for me:

{
"query": {
"query_string": {
"default_field": "name",
"query" : "foo"
}
}
}

this produces error:

{
"query": {
"field": {
"name": "foo"
}
}
}

[STARTED]: Failed to execute
[org.elasticsearch.action.search.SearchRequest@1dfcee26]
org.elasticsearch.search.SearchParseException: [admin_1395519377710][0]:
from[-1],size[-1]: Parse Failure [Failed to parse source [{
"query": {
"field": {
"name": "foo"
}
}
}]]
at
org.elasticsearch.search.SearchService.parseSource(SearchService.java:595)
at
org.elasticsearch.search.SearchService.createContext(SearchService.java:498)
at
org.elasticsearch.search.SearchService.createAndPutContext(SearchService.java:472)
at
org.elasticsearch.search.SearchService.executeFetchPhase(SearchService.java:316)
at
org.elasticsearch.search.action.SearchServiceTransportAction.sendExecuteFetch(SearchServiceTransportAction.java:304)
at
org.elasticsearch.action.search.type.TransportSearchQueryAndFetchAction$AsyncAction.sendExecuteFirstPhase(TransportSearchQueryAndFetchAction.java:71)
at
org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction.performFirstPhase(TransportSearchTypeAction.java:216)
at
org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction.performFirstPhase(TransportSearchTypeAction.java:203)
at
org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction$2.run(TransportSearchTypeAction.java:186)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: org.elasticsearch.index.query.QueryParsingException:
[admin_1395519377710] No query registered for [field]
at
org.elasticsearch.index.query.QueryParseContext.parseInnerQuery(QueryParseContext.java:221)

AFAIK the two are supposed to be identical queries.

-nikita

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearc...@googlegroups.com <javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/522d218d-312c-49b9-a1d1-912f4e5a7174%40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/522d218d-312c-49b9-a1d1-912f4e5a7174%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/63698ebe-058b-48b5-bbbd-9535b4348af7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

4

Indeed. Fwiw I looked at 'v1x breaking changes' page before posting - no
mention there
On Mar 24, 2014 7:07 PM, "Josh Canfield" joshcanfield@gmail.com wrote:

This is pretty helpful.

Elasticsearch Platform — Find real-time answers at scale | Elastic

Josh

On Mon, Mar 24, 2014 at 6:11 PM, Nikita Tovstoles <
nikita.tovstoles@gmail.com> wrote:

just a heads-up for folks who've upgraded to 1.0.x from 0.9x (as did I).
It appears - and I could be wrong - that field queryhttp://www.elasticsearch.org/guide/en/elasticsearch/reference/0.90/query-dsl-field-query.htmlsyntax no longer works (while equivalent query_string query still does).
Has field query been deprecated?

this works for me:

{
"query": {
"query_string": {
"default_field": "name",
"query" : "foo"
}
}
}

this produces error:

{
"query": {
"field": {
"name": "foo"
}
}
}

[STARTED]: Failed to execute
[org.elasticsearch.action.search.SearchRequest@1dfcee26]
org.elasticsearch.search.SearchParseException: [admin_1395519377710][0]:
from[-1],size[-1]: Parse Failure [Failed to parse source [{
"query": {
"field": {
"name": "foo"
}
}
}]]
at
org.elasticsearch.search.SearchService.parseSource(SearchService.java:595)
at
org.elasticsearch.search.SearchService.createContext(SearchService.java:498)
at
org.elasticsearch.search.SearchService.createAndPutContext(SearchService.java:472)
at
org.elasticsearch.search.SearchService.executeFetchPhase(SearchService.java:316)
at
org.elasticsearch.search.action.SearchServiceTransportAction.sendExecuteFetch(SearchServiceTransportAction.java:304)
at
org.elasticsearch.action.search.type.TransportSearchQueryAndFetchAction$AsyncAction.sendExecuteFirstPhase(TransportSearchQueryAndFetchAction.java:71)
at
org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction.performFirstPhase(TransportSearchTypeAction.java:216)
at
org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction.performFirstPhase(TransportSearchTypeAction.java:203)
at
org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction$2.run(TransportSearchTypeAction.java:186)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: org.elasticsearch.index.query.QueryParsingException:
[admin_1395519377710] No query registered for [field]
at
org.elasticsearch.index.query.QueryParseContext.parseInnerQuery(QueryParseContext.java:221)

AFAIK the two are supposed to be identical queries.

-nikita

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/522d218d-312c-49b9-a1d1-912f4e5a7174%40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/522d218d-312c-49b9-a1d1-912f4e5a7174%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/bZedUbHBS_E/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAFaqXJtws7MRnVHkvm572zvH5COoMFjYchKX88e%2BFBWmXZyx2Q%40mail.gmail.comhttps://groups.google.com/d/msgid/elasticsearch/CAFaqXJtws7MRnVHkvm572zvH5COoMFjYchKX88e%2BFBWmXZyx2Q%40mail.gmail.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAJwaA22cUhYDfEhM-twbZ0wfKNFO4VmBg%2BNkjCRW3uG2GL-dqQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

5

An oversight I guess... can't see anything immediately obv. either. I
hope you tested before putting into production.

On Tuesday, March 25, 2014 2:36:27 AM UTC, Nikita Tovstoles wrote:

Indeed. Fwiw I looked at 'v1x breaking changes' page before posting - no
mention there
On Mar 24, 2014 7:07 PM, "Josh Canfield" <joshca...@gmail.com<javascript:>>
wrote:

This is pretty helpful.

Elasticsearch Platform — Find real-time answers at scale | Elastic

Josh

On Mon, Mar 24, 2014 at 6:11 PM, Nikita Tovstoles <nikita.t...@gmail.com<javascript:>

wrote:

just a heads-up for folks who've upgraded to 1.0.x from 0.9x (as did I).
It appears - and I could be wrong - that field queryhttp://www.elasticsearch.org/guide/en/elasticsearch/reference/0.90/query-dsl-field-query.htmlsyntax no longer works (while equivalent query_string query still does).
Has field query been deprecated?

this works for me:

{
"query": {
"query_string": {
"default_field": "name",
"query" : "foo"
}
}
}

this produces error:

{
"query": {
"field": {
"name": "foo"
}
}
}

[STARTED]: Failed to execute
[org.elasticsearch.action.search.SearchRequest@1dfcee26]
org.elasticsearch.search.SearchParseException: [admin_1395519377710][0]:
from[-1],size[-1]: Parse Failure [Failed to parse source [{
"query": {
"field": {
"name": "foo"
}
}
}]]
at
org.elasticsearch.search.SearchService.parseSource(SearchService.java:595)
at
org.elasticsearch.search.SearchService.createContext(SearchService.java:498)
at
org.elasticsearch.search.SearchService.createAndPutContext(SearchService.java:472)
at
org.elasticsearch.search.SearchService.executeFetchPhase(SearchService.java:316)
at
org.elasticsearch.search.action.SearchServiceTransportAction.sendExecuteFetch(SearchServiceTransportAction.java:304)
at
org.elasticsearch.action.search.type.TransportSearchQueryAndFetchAction$AsyncAction.sendExecuteFirstPhase(TransportSearchQueryAndFetchAction.java:71)
at
org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction.performFirstPhase(TransportSearchTypeAction.java:216)
at
org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction.performFirstPhase(TransportSearchTypeAction.java:203)
at
org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction$2.run(TransportSearchTypeAction.java:186)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: org.elasticsearch.index.query.QueryParsingException:
[admin_1395519377710] No query registered for [field]
at
org.elasticsearch.index.query.QueryParseContext.parseInnerQuery(QueryParseContext.java:221)

AFAIK the two are supposed to be identical queries.

-nikita

--
You received this message because you are subscribed to the Google
Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to elasticsearc...@googlegroups.com <javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/522d218d-312c-49b9-a1d1-912f4e5a7174%40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/522d218d-312c-49b9-a1d1-912f4e5a7174%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/bZedUbHBS_E/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearc...@googlegroups.com <javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAFaqXJtws7MRnVHkvm572zvH5COoMFjYchKX88e%2BFBWmXZyx2Q%40mail.gmail.comhttps://groups.google.com/d/msgid/elasticsearch/CAFaqXJtws7MRnVHkvm572zvH5COoMFjYchKX88e%2BFBWmXZyx2Q%40mail.gmail.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/b9ea05ca-2540-47b6-9549-ed3fe318688a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

6

No biggie. Meant it more as a PSA
On Mar 24, 2014 7:43 PM, "Harry Waye" harry@arachnys.com wrote:

An oversight I guess... can't see anything immediately obv. either. I
hope you tested before putting into production.

On Tuesday, March 25, 2014 2:36:27 AM UTC, Nikita Tovstoles wrote:

Indeed. Fwiw I looked at 'v1x breaking changes' page before posting - no
mention there
On Mar 24, 2014 7:07 PM, "Josh Canfield" joshca...@gmail.com wrote:

This is pretty helpful.

Elasticsearch Platform — Find real-time answers at scale | Elastic
reference/1.x/_deprecations.html

Josh

On Mon, Mar 24, 2014 at 6:11 PM, Nikita Tovstoles <nikita.t...@gmail.com

wrote:

just a heads-up for folks who've upgraded to 1.0.x from 0.9x (as did
I). It appears - and I could be wrong - that field queryhttp://www.elasticsearch.org/guide/en/elasticsearch/reference/0.90/query-dsl-field-query.htmlsyntax no longer works (while equivalent query_string query still does).
Has field query been deprecated?

this works for me:

{
"query": {
"query_string": {
"default_field": "name",
"query" : "foo"
}
}
}

this produces error:

{
"query": {
"field": {
"name": "foo"
}
}
}

[STARTED]: Failed to execute [org.elasticsearch.action.
search.SearchRequest@1dfcee26]
org.elasticsearch.search.SearchParseException:
[admin_1395519377710][0]: from[-1],size[-1]: Parse Failure [Failed to parse
source [{
"query": {
"field": {
"name": "foo"
}
}
}]]
at org.elasticsearch.search.SearchService.parseSource(
SearchService.java:595)
at org.elasticsearch.search.SearchService.createContext(
SearchService.java:498)
at org.elasticsearch.search.SearchService.createAndPutContext(
SearchService.java:472)
at org.elasticsearch.search.SearchService.executeFetchPhase(
SearchService.java:316)
at org.elasticsearch.search.action.SearchServiceTransportAction.
sendExecuteFetch(SearchServiceTransportAction.java:304)
at org.elasticsearch.action.search.type.TransportSearchQueryAndFetchAc
tion$AsyncAction.sendExecuteFirstPhase(TransportSearchQueryAndFetchAc
tion.java:71)
at org.elasticsearch.action.search.type.TransportSearchTypeAction$
BaseAsyncAction.performFirstPhase(TransportSearchTypeAction.java:216)
at org.elasticsearch.action.search.type.TransportSearchTypeAction$
BaseAsyncAction.performFirstPhase(TransportSearchTypeAction.java:203)
at org.elasticsearch.action.search.type.TransportSearchTypeAction$
BaseAsyncAction$2.run(TransportSearchTypeAction.java:186)
at java.util.concurrent.ThreadPoolExecutor.runWorker(
ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(
ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: org.elasticsearch.index.query.QueryParsingException:
[admin_1395519377710] No query registered for [field]
at org.elasticsearch.index.query.QueryParseContext.parseInnerQuery(
QueryParseContext.java:221)

AFAIK the two are supposed to be identical queries.

-nikita

--
You received this message because you are subscribed to the Google
Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/elasticsearch/522d218d-312c-49b9-a1d1-912f4e5a7174%
40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/522d218d-312c-49b9-a1d1-912f4e5a7174%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit https://groups.google.com/d/
topic/elasticsearch/bZedUbHBS_E/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/elasticsearch/CAFaqXJtws7MRnVHkvm572zvH5COoM
FjYchKX88e%2BFBWmXZyx2Q%40mail.gmail.comhttps://groups.google.com/d/msgid/elasticsearch/CAFaqXJtws7MRnVHkvm572zvH5COoMFjYchKX88e%2BFBWmXZyx2Q%40mail.gmail.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/bZedUbHBS_E/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/b9ea05ca-2540-47b6-9549-ed3fe318688a%40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/b9ea05ca-2540-47b6-9549-ed3fe318688a%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAJwaA208p3oa7fcK9EeNLdnpVhc3LHUtgE8U0%3De3FgoV7T6Bag%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.