Hi Michael,
Are you subscribed to the lucene-net-dev@ list? You posting didn't make it.
I will approve this one, but you should check your subscription status (make
sure you used the same email for your posting as for your subscription).
Regards,
-- George
-----Original Message-----
From:
lucene-net-dev-reject-1255372812.87094.cnlopgbjkljdlajjn...@incubator.apache
.org
[mailto:lucene-net-dev-reject-1255372812.87094.cnlopgbjkljdlajjn...@incubato
r.apache.org]
Sent: Monday, October 12, 2009 2:40 PM
To: Recipient list not shown:
Cc:
lucene-net-dev-allow-tc.1255372812.ghhcbeiegahhonkbflkd-mgarski=myspace-inc.
[email protected]
Subject: MODERATE for [email protected]
To approve:
lucene-net-dev-accept-1255372812.87094.cnlopgbjkljdlajjn...@incubator.apache
.org
To reject:
lucene-net-dev-reject-1255372812.87094.cnlopgbjkljdlajjn...@incubator.apache
.org
To give a reason to reject:
%%% Start comment
%%% End comment
--- Begin Message ---
S�rgio,
What is the stack trace on that exception? That will help point to where in
the optimize process the issue is occurring.
I noticed similar behavior during an optimization on a large index on 1.9 & 2.0
only when term vectors were enabled. As I didn't really need term vectors I
disabled them and then everything was fine. With version 2.3 and beyond I have
not encountered any issues during an optimize when term vectors were enabled
(we use them for faceting and a few other things). I'd suggest going with a
newer version of Lucene.Net in a test environment to see if it is reproducible
there.
Michael
-----Original Message-----
From: S�rgio Ara�jo (JIRA) [mailto:[email protected]]
Sent: Monday, October 12, 2009 9:52 AM
To: [email protected]
Subject: [jira] Created: (LUCENENET-195) IndexWriter.Optimize(); return an
exception
IndexWriter.Optimize(); return an exception
-------------------------------------------
Key: LUCENENET-195
URL: https://issues.apache.org/jira/browse/LUCENENET-195
Project: Lucene.Net
Issue Type: Bug
Environment: Framework 1.1 .NET
Reporter: S�rgio Ara�jo
We are using the Lucene search engine a couple of months, on the first approach
seems a very good and high-performance engine.
We are using the your "Lucene.net.dll"API version 2.0.0.4.
We have an index with 20GB approximately, all hours are added news docs to
index and a time per day the optimization is done at 9 pm.
During a couple of days everything ran fine even a day that optimization
process "writer.Optimize();" return the following exception:
"Source array was not long enough. Check srcIndex and length, and the array�s
lower bounds."
Here you can find some parts of my code:
Document doc; doc = null;
IndexWriter writer; writer = null;
writer = new IndexWriter(strArticleIndexFolder, new StandardAnalyzer(), isNew);
writer.SetMergeFactor(1000);
writer.SetMaxMergeDocs(10000);
foreach (ArticleIndexFull objArticleIndex in lstArticleIndexFull)
{
doc = new Document();
doc.Add(newField(O4kFreeSearchTag.ArticleLuceneId,objArticleIndex.ArticleIndexFullId.ToString(),
Field.Store.YES, Field.Index.TOKENIZED, Field.TermVector.YES));
doc.Add(newField(O4kFreeSearchTag.ArticleId,objArticleIndex.ArticleId.ToString(),Field.Store.YES,
Field.Index.TOKENIZED, Field.TermVector.YES));
doc.Add(newField(O4kFreeSearchTag.ProductionDate,FactoryBLL.ArticleIndex.ClearCharStream(AlphaNumeric.ConvertToString(objArticleIndex.ProductionDate.ToString("yyyyMMdd",System.Globalization.CultureInfo.GetCultureInfo("en-US")),String.Empty)),Field.Store.NO,
Field.Index.TOKENIZED, Field.TermVector.YES));
....
writer.AddDocument(doc);
}
if (System.DateTime.Now.Hour == 21)
{
writer.Optimize();
}
writer.Close();
If we migrate to last version available in this case the 2.4.3 my problem will
be fixed?
Has my code any kind of problem?
We will appreciate your help.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
--- End Message ---
