Hi all,
I noticed that many of the action commands one can execute on an index, or
indices, are documented in the guide as POST, yet GET requests seem to have
the same effect. I'm assuming this is by design and isn't a sign of a
deprecated feature.
My 0.02... someone should update the guide to reflect the support for GET.
Alternatively, the guide could be a nifty github project where the
community can help maintain it? Alternatively-alternatively, the guide
could support comments much like the MySQL docs do. 
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
Hi Roy,
I noticed that many of the action commands one can execute on an index, or
indices, are documented in the guide as POST, yet GET requests seem to have
the same effect. I'm assuming this is by design and isn't a sign of a
deprecated feature.
My understanding is that what you see in guide is aligned with the REST
design principles. However, not all clients can make all types of requests
with request body (for example http clients running in web browser may be
subject of specific restrictions). Due to this GET requests are allowed on
such requests. So, yes, this is by design and is not deprecated.
Not sure if all alternative http methods are always documented in the
guide. When I wanted to learn details I always checked the Java source code
(it is not that hard to find relevant part of the code in Elasticsearch).
My 0.02... someone should update the guide to reflect the support for GET.
Alternatively, the guide could be a nifty github project where the
community can help maintain it? Alternatively-alternatively, the guide
could support comments much like the MySQL docs do. 
The content of guide doc is still generated from
https://github.com/elasticsearch/elasticsearch.github.com
Regards,
Lukas
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
Ah good. I didn't realize the docs were on github.
On Thursday, June 6, 2013 10:53:28 AM UTC-4, Roy Russo wrote:
Hi all,
I noticed that many of the action commands one can execute on an index, or
indices, are documented in the guide as POST, yet GET requests seem to have
the same effect. I'm assuming this is by design and isn't a sign of a
deprecated feature.
My 0.02... someone should update the guide to reflect the support for GET.
Alternatively, the guide could be a nifty github project where the
community can help maintain it? Alternatively-alternatively, the guide
could support comments much like the MySQL docs do.
--
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.
For more options, visit https://groups.google.com/groups/opt_out.