Using AND and OR terms with multi-match ?

[Kristian Rosenvold]

Fixing the to be or not to be stop word problem with multi-match, has 
the very undesirable effect of breaking user-entered AND and OR terms 
directly in the query string. Our users would really like both; is there a 
way to accomplish this ?

Kristian


-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/43303639-42d2-4516-9714-f322f7eaf9d7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Matching on sibling json nodes ?

[Kristian Rosenvold]

We're submitting a json document that looks like this:

{
  book: {
title : book1,
  authors: [
{name:auth1, role:role1},
{name:auth2, role:role2}
  ]
}
}


We would like to do searches that find this for a search on auth1/role1 but 
*not* for auth1/role2. We have used nested queries to make this work, but 
unfortunately nested queries dont work with highlighting. Is there any 
other way to accomplish this ? (We are contemplating simply filing a new 
field that combines name and role, but that would also have some drawbacks).

Kristian

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/0b062a6d-5766-4dee-96a5-27aff637f56b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.