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.
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
mpercolate REST API should support source parameter #4900
Labels
Comments
ghost
assigned dadoonet
Jan 27, 2014
dadoonet
added a commit
to dadoonet/elasticsearch
that referenced
this issue
Jan 27, 2014
As stated in documentation, we should support `?source=` parameter in mpercolate REST operations. This is how to reproduce it: ```sh curl -XDELETE "http://localhost:9200/test" curl -XPUT "http://localhost:9200/test/.percolator/1" -d' { "query" : { "match" : { "foo" : "bar" } } }' # This one works curl -XPOST "http://localhost:9200/test/message/_mpercolate" -d ' {"percolate" : {}} {"doc" : {"foo" : "bar is in foo"}} ' # This one gives: BroadcastShardOperationFailedException[[test][2] ]; nested: PercolateException[failed to percolate]; nested: ElasticsearchIllegalArgumentException[Nothing to percolate]; curl -XGET "http://localhost:9200/test/message/_mpercolate?source=%7B%22percolate%22%3A%7B%7D%7D%0A%7B%22doc%22%3A%7B%22foo%22%3A%22bar is in foo%22%7D%7D%0A" ``` Closes elastic#4900.
dadoonet
added a commit
that referenced
this issue
Jan 28, 2014
As stated in documentation, we should support `?source=` parameter in mpercolate REST operations. This is how to reproduce it: ```sh curl -XDELETE "http://localhost:9200/test" curl -XPUT "http://localhost:9200/test/.percolator/1" -d' { "query" : { "match" : { "foo" : "bar" } } }' # This one works curl -XPOST "http://localhost:9200/test/message/_mpercolate" -d ' {"percolate" : {}} {"doc" : {"foo" : "bar is in foo"}} ' # This one gives: BroadcastShardOperationFailedException[[test][2] ]; nested: PercolateException[failed to percolate]; nested: ElasticsearchIllegalArgumentException[Nothing to percolate]; curl -XGET "http://localhost:9200/test/message/_mpercolate?source=%7B%22percolate%22%3A%7B%7D%7D%0A%7B%22doc%22%3A%7B%22foo%22%3A%22bar is in foo%22%7D%7D%0A" ``` Closes #4900.
dadoonet
added a commit
that referenced
this issue
Jan 28, 2014
As stated in documentation, we should support `?source=` parameter in mpercolate REST operations. This is how to reproduce it: ```sh curl -XDELETE "http://localhost:9200/test" curl -XPUT "http://localhost:9200/test/.percolator/1" -d' { "query" : { "match" : { "foo" : "bar" } } }' # This one works curl -XPOST "http://localhost:9200/test/message/_mpercolate" -d ' {"percolate" : {}} {"doc" : {"foo" : "bar is in foo"}} ' # This one gives: BroadcastShardOperationFailedException[[test][2] ]; nested: PercolateException[failed to percolate]; nested: ElasticsearchIllegalArgumentException[Nothing to percolate]; curl -XGET "http://localhost:9200/test/message/_mpercolate?source=%7B%22percolate%22%3A%7B%7D%7D%0A%7B%22doc%22%3A%7B%22foo%22%3A%22bar is in foo%22%7D%7D%0A" ``` Closes #4900.
dadoonet
added a commit
to dadoonet/elasticsearch
that referenced
this issue
Jan 28, 2014
In recent changes, we added missing support for `source` parameter in some REST APIs: * elastic#4892 : mget * elastic#4900 : mpercolate * elastic#4901 : msearch * elastic#4902 : mtermvectors * elastic#4903 : percolate ```java BytesReference content = null; if (request.hasContent()) { content = request.content(); } else { String source = request.param("source"); if (source != null) { content = new BytesArray(source); } } ``` It's definitely better to have: ```java BytesReference content = request.content(); if (!request.hasContent()) { String source = request.param("source"); if (source != null) { content = new BytesArray(source); } } ``` That said, it could be nice to have a single method to manage it for various REST actions. Closes elastic#4924.
dadoonet
added a commit
that referenced
this issue
Jan 28, 2014
In recent changes, we added missing support for `source` parameter in some REST APIs: * #4892 : mget * #4900 : mpercolate * #4901 : msearch * #4902 : mtermvectors * #4903 : percolate ```java BytesReference content = null; if (request.hasContent()) { content = request.content(); } else { String source = request.param("source"); if (source != null) { content = new BytesArray(source); } } ``` It's definitely better to have: ```java BytesReference content = request.content(); if (!request.hasContent()) { String source = request.param("source"); if (source != null) { content = new BytesArray(source); } } ``` That said, it could be nice to have a single method to manage it for various REST actions. Closes #4924.
dadoonet
added a commit
that referenced
this issue
Jan 28, 2014
In recent changes, we added missing support for `source` parameter in some REST APIs: * #4892 : mget * #4900 : mpercolate * #4901 : msearch * #4902 : mtermvectors * #4903 : percolate ```java BytesReference content = null; if (request.hasContent()) { content = request.content(); } else { String source = request.param("source"); if (source != null) { content = new BytesArray(source); } } ``` It's definitely better to have: ```java BytesReference content = request.content(); if (!request.hasContent()) { String source = request.param("source"); if (source != null) { content = new BytesArray(source); } } ``` That said, it could be nice to have a single method to manage it for various REST actions. Closes #4924.
dadoonet
added a commit
that referenced
this issue
Jan 28, 2014
In recent changes, we added missing support for `source` parameter in some REST APIs: * #4892 : mget * #4900 : mpercolate * #4901 : msearch * #4902 : mtermvectors * #4903 : percolate ```java BytesReference content = null; if (request.hasContent()) { content = request.content(); } else { String source = request.param("source"); if (source != null) { content = new BytesArray(source); } } ``` It's definitely better to have: ```java BytesReference content = request.content(); if (!request.hasContent()) { String source = request.param("source"); if (source != null) { content = new BytesArray(source); } } ``` That said, it could be nice to have a single method to manage it for various REST actions. Closes #4924.
dadoonet
added a commit
that referenced
this issue
Jan 28, 2014
In recent changes, we added missing support for `source` parameter in some REST APIs: * #4892 : mget * #4900 : mpercolate * #4901 : msearch * #4902 : mtermvectors * #4903 : percolate ```java BytesReference content = null; if (request.hasContent()) { content = request.content(); } else { String source = request.param("source"); if (source != null) { content = new BytesArray(source); } } ``` It's definitely better to have: ```java BytesReference content = request.content(); if (!request.hasContent()) { String source = request.param("source"); if (source != null) { content = new BytesArray(source); } } ``` That said, it could be nice to have a single method to manage it for various REST actions. Closes #4924.
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
In recent changes, we added missing support for `source` parameter in some REST APIs: * elastic#4892 : mget * elastic#4900 : mpercolate * elastic#4901 : msearch * elastic#4902 : mtermvectors * elastic#4903 : percolate ```java BytesReference content = null; if (request.hasContent()) { content = request.content(); } else { String source = request.param("source"); if (source != null) { content = new BytesArray(source); } } ``` It's definitely better to have: ```java BytesReference content = request.content(); if (!request.hasContent()) { String source = request.param("source"); if (source != null) { content = new BytesArray(source); } } ``` That said, it could be nice to have a single method to manage it for various REST actions. Closes elastic#4924.
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
As stated in documentation, we should support `?source=` parameter in mpercolate REST operations. This is how to reproduce it: ```sh curl -XDELETE "http://localhost:9200/test" curl -XPUT "http://localhost:9200/test/.percolator/1" -d' { "query" : { "match" : { "foo" : "bar" } } }' # This one works curl -XPOST "http://localhost:9200/test/message/_mpercolate" -d ' {"percolate" : {}} {"doc" : {"foo" : "bar is in foo"}} ' # This one gives: BroadcastShardOperationFailedException[[test][2] ]; nested: PercolateException[failed to percolate]; nested: ElasticsearchIllegalArgumentException[Nothing to percolate]; curl -XGET "http://localhost:9200/test/message/_mpercolate?source=%7B%22percolate%22%3A%7B%7D%7D%0A%7B%22doc%22%3A%7B%22foo%22%3A%22bar is in foo%22%7D%7D%0A" ``` Closes elastic#4900.
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
In recent changes, we added missing support for `source` parameter in some REST APIs: * elastic#4892 : mget * elastic#4900 : mpercolate * elastic#4901 : msearch * elastic#4902 : mtermvectors * elastic#4903 : percolate ```java BytesReference content = null; if (request.hasContent()) { content = request.content(); } else { String source = request.param("source"); if (source != null) { content = new BytesArray(source); } } ``` It's definitely better to have: ```java BytesReference content = request.content(); if (!request.hasContent()) { String source = request.param("source"); if (source != null) { content = new BytesArray(source); } } ``` That said, it could be nice to have a single method to manage it for various REST actions. Closes elastic#4924.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As stated in documentation, we should support
?source=
parameter in mpercolate REST operations.This is how to reproduce it:
The text was updated successfully, but these errors were encountered: