I have a visual query generator in my application from which user can
generate complex and large ES queries. As these queries may be quite large
(a few megabytes), I want to compress the search request I'm sending to ES.
Trying this with curl has proved unsuccessful so far, using the command:
ES just replies with a generic search response (the one you get when you
send an empty post request to search url). If I remove the content encoding
header ES replies with a SearchParseException (as expected because it can't
parse compressed bytes as JSON).
So, am I missing something here or ES just does not support compressed
requests?
On Sat, 2013-02-23 at 04:35 -0800, C. Keser wrote:
Hi,
I have a visual query generator in my application from which user can
generate complex and large ES queries. As these queries may be quite
large (a few megabytes), I want to compress the search request I'm
sending to ES. Trying this with curl has proved unsuccessful so far,
using the command:
You need to enable http compression on each node, by adding this to your
config file:
ES just replies with a generic search response (the one you get when
you send an empty post request to search url). If I remove the content
encoding header ES replies with a SearchParseException (as expected
because it can't parse compressed bytes as JSON).
So, am I missing something here or ES just does not support compressed
requests?
Already did that. Also doesn't setting http.compression affect the
responses (from ES) only? I want ES to accept compressed requests.
23 Şubat 2013 Cumartesi 15:49:45 UTC+2 tarihinde Clinton Gormley yazdı:
On Sat, 2013-02-23 at 04:35 -0800, C. Keser wrote:
Hi,
I have a visual query generator in my application from which user can
generate complex and large ES queries. As these queries may be quite
large (a few megabytes), I want to compress the search request I'm
sending to ES. Trying this with curl has proved unsuccessful so far,
using the command:
You need to enable http compression on each node, by adding this to your
config file:
ES just replies with a generic search response (the one you get when
you send an empty post request to search url). If I remove the content
encoding header ES replies with a SearchParseException (as expected
because it can't parse compressed bytes as JSON).
So, am I missing something here or ES just does not support compressed
requests?
--
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:>.
For more options, visit https://groups.google.com/groups/opt_out.
On a different note , can i compress the response from ES ?
Thanks
Vineeth
On Sat, Feb 23, 2013 at 7:26 PM, C. Keser ckeser@gmail.com wrote:
Already did that. Also doesn't setting http.compression affect the
responses (from ES) only? I want ES to accept compressed requests.
23 Şubat 2013 Cumartesi 15:49:45 UTC+2 tarihinde Clinton Gormley yazdı:
On Sat, 2013-02-23 at 04:35 -0800, C. Keser wrote:
Hi,
I have a visual query generator in my application from which user can
generate complex and large ES queries. As these queries may be quite
large (a few megabytes), I want to compress the search request I'm
sending to ES. Trying this with curl has proved unsuccessful so far,
using the command:
You need to enable http compression on each node, by adding this to your
config file:
ES just replies with a generic search response (the one you get when
you send an empty post request to search url). If I remove the content
encoding header ES replies with a SearchParseException (as expected
because it can't parse compressed bytes as JSON).
So, am I missing something here or ES just does not support compressed
requests?
On Sat, 2013-02-23 at 05:56 -0800, C. Keser wrote:
Already did that. Also doesn't setting http.compression affect the
responses (from ES) only? I want ES to accept compressed requests.
Oh right - hmmm... interesting
No idea I'm afraid
23 Şubat 2013 Cumartesi 15:49:45 UTC+2 tarihinde Clinton Gormley
yazdı:
On Sat, 2013-02-23 at 04:35 -0800, C. Keser wrote:
> Hi,
>
>
> I have a visual query generator in my application from which
user can
> generate complex and large ES queries. As these queries may
be quite
> large (a few megabytes), I want to compress the search
request I'm
> sending to ES. Trying this with curl has proved unsuccessful
so far,
> using the command:
You need to enable http compression on each node, by adding
this to your
config file:
http.compression: true
See
http://www.elasticsearch.org/guide/reference/modules/http.html
clint
>
>
> curl -v -i --compressed -H "Content-encoding: gzip" -X POST
--data
> @req.txt.gz http://localhost:9200/test1/_search\?pretty
\=true
>
>
>
>
>
> ES just replies with a generic search response (the one you
get when
> you send an empty post request to search url). If I remove
the content
> encoding header ES replies with a SearchParseException (as
expected
> because it can't parse compressed bytes as JSON).
>
>
> So, am I missing something here or ES just does not support
compressed
> requests?
>
> --
> 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.
> For more options, visit
https://groups.google.com/groups/opt_out.
>
>
On Sat, 2013-02-23 at 19:44 +0530, Vineeth Mohan wrote:
On a different note , can i compress the response from ES ?
yes - set http.compression: true, and include this header in your
request:
Accept-Encoding: gzip, deflate
clint
Thanks
Vineeth
On Sat, Feb 23, 2013 at 7:26 PM, C. Keser ckeser@gmail.com wrote:
Already did that. Also doesn't setting http.compression affect
the responses (from ES) only? I want ES to accept compressed
requests.
23 Şubat 2013 Cumartesi 15:49:45 UTC+2 tarihinde Clinton
Gormley yazdı:
On Sat, 2013-02-23 at 04:35 -0800, C. Keser wrote:
> Hi,
>
>
> I have a visual query generator in my application
from which user can
> generate complex and large ES queries. As these
queries may be quite
> large (a few megabytes), I want to compress the
search request I'm
> sending to ES. Trying this with curl has proved
unsuccessful so far,
> using the command:
You need to enable http compression on each node, by
adding this to your
config file:
http.compression: true
See
http://www.elasticsearch.org/guide/reference/modules/http.html
clint
>
>
> curl -v -i --compressed -H "Content-encoding: gzip"
-X POST --data
> @req.txt.gz http://localhost:9200/test1/_search
\?pretty\=true
>
>
>
>
>
> ES just replies with a generic search response (the
one you get when
> you send an empty post request to search url). If I
remove the content
> encoding header ES replies with a
SearchParseException (as expected
> because it can't parse compressed bytes as JSON).
>
>
> So, am I missing something here or ES just does not
support compressed
> requests?
>
> --
> 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.
> For more options, visit
https://groups.google.com/groups/opt_out.
>
>
23 Şubat 2013 Cumartesi 15:49:45 UTC+2 tarihinde Clinton Gormley yazdı:
On Sat, 2013-02-23 at 04:35 -0800, C. Keser wrote:
Hi,
I have a visual query generator in my application from which user can
generate complex and large ES queries. As these queries may be quite
large (a few megabytes), I want to compress the search request I'm
sending to ES. Trying this with curl has proved unsuccessful so far,
using the command:
You need to enable http compression on each node, by adding this to your
config file:
ES just replies with a generic search response (the one you get when
you send an empty post request to search url). If I remove the content
encoding header ES replies with a SearchParseException (as expected
because it can't parse compressed bytes as JSON).
So, am I missing something here or ES just does not support compressed
requests?
23 Şubat 2013 Cumartesi 15:49:45 UTC+2 tarihinde Clinton Gormley yazdı:
On Sat, 2013-02-23 at 04:35 -0800, C. Keser wrote:
Hi,
I have a visual query generator in my application from which user can
generate complex and large ES queries. As these queries may be quite
large (a few megabytes), I want to compress the search request I'm
sending to ES. Trying this with curl has proved unsuccessful so far,
using the command:
You need to enable http compression on each node, by adding this to your
config file:
ES just replies with a generic search response (the one you get when
you send an empty post request to search url). If I remove the content
encoding header ES replies with a SearchParseException (as expected
because it can't parse compressed bytes as JSON).
So, am I missing something here or ES just does not support compressed
requests?
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.