Hi all,
I'm getting some strange behavior from the ES server when using a term
query + a geo distance filter + a sort. I've tried this with 1.3.2,
1.3.5, as well as 1.4.0. All exhibit this same behavior. I'm using the
Java transport client. Here is my SearchRequestBuilder payload in
I just noticed I had a typo in my query, this is the query payload I'm
executing if I run it in HTTP (which works)
{
from : 0,
size : 10,
query : {
term : {
ug_context :
c2d2d78a-69cc-11e4-b22e-81db7b9aa660__user__zzzconnzzzlikes
}
},
Looks like a bug in org.apache.usergrid.persistence.index.impl.
EsEntityIndexImpl
Check if the types are set to a non-null value in the SearchRequest. If
you force them to be a null value, SearchRequest will throw the NPE you
posted.
Jörg
On Tue, Nov 11, 2014 at 6:11 PM, Todd Nine
You're right Jorg. There was an issue where types was incorrectly set to
null because more than 1 was specified. As a result, it passed the check
for at least 1 element in the array, even though the type itself in element
0 was null. Thank you for your help!
On Tuesday, November 11, 2014
Hi all
I successfully deployed KIBANA 3.1.0 and I made a first dashboard based on
ELK stack to monitor log files.
However I m quiet surprise since my KIBANA GUI does not look those shown in
on screenshots available on the ElasticSearch web site : Query Filter (on
top of dashboard
I will answer myself:
Any queried type (the parent or any one of its children), if there should
be a filter on it, should be queried using a *filtered query* clause. Any
filtered field should come under the filtered-query *filter *clause, and
any analyzed or score-affecting field should come
Hi,
I need to perform a query + filter on child documents. For the query, I'm
using TopChildren.
Now I wonder what would be more efficient regarding query on *date/numeric
(no score needed) fields* of this child -
should I query on these fields using a HasChild filter in a bool query
Trying to compose a query and filter combination to no avail:
{
from:0,
size:200,
query:{
filtered:{
query:{
query_string:{
fields:[
_all
],
query:\Test message
Weber
On Fri, Apr 18, 2014 at 12:52 PM, Matt Hughes hughes.m...@gmail.com wrote:
Trying to compose a query and filter combination to no avail:
{
from:0,
size:200,
query:{
filtered:{
query:{
query_string:{
fields:[
_all
to compose a query and filter combination to no avail:
{
from:0,
size:200,
query:{
filtered:{
query:{
query_string:{
fields:[
_all
],
query:\Test message
://www.elasticsearch.org/guide/en/elasticsearch/
reference/current/query-dsl-bool-filter.html
Thanks,
Matt Weber
On Fri, Apr 18, 2014 at 12:52 PM, Matt Hughes hughe...@gmail.com wrote:
Trying to compose a query and filter combination to no avail:
{
from:0,
size:200,
query:{
filtered
/elasticsearch/reference/current/query-dsl-bool-filter.html
Thanks,
Matt Weber
On Fri, Apr 18, 2014 at 12:52 PM, Matt Hughes hughe...@gmail.com wrote:
Trying to compose a query and filter combination to no avail:
{
from:0,
size:200,
query:{
filtered:{
query
Hi Clinton,
Thanks for your reply. I tried as suggested and the same is working now :)
One question though, I have to pass the text field in lower case always as
the same is getting analyzed by standard analyzer I guess. Is there any way
to pass multiple match in bool for text search so that I
Hi,
I'm doing the below query to fetch data date wise. But in the result the
score is coming as null. How to get the score here.
curl -XPOST 10.203.251.142:9200/aricloud/_search -d
'{
query: {
filtered: {
query : {
match : {
CLOUD_TYPE
My first question is: why do you want the score? The score is used only for
sorting, and you're sorting on NODE_ID.
If you really want it (and there is a cost to computing the score) then you
can set track_scores to true.
Hi,
I'm trying to run the below bool query with filter range to fetch all the
node data with CLOUD_TYPE=AWS-EC2 and NODE_STATUS=ACTIVE.
But I'm getting SearchPhaseExecutionException from elasticsearch. Please
let me know the correct way to do this.
curl -XPOST http://10.203.251.142:9200
You need to pass the search request a query, so just change the above to:
GET /_search
{ query: { filtered: }, from: 0, size: 3 ...}
On 14 March 2014 14:55, Subhadip Bagui i.ba...@gmail.com wrote:
Hi,
I'm trying to run the below bool query with filter range to fetch all the
node
17 matches
Mail list logo
