Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <4AF45CF0.2020105@deri.org>
References: <4AF45CF0.2020105@deri.org>
Date: Fri, 6 Nov 2009 13:09:09 -0500
Message-ID: <9ac0c6aa0911061009r771021a3i55f849209353fa2c@mail.gmail.com>
Subject: Re: IndexingChain and TermHash
From: Michael McCandless <lucene@mikemccandless.com>
To: java-user@lucene.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

To be honest, you are sort of forging new territory here :)

The intention of TermsHash was to allow a null nextTermsHash.
Hopefully fixing a few places will in fact make it work that way.

EG for this, maybe change (in TermsHashPerThread.java) this:

    if (nextTermsHash !=3D null) {
      // We are primary
      charPool =3D new CharBlockPool(termsHash.docWriter);
      primary =3D true;
    } else {
      charPool =3D primaryPerThread.charPool;
      primary =3D false;
    }

to:

    if (nextTermsHash !=3D null || primaryPerThread =3D=3D null) {
      // We are primary
      charPool =3D new CharBlockPool(termsHash.docWriter);
      primary =3D true;
    } else {
      charPool =3D primaryPerThread.charPool;
      primary =3D false;
    }

?

Mike

On Fri, Nov 6, 2009 at 12:29 PM, Renaud Delbru <renaud.delbru@deri.org> wro=
te:
> Hi,
>
> I am trying to modify the indexing chain of Lucene. To start, I have
> extracted and modified the default indexing chain. I have just removed th=
e
> TermVectorsTermsWriter from the chain, i.e., I instantiate a TermHash wit=
h a
> null 'nextTermsHash'. So, in the chain, my inverted doc consumer looks li=
ke:
>
> =A0final InvertedDocConsumer termsHash =3D new TermsHash(documentsWriter,=
 true,
> freqProxWriter, null);
>
> From looking at the code of TermsHash, it looks like you can pass a null
> value as 'nextTermsHash' parameter. However, I got a NPE during the
> TermsHashPerThread initialisation (line 48, primaryPerThread is null).
>
> Is it a normal behavior ? Do TermHash is always waiting for a non null
> 'nextTermsHash' by design ?
>
> Thanks
> --
> Renaud Delbru
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org