ES 2.2 Boolean search?

[RobParker]

I thought this would be really simple but it's proving harder than I thought.

Is it possible to search for a post that contains all 3 specific terms. Ideally I'd like to find the oldest first.

"term1" AND "term2" AND "term3"

matches with the "and" as well.

I assumed ES can do these type of boolean searches so assume XFES can?

 

[Mike]

We use + / | / - for and, or and not respectively, though the plus is essentially unneeded as your example is equivalent to term1 term2 term3 -- they all have to be present by default.

 

[RobParker]

That doesn't seem to be the case.

term1 term2 term3

Turns up posts with only 1 of those terms which made me think there must have been a different way to specify the AND

 

[Mike]

As an example, if I search for term1 term4 here (literally those values ), I don't get this thread. I get only one result (probably now 2 including this post) which happens to use both words. If I do a search with term 1-2-3 as written out, the only results are this thread.

So it certainly appears to work as I'd expect.

 

[Mikethemix]

I find this most confusing.
When I searched
term 1-2-3
as suggested, it produced loads of results NOT including this thread
When I searched
term 1 term 2
it found this thread.

can you please explain exactly how to use the / escape character with specific examples?
(We are using XFES plus XON's search add-ons on a VPS with Elastic Search).
Many thanks,
Mike

 

[Mr Lucky]

As an example, if I search for term1 term4 here (literally those values ), I don't get this thread.

Seems to me search is not returning threads, it is returning posts. Hence no results for term1 term2 term3 term4

(Well there will be after I post this)

 

[Mr Lucky]

We use + / | / - for and, or and not respectively,

However I just noticed that unlike + or -, to function as or, | requires a space either side.

 

[Mikethemix]

Very helpful comments above, however...

can someone please explain exactly how to use the / escape character with specific examples?

Many thanks,
Mike