The wiki at http://wiki.apache.org/lucene-java/ has come under attack by
spammers more frequently of late, so the PMC has decided to lock it down in an
attempt to reduce the work involved in tracking and removing spam.
From now on, only people who appear on
http://wiki.apache.org/lucene-java/Co
Unfortunately updateable docvalues is not supported yet, but it future
AFAIK it could be available using stack update approach
https://issues.apache.org/jira/browse/SOLR-3855
https://issues.apache.org/jira/browse/LUCENE-4258
On Sat, Mar 23, 2013 at 9:52 AM, Pablo Guerrero wrote:
> Hello everyo
I appreciate your help with this!
I was attempting to follow your advice when I noticed another odd behavior
that leads me to believe they are not being stored correctly.
If I add two documents at once using solr's update handler like so:
[{"id":"1","foo_ap":"bar|50"}},{"id":"2","foo_ap":"bar|75
ISOLatin1AccentFilter has been deprecated for quite some time,
ASCIIFoldingFilter is preferred
Best
Erick
On Fri, Mar 22, 2013 at 2:59 PM, Jerome Blouin wrote:
> Thanks. I'll check that later.
>
> -Original Message-
> From: Sujit Pal [mailto:sujitatgt...@gmail.com] On Behalf Of SUJ
Alex, did you try to get it working with a single term like adding
"the foobar" and then drawing suggestions for "the foo" ?
simon
On Sun, Mar 24, 2013 at 8:51 PM, Alexander Reelsen wrote:
> Hey there,
>
> I am trying to get up some working example with the AnalyzingSuggester and
> stopwords - l
Hey there,
I am trying to get up some working example with the AnalyzingSuggester and
stopwords - like it is done in the corresponding unit test.
I thought, I could build the AnalyzingSuggester from a
HighfrequencyDictionary using a non_analyzed field - and then use a
stopwordsanalyzer in the con
Hey,
this is in-fact a bug in the MultiFieldQueryParser, can you open a
ticket for this please in our bugtracker?
MultifieldQueryParser should override getRegexpQuery but it doesn't
simon
On Sun, Mar 24, 2013 at 3:57 PM, Adam Rauch wrote:
> I'm using MultiFieldQueryParser to parse search queri
I'm using MultiFieldQueryParser to parse search queries. I find that
certain query strings (e.g., "/study/" without the quotes) cause
MultiFieldQueryParser.parse() to throw an AssertionError, if asserts are
enabled. In production, parse() returns a Query, but it seems to be
corrupt. using it to s
Hello,
We have documents with many numerical fields. In some search scenario,
we would like to create a filter based on the sum of the values of two
fields.
For example, assume we have fields F1 and F2, we would like to find
all documents with condition F1+F2 > 5.0. This filter may be combined
wi
