S.txt
>
> On Thu, Jul 7, 2011 at 11:04 PM, Rob Bygrave
> wrote:
> > This looks like a Bug in v3.3.0.
> >
> > The code below works in 3.0.1 without calling the writer.commit() before
> > IndexReader.open(directory).
> >
> > In v3.3.0 when the index d
This looks like a Bug in v3.3.0.
The code below works in 3.0.1 without calling the writer.commit() before
IndexReader.open(directory).
In v3.3.0 when the index does not yet exist I need to add the
writer.commit() and I believe that creates the segments. If I don't add the
writer.commit() then I
>> Any case where it would break?
If a query uses multiple fields it would break. That is, usually all the
fields need to be in doc in index 2 - not just the modified one.
On Fri, Oct 15, 2010 at 2:35 PM, Erick Erickson wrote:
> This seems like far too much work if I'm reading things right. You
Thanks !!
On Sun, Jun 13, 2010 at 9:43 PM, Toke Eskildsen wrote:
> Rob Bygrave [robin.bygr...@gmail.com] wrote:
> > Has anyone done a performance comparison for an index on a Solid State
> Drive
> > (vs any other hard drive ... SATA/SCSI)?
>
> We did a fair amount of t
Hi,
Has anyone done a performance comparison for an index on a Solid State Drive
(vs any other hard drive ... SATA/SCSI)?
Thanks, Rob.
BTW: Saw this in the SOLR docs...
- If sortMissingLast="false" and sortMissingFirst="false" (the
default),
* then default lucene sorting will be used which places docs without
the
field first in an ascending sort and last in a descending sort.*
On Wed, May 19, 2010 at 4
I'm not a Lucene Guru so hopefully you get a more definitive response.
I believe this means you want a way to specify ... "Nulls High" / "Nulls
Low" for your field (in this case you want Nulls High I believe).
I haven't seen support for that (but it might exist). Looking at
StringValComparator I'
