Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <94095f520912030846j5c25f0aetdf5a0f4215a04342@mail.gmail.com>
References: <94095f520912030846j5c25f0aetdf5a0f4215a04342@mail.gmail.com>
Date: Thu, 3 Dec 2009 12:13:48 -0500
Message-ID: <9ac0c6aa0912030913n4075a4falab1263ce5e924e6@mail.gmail.com>
Subject: Re: Norm Value of not existing Field
From: Michael McCandless <lucene@mikemccandless.com>
To: java-user@lucene.apache.org
Content-Type: text/plain; charset=ISO-8859-1

This isn't easy to change; it's hardcoded, in oal.index.NormsWriter,
to 1.0, and also in SegmentReader, to 1.0 (when the field doesn't have
norms stored, but eg someone is requesting them anyway).  1.0 must
encode to 124.  I suppose we could empower Similarity to define what
the "undefined norm value" should be?  Wanna make a patch?

Mike

On Thu, Dec 3, 2009 at 11:46 AM, Benjamin Heilbrunn <benhei@gmail.com> wrote:
> Hi,
>
> I'm using Lucene 2.9.1 patched with
> http://issues.apache.org/jira/browse/LUCENE-1260
> For some special reason I need to find all documents which contain at
> least 1 term in a certain field.
> This works by iterating the norms array only as long as the field
> exists on every document.
> For documents without the field the norms array holds the byte-value 124.
> Where does 124 come from - and is there a way to change it to an other
> value like -128 (0xFF) for not existing fields?
>
>
> Benjamin
>
> ---------------------------------------------------------------------
> 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