+1
On 07/08/2012 1:44 PM, Prescott Nasser wrote:
Hey All,
This is the first step for graduation for the Apache Lucene.Net project
(incubating of course..). We're taking a vote for the Lucene.Net community to
see if the community is ready to govern itself as a top level project.
Here is a
n Tue, Nov 29, 2011 at 2:59 PM, Trevor Watson <
powersearchsoftw...@gmail.com> wrote:
> I can send you the dll that I am using if you would like. The documents
> are _mostly_ small documents. Emails and office docs size of plain text
>
>
> On Tuesday, November 29, 2011, Chr
n the analyzer itself?
On Tue, Nov 29, 2011 at 12:16 PM, Trevor Watson <
powersearchsoftw...@gmail.com> wrote:
> I don't recall seeing a close function on the analyzer. But I will
> definitely take a look. Thanks!
>
>
> On Tuesday, November 29, 2011, Oren Eini (Ayend
27;m trying to find a copy of 2.9.2 to see if I can reproduce it.
>
>
> Thanks,
> Christopher
>
> On Tue, Nov 29, 2011 at 9:11 AM, Trevor Watson <
> powersearchsoftw...@gmail.com> wrote:
>
>> Sorry for the duplicate post. I was on the road and posted both via my
w
I replaced the UpdateDocument with the following lines:
iw.DeleteDocuments(new Lucene.Net.Index.Term("FileId",
this.FileID.ToString("0")));
iw.AddDocument(doc, analyzer);
The memory usage still climbs constantly when updating.
I'm using the following block of code. The document is created in another
function and written to the Lucene index via an IndexWriter
private void SaveFileToFileInfo(Lucene.Net.Index.IndexWriter iw, bool
delayCommit, string sDataPath)
{
Document doc = getFileInfoDoc(sDataPath)
tried replacing it with a deleteDocument and AddDocument and the
memory increased the same as using the UpdateDocument function
The getAnalyzer() function returns a ExtendedStandardAnalyzer, but it's the
UpdateDocument line specifically that gives me the issue.
Any assistance would be greatly appreciated.
Trevor Watson
