Thanks!

Is there a writeup somewhere describing the differences among the Directory
classes?  The documentation is copy and pasted from the Java version and I
suspect the differences due to JVM peculiarities and such do not really
translate to the .NET world : ).  So how do we chose between these?

Thanks!

Nima

On Fri, Dec 25, 2009 at 4:38 PM, Digy <[email protected]> wrote:

> Hi Nima,
>
> Altought there isn't any official release during the past 2-3 years, many
> Lucene.Net tags are created and these versions are used by many people in
> production environments.
> See https://svn.apache.org/repos/asf/incubator/lucene.net/tags
>
> The latest version in trunk is 2.9.1 and is almost ready.
>
> "NIOFSDirectory" and "MmapDirectory" may be problematic(as you hit one of
> them). If you avoid using them, I don't think that you will face with a
> problem.
>
> DIGY
>
> -----Original Message-----
> From: nima dilmaghani [mailto:[email protected]]
> Sent: Friday, December 25, 2009 9:05 PM
> To: [email protected]
> Subject: byteBuf in NIOFSDirectory.cs is never set
>
> Hello,
>
> I am new here so a please help me understand what is going on.
>
> 1. I see that the release version is over 2 1/2 years old but there has
> been
> significant dev effort.  So for a release product, is the 2 1/2 year old
> version really what is recommended?  If someone is to check out code from
> svn repository to use, is there a build that would be production quality
> and
> not too bleeding edge?
>
> 2. I went with the recommendation from George here:
>
> http://mail-archives.apache.org/mod_mbox/incubator-lucene-net-user/200912.mb
> ox/browser<http://mail-archives.apache.org/mod_mbox/incubator-lucene-net-user/200912.mbox/browser>
>  and
> tried to use the latest code.
>
> When making this call:
>
> indexWriter = new IndexWriter( niopfsDir, a, true,
> IndexWriter.MaxFieldLength.UNLIMITED);
>
> with the latest build (893876)
>
> I get a null reference exception because in NIOFSDirectory.cs byteBuf's
> initialization is commented out.
>
> Thanks and Happy Holidays!
>
> Nima
>
>


-- 
Nima

Reply via email to