Yep..
On Fri, Aug 11, 2017 at 6:31 AM, OTH wrote:
> Hi, thanks for sharing the article.
>
> On Fri, Aug 11, 2017 at 4:38 AM, Erick Erickson
> wrote:
>
>> Omer:
>>
>> Solr does not implement pure boolean logic, see:
>> https://lucidworks.com/2011/12/28/why-not-and-or-and-not/.
>>
>> With appropri
Hi, thanks for sharing the article.
On Fri, Aug 11, 2017 at 4:38 AM, Erick Erickson
wrote:
> Omer:
>
> Solr does not implement pure boolean logic, see:
> https://lucidworks.com/2011/12/28/why-not-and-or-and-not/.
>
> With appropriate parentheses it can give the same results as you're
> discoveri
Eric you going to vegas next month?
> On Aug 10, 2017, at 7:38 PM, Erick Erickson wrote:
>
> Omer:
>
> Solr does not implement pure boolean logic, see:
> https://lucidworks.com/2011/12/28/why-not-and-or-and-not/.
>
> With appropriate parentheses it can give the same results as you're
> discov
Omer:
Solr does not implement pure boolean logic, see:
https://lucidworks.com/2011/12/28/why-not-and-or-and-not/.
With appropriate parentheses it can give the same results as you're
discovering.
Best
Erick
On Thu, Aug 10, 2017 at 3:00 PM, OTH wrote:
> Thanks for the help!
> That's resolved
Thanks for the help!
That's resolved the issue.
On Fri, Aug 11, 2017 at 1:48 AM, David Hastings <
hastings.recurs...@gmail.com> wrote:
> type:value AND (name:america^1+name:state^1+name:united^1)
>
> but in reality what you want to do is use the fq parameter with type:value
>
> On Thu, Aug 10, 20
type:value AND (name:america^1+name:state^1+name:united^1)
but in reality what you want to do is use the fq parameter with type:value
On Thu, Aug 10, 2017 at 4:36 PM, OTH wrote:
> Hello,
>
> I have the following use case:
>
> I have two fields (among others); one is 'name' and the other is 'typ
I tried that, but it returned no results.
I understand now that the issue is that since the field has been tokenized
- searching for "*san\ *" will try to search for individual tokens which
contain the string sequence "san ", and so of course it won't find any.
I think I've found another workaround
This can be done with escaping space
select?q=field:*san\ *
Probably sow=false in new version might also helo
On Mon, Apr 17, 2017 at 4:42 PM, OTH wrote:
> If I submit the query:
> "select?q=field:*san*"
> Then it works as expected; returning all values in the field which contain
> the string
Ok. What analyzer / fieldtype should I use to be able to search across
tokens?
Basically, I'm just trying to replicate the functionality of the
AnalyzingInfixLookupFactor Suggester, but I need to do it using a regular
index, because I need to utilize multiple fields using edismax bq, which
seems t
Use the analyser available in the solr admin console to find out exactly
how your query is analysed. That should give you a lot more information.
On Mon 17 Apr, 2017, 21:58 OTH, wrote:
> Ok, I get it now, it's because the field has been indexed as tokens. So
> maybe I should use a field which d
Ok, I get it now, it's because the field has been indexed as tokens. So
maybe I should use a field which does not have a tokenizer index? I'll try
something like that. Thanks
On Mon, Apr 17, 2017 at 9:16 PM, OTH wrote:
> The field type is "text_general".
>
> On Mon, Apr 17, 2017 at 7:15 PM, B
The field type is "text_general".
On Mon, Apr 17, 2017 at 7:15 PM, Binoy Dalal wrote:
> I think it returns everything because your query matches *san or " *".
> What is your field type definition?
>
> On Mon 17 Apr, 2017, 19:12 OTH, wrote:
>
> > If I submit the query:
> > "select?q=field:*san*
I think it returns everything because your query matches *san or " *".
What is your field type definition?
On Mon 17 Apr, 2017, 19:12 OTH, wrote:
> If I submit the query:
> "select?q=field:*san*"
> Then it works as expected; returning all values in the field which contain
> the string "san".
>
13 matches
Mail list logo
