On Monday 01 June 2009 16:50, Sam Michaels wrote:
> So the fix for this problem would be
>
> 1. Stop using WordDelimiterFilter for queries (what is the alternative) OR
> 2. Not allow any search strings without any alphanumeric characters..
We ran into this same problem while replacing all characte
Yonik,
Done, here is the link.
https://issues.apache.org/jira/browse/SOLR-1196
SM.
Yonik Seeley-2 wrote:
>
> On Mon, Jun 1, 2009 at 10:50 AM, Sam Michaels wrote:
>>
>> So the fix for this problem would be
>>
>> 1. Stop using WordDelimiterFilter for queries (what is the alternative)
>> OR
>>
On Mon, Jun 1, 2009 at 10:50 AM, Sam Michaels wrote:
>
> So the fix for this problem would be
>
> 1. Stop using WordDelimiterFilter for queries (what is the alternative) OR
> 2. Not allow any search strings without any alphanumeric characters..
Short term workaround for you, yes.
I would classify
So the fix for this problem would be
1. Stop using WordDelimiterFilter for queries (what is the alternative) OR
2. Not allow any search strings without any alphanumeric characters..
SM.
Yonik Seeley-2 wrote:
>
> OK, here's the deal:
>
> -features:foo features:(\...@#$%\^&\*\(\))
> -features:
OK, here's the deal:
-features:foo features:(\...@#$%\^&\*\(\))
-features:foo features:(\...@#$%\^&\*\(\))
-features:foo
-features:foo
The text analysis is throwing away non alphanumeric chars (probably
the WordDelimiterFilter). The Lucene (and Solr) query parser throws
away term queries when th
Walter,
The analysis link does not produce any matches for either @ or !...@#$%^&*()
strings when I try to match against bathing. I'm worried that this might be
the symptom of another problem (which has not revealed itself yet) and want
to get to the bottom of this...
Thank you.
sm
Walter Unde
Use the [analysis] link on the Solr admin UI to get more info on
how this is being interpreted.
However, I am curious about why this is important. Do users enter
this query often? If not, maybe it is not something to spend time on.
wunder
On 5/31/09 2:56 PM, "Sam Michaels" wrote:
>
> Here is
Here is the output from the debug query when I'm trying to match the String @
against Bathing (should not match)
3.2689073 = (MATCH) weight(activity_type:NAME in 0), product of:
0.9994 = queryWeight(activity_type:NAME), product of:
3.2689075 = idf(docFreq=153, numDocs=1489)
0.30591
Upon some further experimentation, I found out that even @ matches all the
documents. However when I append the wildcard * to @ (@*) then there is no
match...
SM
Sam Michaels wrote:
>
> Hi,
>
> I'm running Solr 1.3/Java 1.6.
>
> When I run a query like - (activity_type:NAME) AND
> title:(
As per relevance, no results should be returned. But all the results are
returned in alphabetical order.
Walter Underwood wrote:
>
> I'm really curious. What is the most relevant result for that query?
>
> wunder
>
> On 5/30/09 7:35 PM, "Ryan McKinley" wrote:
>
>> two key things to try (for
I'm really curious. What is the most relevant result for that query?
wunder
On 5/30/09 7:35 PM, "Ryan McKinley" wrote:
> two key things to try (for anyone ever wondering why a query matches
> documents)
>
> 1. add &debugQuery=true and look at the explain text below --
> anything that contribu
two key things to try (for anyone ever wondering why a query matches documents)
1. add &debugQuery=true and look at the explain text below --
anything that contributed to the score is listed there
2. check /admin/analysis.jsp -- this will let you see how analyzers
break text up into tokens.
Not
Hi,
I'm running Solr 1.3/Java 1.6.
When I run a query like - (activity_type:NAME) AND title:(\...@#$%\^&\*\(\))
all the documents are returned even though there is not a single match.
There is no title that matches the string (which has been escaped).
My document structure is as follows
N
13 matches
Mail list logo
