I was just wondering why Elasticsearch facets are queried with a POST,
as opposed to a GET, request. Does Elastic search store facets on the
system to be used again later, or are they more of a one time thing
like search queries?
Thanks
~Gregory
I was just wondering why Elasticsearch facets are queried with a POST,
as opposed to a GET, request. Does Elastic search store facets on the
system to be used again later, or are they more of a one time thing
like search queries?
Thanks
~Gregory
facets are just part of a search request, and the search request can be
executed either using a GET, or using a POST. The reason why it also
supports POST is because some HTTP client libs have problems sending GET
requests with a body.
On Wed, Apr 4, 2012 at 6:05 AM, Gregory Schier gschier1990@gmail.comwrote:
I was just wondering why Elasticsearch facets are queried with a POST,
as opposed to a GET, request. Does Elastic search store facets on the
system to be used again later, or are they more of a one time thing
like search queries?Thanks
~Gregory
Oh right I forgot about the troubles sending get requests with a body.
It makes sense now.
Thanks!
On Apr 4, 8:47 am, Shay Banon kim...@gmail.com wrote:
facets are just part of a search request, and the search request can be
executed either using a GET, or using a POST. The reason why it also
supports POST is because some HTTP client libs have problems sending GET
requests with a body.On Wed, Apr 4, 2012 at 6:05 AM, Gregory Schier gschier1...@gmail.comwrote:
I was just wondering why Elasticsearch facets are queried with a POST,
as opposed to a GET, request. Does Elastic search store facets on the
system to be used again later, or are they more of a one time thing
like search queries?Thanks
~Gregory
© 2020. All Rights Reserved - Elasticsearch
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.