lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Itamar Syn-Hershko <ita...@code972.com>
Subject Re: Lucene.NET 4.8.0 status update
Date Mon, 11 Aug 2014 06:35:29 GMT
The core stuff is all ported (the link that u posted, only for v4.8). I
fixed many of the tests there (will push shortly) but still there are some
that are failing. You want to port new stuff or can you join me in cleaning
up those failures?

--

Itamar Syn-Hershko
http://code972.com | @synhershko <https://twitter.com/synhershko>
Freelance Developer & Consultant
Author of RavenDB in Action <http://manning.com/synhershko/>


On Mon, Aug 11, 2014 at 2:42 AM, Prescott Nasser <geobmx540@hotmail.com>
wrote:

> Itamar, I can't do much with the codecs until the core codec stuff is
> ported over - it is all inherited from that stuff.
>
> Do you want me to switch gears and look at porting that stuff into the
> core library then come back to the separate codecs?
>
> Codecs from core:
> https://github.com/apache/lucene-solr/tree/accd7dad82693669f6845d26deabd7b75e0db4b5/lucene/core/src/java/org/apache/lucene/codecs
>
> > Date: Sat, 9 Aug 2014 20:31:11 +0300
> > Subject: Re: Lucene.NET 4.8.0 status update
> > From: itamar@code972.com
> > To: dev@lucenenet.apache.org
> >
> > Separate project, the way I see it we will have several nuget packages
> and
> > codecs will be one of them, e.g. Lucene.Net, Lucene.Net.TestingFramework,
> > Lucene.Net.Codecs, Lucene.Net.Highlighting etc and then all the contribs
> >
> > BTW after taking a look again it seems many codec related failures are
> from
> > within the core itself and not because of the external codecs support,
> I'll
> > work on that tonight
> >
> > --
> >
> > Itamar Syn-Hershko
> > http://code972.com | @synhershko <https://twitter.com/synhershko>
> > Freelance Developer & Consultant
> > Author of RavenDB in Action <http://manning.com/synhershko/>
> >
> >
> > On Sat, Aug 9, 2014 at 2:14 AM, Prescott Nasser <geobmx540@hotmail.com>
> > wrote:
> >
> > > I will take up the call on codecs - two questions:
> > >
> > > Should I make separate projects for each or one project for all? Move
> > > those to contrib?
> > >
> > > Date: Fri, 8 Aug 2014 06:34:02 +0300
> > > Subject: Lucene.NET 4.8.0 status update
> > > From: itamar@code972.com
> > > To: dev@lucenenet.apache.org
> > >
> > > Hi all.
> > > I've been working on the 4.8 branch to try and stabilize it so it can
> be
> > > the base for our next release. There's still plenty to do, but I was
> able
> > > to make decent progress.
> > >
> > > This thread will be used for me to report progress and hopefully get
> some
> > > more people involved.
> > > My branch is here:
> > > https://github.com/synhershko/lucene.net/tree/Lucene.Net_4.8.0
> > >
> > > Out of about 2300 tests currently, there are about 600 failing tests
> and
> > > the rest are green. At least 300 of the failing tests are due to
> missing
> > > codecs (some codecs haven't been ported yet). The rest of the failures
> can
> > > be largely categorized as below.
> > >
> > > 1. The missing codecs need to be ported (into a separate assembly).
> There
> > > isn't too much of code to port and work is pretty much self contained.
> > > However completing this will make about 300 tests green.
> > > The code to port is here:
> > >
> https://github.com/apache/lucene-solr/tree/lucene_solr_4_8_0/lucene/codecs/src/java/org/apache/lucene/codecs
> > >
> > > 2. Compressed fields implementation is largely broken. Quite a few test
> > > are red and I'm pretty sure the fix is quite simple, just a faulty
> > > implementation to quickly re-write.
> > >
> > > 3. Many, many tests are very slow or even deadlocking because of
> threading
> > > issues. Culprits are both IndexWriter and FSDirectory. This is the most
> > > severe and probably challenging issue to solve.There are multiple
> failures
> > > which I believe relate to this issue. "Access to the path is denied."
> on
> > > index files, failing Asserts etc.
> > >
> > > 4. The fsync implementation (in FSDirectory) needs some love and
> testing.
> > > 5. The rest of the failing tests are probably isolated porting issues
> > > (Java / C# differences or bugs introduced while porting). I attached a
> > > screenshot of one such error, thrown using Debug.Assert from the core
> while
> > > running some of the tests.
> > >
> > > Other items to tackle later:
> > > 1. CLS compliance. Maybe the biggest item there is the byte/sbyte
> thing we
> > > discussed several times before.
> > > 2. Porting the contribs.
> > >
> > > 3. Cleaning up the API and XML comments
> > > 4. Fixing the license header in all source files
> > > 5. CI pipeline and SlowTest attribute to have some tests run only on
> > > nightly builds or similar
> > >
> > > Anyone up for some coding?--
> > > Itamar Syn-Hershkohttp://code972.com | @synhershko
> > >
> > > Freelance Developer & ConsultantAuthor of RavenDB in Action
> > >
> > >
> > >
> > >
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message