Yes cleaning up works...
But not sure how to avoid this happening again??
-Ashish
jonbaer wrote:
>
> Id suggest what someone else mentioned to just do a full clean up of
> the index. Sounds like you might have kill -9 or stopped the process
> manually while indexing (would be only reason f
Id suggest what someone else mentioned to just do a full clean up of
the index. Sounds like you might have kill -9 or stopped the process
manually while indexing (would be only reason for a left over lock).
- Jon
On Mar 11, 2009, at 5:16 AM, Ashish P wrote:
I added single in indexDefault
Erm... can it be you have several processes running on it?
I would start by a cleanup of it all and attempt a simple solr
addition before the xml.
paul
Le 11-mars-09 à 10:16, Ashish P a écrit :
I added single in indexDefaults that made the
error
before go away but now I am getting foll
I added single in indexDefaults that made the error
before go away but now I am getting following error :
Mar 11, 2009 6:12:56 PM org.apache.solr.common.SolrException log
SEVERE: java.io.IOException: Cannot overwrite:
C:\dw-solr\solr\data\index\_1o.fdt
at
org.apache.lucene.store.FSDirect
Thanks man.
I just tried what u suggested but I am getting following error when
performing request
Mar 11, 2009 6:00:28 PM org.apache.solr.update.SolrIndexWriter getDirectory
WARNING: No lockType configured for C:\dw-solr\solr\./data/index/ assuming
'simple'
Mar 11, 2009 6:00:29 PM org.apache.sol
String xml = null;//load the file to the xml string
DirectXmlRequest up = new DirectXmlRequest( "/update", xml );
solrServer.request( up );
On Wed, Mar 11, 2009 at 2:19 PM, Ashish P wrote:
>
> I have an XML file with structure :
>
> ...
> ...
> .
> .
>
>
> It is present on disk on some
