just one IndexWriter writes on Index and after a specific time(like one day
or one week etc), i create a new IndexWriter on new Directory and another
thread try to optimize old IndexWirter.
On Thu, Oct 16, 2008 at 5:25 PM, Michael McCandless <
[EMAIL PROTECTED]> wrote:
>
> Can you post the full t
i think you can use SortComparatorSource to control on sort of documents.
but i can not understand your problem correctly
On Thu, Oct 16, 2008 at 6:14 PM, Anselmo <[EMAIL PROTECTED]>wrote:
>
> I am using Lucene to search for products in an online-shop with several
> shops, brands etc.
>
> Is it
When you run the optimize, is it with the already opened IndexWriter
on the old directory?
Do you use the default locking impl. in Directory
(SimpleFSLockFactory)? Are you changing the lock directory, or ever
forcefully removing the lock file (or calling IndexReader/
Writer#unlock)?
M
i use SimpleFSLockFactory and optimized opened IndexWriter, but i use api to
forcefully removing the lock file.
this missing file, just occurs in sometimes not always??
On Fri, Oct 17, 2008 at 12:41 PM, Michael McCandless <
[EMAIL PROTECTED]> wrote:
>
> When you run the optimize, is it with the
what i observed is that it creates the index folder, but that is empty.
it should have one/two file named segments.gen and segments_x(any no.) .
but these two files are not being created inside the index folder.
that's why it is throwing the exception message:
no segments* file found in [EMAIL PROT
