Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <4AAE5E63.5040601@lexum.umontreal.ca>
Date: Mon, 14 Sep 2009 11:16:51 -0400
From: Daniel Shane <shaned@LEXUM.UMontreal.CA>
User-Agent: Thunderbird 2.0.0.19 (X11/20081216)
MIME-Version: 1.0
To: java-dev@lucene.apache.org
Subject: Re: NumericRange Field and LuceneUtils?
References: <9ac0c6aa0909111132s69804fa5vbf5590ea6181ef7a@mail.gmail.com>
 <4AAA9E83.6090202@lexum.umontreal.ca> <6869825E6B56402F8FFB1EF79BEDD02C@VEGA>
 <AAC3D5A8E1F74B98B7682F07A2B4EE74@VEGA>
 <c68e39170909111354i5a9589b7wa865a48b1f5c9df6@mail.gmail.com>
 <6BA66EC75497437298384200755D2F60@VEGA>
In-Reply-To: <6BA66EC75497437298384200755D2F60@VEGA>
Content-Type: multipart/alternative;
 boundary="------------000800040002010200030605"

--------------000800040002010200030605
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Sorry for all the confusion, indeed, the LuceneUtils class I was talking 
about is not in the Lucene distro, so I'd like to appologize if I wasted 
anyones time on this... *guilt*.

I'll second Yonik in thinking that maybe getField() is a bit broken 
since it may lead to class cast exceptions, even though the JavaDoc says 
not to use it with lazy loading fields.

Daniel Shane

Uwe Schindler wrote:
>> On Fri, Sep 11, 2009 at 4:45 PM, Uwe Schindler <uwe@thetaphi.de> wrote:
>>     
>>> By the way: This is documented:
>>> http://hudson.zones.apache.org/hudson/job/Lucene-
>>>       
>> trunk/javadoc/core/org/apac
>>     
>>> he/lucene/document/NumericField.html
>>>
>>> NOTE: This class is only used during indexing. When retrieving the
>>>       
>> stored
>>     
>>> field value from a Document instance after search, you will get a
>>> conventional Fieldable instance where the numeric values are returned as
>>> Strings (according to toString(value) of the used data type).
>>>
>>> (this o.a.l.document.Fieldable is always a o.a.l.document.Field)
>>>       
>> Lazy loading could return a different implementation.  Even w/o lazy
>> loading, we're also not going to guarantee that a Fieldable is always
>> a Field, right?  Perhaps those methods returning a Field should be
>> deprecated sometime.
>>     
>
> Yes. But this is not related to NumericField at all. But it would provide us
> the possibility to return also NumericField instances from stored fields
> some time in future.
>
> Uwe
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-dev-help@lucene.apache.org
>
>   


--------------000800040002010200030605
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Sorry for all the confusion, indeed, the LuceneUtils class I was
talking about is not in the Lucene distro, so I'd like to appologize if
I wasted anyones time on this... *guilt*. <br>
<br>
I'll second Yonik in thinking that maybe getField() is a bit broken
since it may lead to class cast exceptions, even though the JavaDoc
says not to use it with lazy loading fields.<br>
<br>
Daniel Shane<br>
<br>
Uwe Schindler wrote:
<blockquote cite="mid:6BA66EC75497437298384200755D2F60@VEGA" type="cite">
  <blockquote type="cite">
    <pre wrap="">On Fri, Sep 11, 2009 at 4:45 PM, Uwe Schindler <a class="moz-txt-link-rfc2396E" href="mailto:uwe@thetaphi.de">&lt;uwe@thetaphi.de&gt;</a> wrote:
    </pre>
    <blockquote type="cite">
      <pre wrap="">By the way: This is documented:
<a class="moz-txt-link-freetext" href="http://hudson.zones.apache.org/hudson/job/Lucene">http://hudson.zones.apache.org/hudson/job/Lucene</a>-
      </pre>
    </blockquote>
    <pre wrap="">trunk/javadoc/core/org/apac
    </pre>
    <blockquote type="cite">
      <pre wrap="">he/lucene/document/NumericField.html

NOTE: This class is only used during indexing. When retrieving the
      </pre>
    </blockquote>
    <pre wrap="">stored
    </pre>
    <blockquote type="cite">
      <pre wrap="">field value from a Document instance after search, you will get a
conventional Fieldable instance where the numeric values are returned as
Strings (according to toString(value) of the used data type).

(this o.a.l.document.Fieldable is always a o.a.l.document.Field)
      </pre>
    </blockquote>
    <pre wrap="">Lazy loading could return a different implementation.  Even w/o lazy
loading, we're also not going to guarantee that a Fieldable is always
a Field, right?  Perhaps those methods returning a Field should be
deprecated sometime.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Yes. But this is not related to NumericField at all. But it would provide us
the possibility to return also NumericField instances from stored fields
some time in future.

Uwe


---------------------------------------------------------------------
To unsubscribe, e-mail: <a class="moz-txt-link-abbreviated" href="mailto:java-dev-unsubscribe@lucene.apache.org">java-dev-unsubscribe@lucene.apache.org</a>
For additional commands, e-mail: <a class="moz-txt-link-abbreviated" href="mailto:java-dev-help@lucene.apache.org">java-dev-help@lucene.apache.org</a>

  </pre>
</blockquote>
<br>
</body>
</html>

--------------000800040002010200030605--