Of course, I should have noticed he typed 3G instead of 32G.
On 2017-05-07 10:46 AM, Aman Deep Singh wrote:
Yes Rick,
User is actually typing this type of queries ,this was a random user query
pick from access logs
On 07-May-2017 7:29 PM, "Rick Leir" <rl...@leirtech.com> wrote:
Hi Aman,
Is the user actually entering that query? It seems unlikely. Perhaps you
have a form selector for various Apple products. Could you not have an
enumerated type for the products, and simplify everything? I must be
missing something here. Cheers -- Rick
On May 6, 2017 8:38:14 AM EDT, Shawn Heisey <apa...@elyograg.org> wrote:
On 5/5/2017 12:42 PM, Aman Deep Singh wrote:
Hi Erick, I don't want to do the range query , That is why I'm using
the pattern replace filter to remove all the non alphanumeric to
space
so that this type of situation don't arrive,Since end user can query
anything, also in the query I haven't mention any range related
keyword (TO). If my query is like [64GB/3GB] it works fine and
doesn't
convert to range query.
I hope I'm headed in the right direction here.
Square brackets are special characters to the query parser -- they are
typically used to specify a range query. It's a little odd that Solr
would add the "TO" for you like it seems to be doing, but not REALLY
surprising. This would be happening *before* the parts of the query
make it to your analysis chain where you have the pattern replace
filter.
If you want to NOT have special characters perform their special
function, but actually become part of the query, you'll need to escape
them with a backslash. Escaping all the special characters in your
query yields this query:
xiomi Mi 5 \-white \[64GB\/ 3GB\]
It's difficult to decide whether the dash character before "white" was
intended as a "NOT" operator or to be part of the query. You might not
want to escape that one.
Thanks,
Shawn
--
Sorry for being brief. Alternate email is rickleir at yahoo dot com
