Yes hoss,
it only convert to the range query when there is two token only,,BTW
thanks for raising the issue
On 11-May-2017 5:38 AM, "Chris Hostetter" wrote:
> : I'm facing a issue when i'm querying the Solr
> : my query is "xiomi Mi 5 -white [64GB/ 3GB]"
> ...
> : +(((Synonym(nameSearch
: I'm facing a issue when i'm querying the Solr
: my query is "xiomi Mi 5 -white [64GB/ 3GB]"
...
: +(((Synonym(nameSearch:xiaomi nameSearch:xiomi)) (nameSearch:mi)
: (nameSearch:5) -(Synonym(nameSearch:putih
: nameSearch:white))*(nameSearch:[64gb/ TO 3gb])*)~4)
...
: Now due to aut
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" wrote:
Hi Aman,
Is the user actually ent
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" 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
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, Sha
Fair enough indeed. And as you've experienced, that other functionality
includes syntax that needs escaping. If you're using SolrJ then there's a
utility method to escape characters.
Erik
> On May 6, 2017, at 20:53, Aman Deep Singh wrote:
>
> Hi Erik,
> We can't use dismax as we are
Hi Erik,
We can't use dismax as we are using the other functionality of edismax
parser
On 07-May-2017 12:13 AM, "Erik Hatcher" wrote:
What about dismax instead of edismax?It might do the righter thing here
without escaping.
> On May 6, 2017, at 12:57, Shawn Heisey wrote:
>
>> On 5/6/2017 7
What about dismax instead of edismax?It might do the righter thing here
without escaping.
> On May 6, 2017, at 12:57, Shawn Heisey wrote:
>
>> On 5/6/2017 7:09 AM, Aman Deep Singh wrote:
>> After escaping the square bracket the query is working fine, Is their
>> any way in the parser to av
On 5/6/2017 7:09 AM, Aman Deep Singh wrote:
> After escaping the square bracket the query is working fine, Is their
> any way in the parser to avoid the automatic conversion if not proper
> query will be passed like in my case even though I haven't passed
> proper range query (with keyword TO).
If
Thanks Shawn,
After escaping the square bracket the query is working fine,
Is their any way in the parser to avoid the automatic conversion if not
proper query will be passed like in my case even though I haven't passed
proper range query (with keyword TO).
On 06-May-2017 6:08 PM, "Shawn Heisey"
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
I'm using a custom request handler with deftype as edismax
My query is -
xiomi Mi 5 -white [64GB/ 3GB]
On 06-May-2017 12:48 AM, "Erick Erickson" wrote:
OK, what _request handler_ are you using? what is the original query?
On Fri, May 5, 2017 at 11:42 AM, Aman Deep Singh
wrote:
> Hi Erick,
> I
OK, what _request handler_ are you using? what is the original query?
On Fri, May 5, 2017 at 11:42 AM, 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 si
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
I'm going to go a little sideways and claim this is an "XY" problem,
the range bits are a side-issue. The problem is that you're trying to
do ranges on textual data that are really numbers. So even if there's
a way to fix the range issue you're talking about, it still won't do
what you expect.
Con
15 matches
Mail list logo
