On 2011-11-29, Prescott Nasser wrote:
> 1. Move the artifacts to the distribution place (not sure where or how yet)
/www/www.apache.org/dist/incubator/lucene.net/
make sure all files and directories are owned by the group incubator and
group writable. If you create new directories, set the stic
Alright, we've passed the general voting gauntlet. Steps I see are:
1. Move the artifacts to the distribution place (not sure where or how yet)
2. NuGet for those who want it (if anyone is familiar with this, I have only
used Nuget to get packages, not sure how to submit)
3. Update the webs
You need to close the analyzer.
On Tue, Nov 29, 2011 at 12:32 AM, Trevor Watson <
powersearchsoftw...@gmail.com> wrote:
> 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(Lu
Did you mean to create 2 new threads? Also have you read Christopher's
response?
Hi Trevor,
What kind of memory increase are we talking about? Also, how big are the
docum
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)
Hi Trevor,
What kind of memory increase are we talking about? Also, how big are the
documents that you are indexing, the ones returned from getFileInfoDoc()?
Is it putting an entire file into the index? Pre 2.9.3 versions had
issues with holding onto allocated byte arrays far beyond when they w
I'm attempting to use Lucene.Net v2.9.2.2 in a Visual Studio 2005 (.NET
2.0) environment. We had a piece of software that WAS working. I'm not
sure what has changed however, the following code results in a memory leak
in the Lucene.Net component (or a failure to clean up used memory).
The code i
