Greetings all,
I found a bug today while trying to upgrade solr from 1.4.1 to 3.1 I'm not
sure if this is a lucene or solr problem, I normally use lucene through
solr. I've already posted this to the solr mailing list, but I wanted to
notify the lucene group also.
In 1.4.1 I was able to insert t
OK, if they're all in a single index, you might also try using Lucene
sorting. Be aware
that the first sort on a field takes extra time to warm the caches...
But note that sorting is for single-valued, un-tokenized fields..
Best
Erick
On Fri, Jun 3, 2011 at 2:39 AM, Alexander Rosemann
wrote:
>
The Boolean operators provided basically map to MUST (+), SHOULD (no
symbol) and NOT (-)
If we write query like (jakarta AND apache) OR website what happen?
>> It will return results with documents having Jakarta & Apache or Website
Is it possible that we can get the document that contains 'jakar
Hi,
As per the Grouping discussion in the URL below:
http://lucene.apache.org/java/3_0_3/queryparsersyntax.html
(jakarta OR apache) AND website query means website must exist and either term
jakarta or apache may exist.
If we write query like (jakarta AND apache) OR website what happen?
Is it pos
Hi,
As per the Grouping discussion in the URL below:
http://lucene.apache.org/java/3_0_3/queryparsersyntax.html
(jakarta OR apache) AND website query means website must exist and either term
jakarta or apache may exist.
If we write query like (jakarta AND apache) OR website what happen?
Is it pos
