Le Samedi 07 Octobre 2006 18:29, Yonik Seeley a écrit :
> While reviewing some of the LazyField code in preparation for Solr support,
> https://issues.apache.org/jira/browse/SOLR-52
> I noticed that the char[] used to read the String data is a member,
> and thus kept around after the data is read a
I think I was modeling it after IndexInput which does a similar thing
when reading in String data to avoid having to reallocate the buffer
unless it is necessary. But you're right, in looking at it now,
there really is no need for it since the LazyField is instantiated
each time it is read
Le Samedi 05 Août 2006 09:54, Nicolas Lalevée a écrit :
> Le Jeudi 3 Août 2006 21:49, Marvin Humphrey a écrit :
> > On Jul 31, 2006, at 8:25 AM, Nicolas Lalevée wrote:
> > > That looks good, but there is one restriction : it have to be per
> > > document.
> >
> > Yes, what I laid out was per-docume
[
http://issues.apache.org/jira/browse/LUCENE-664?page=comments#action_12440759 ]
Grant Ingersoll commented on LUCENE-664:
Doron,
I really like this. It is so much cleaner and easier to read, IMO. I will
commit this tomorrow or Tuesda
CLONE -QueryParser is not applicable for the arguments (String, String,
Analyzer) error in results.jsp when executing search in the browser (demo from
Lucene 2.0)
--
[
http://issues.apache.org/jira/browse/LUCENE-679?page=comments#action_12440785 ]
Ted Cahall commented on LUCENE-679:
---
The original bug (LUCENE-634) shows this as corrected after 2.0.
I downloaded 2.0.1 on 10/06/06 and it was still broken...
[
http://issues.apache.org/jira/browse/LUCENE-679?page=comments#action_12440786 ]
Ted Cahall commented on LUCENE-679:
---
Forgot to mention. I was running RHEL 3.0, tomcat 4.1.31 and JDK 1.4.2_04.
> CLONE -QueryParser is not applicable for the a
demo war: All links returned by results.jsp are "null"
--
Key: LUCENE-680
URL: http://issues.apache.org/jira/browse/LUCENE-680
Project: Lucene - Java
Issue Type: Bug
Components: E
