Max expansion in text queries


(Alexander Reelsen) #1

Hi there,

I have got a question about the max_expansions parameter in text
queries. According to the documentation the parameter only applies for
text phrase prefix queries and has a different meaning in text queries
(for fuzziness instead of prefix query expansions).

However the following lines seem to cause different results

QueryBuilders.textQuery("ProductName.query",
queryString).maxExpansions($arbitraryNumber)
QueryBuilders.textQuery("ProductName.query", queryString)

We had this accidentally in our code. The first version caused a out
of memory exception with small memory memory setups (like on our
development machines where we dont handle big indexes), but seems to
work on our bigger testing machines. My guess was, that using this
parameter should not have any effect in a text query without
specifying fuzziness.
I guess I am wrong on this one?

--Alexander


(Shay Banon) #2

maxExpansion is not used when using text query (I just double checked it), so its strange. Are you sure its related?

On Monday, January 30, 2012 at 4:45 PM, Alexander Reelsen wrote:

Hi there,

I have got a question about the max_expansions parameter in text
queries. According to the documentation the parameter only applies for
text phrase prefix queries and has a different meaning in text queries
(for fuzziness instead of prefix query expansions).

However the following lines seem to cause different results

QueryBuilders.textQuery("ProductName.query",
queryString).maxExpansions($arbitraryNumber)
QueryBuilders.textQuery("ProductName.query", queryString)

We had this accidentally in our code. The first version caused a out
of memory exception with small memory memory setups (like on our
development machines where we dont handle big indexes), but seems to
work on our bigger testing machines. My guess was, that using this
parameter should not have any effect in a text query without
specifying fuzziness.
I guess I am wrong on this one?

--Alexander


(system) #3