Benson Margulies
2012-03-06, 13:50
Uwe Schindler
2012-03-06, 13:56
Benson Margulies
2012-03-06, 14:14
Uwe Schindler
2012-03-06, 14:34
Benson Margulies
2012-03-06, 14:39
Uwe Schindler
2012-03-06, 14:46
Benson Margulies
2012-03-06, 14:59
Benson Margulies
2012-03-06, 14:16
Michael McCandless
2012-03-06, 14:09
Benson Margulies
2012-03-06, 14:18
Benson Margulies
2012-03-06, 14:19
-
A little more CHANGES.txt help on terms(), pleaseBenson Margulies 2012-03-06, 13:50
Under "LUCENE-1458, LUCENE-2111: Flexible Indexing", CHANGES.txt
appears to be missing one critical hint. If you have existing code
that called IndexReader.terms(), where do you start to get a
FieldsEnum?
---------------------------------------------------------------------
appears to be missing one critical hint. If you have existing code
that called IndexReader.terms(), where do you start to get a
FieldsEnum?
---------------------------------------------------------------------
+
Benson Margulies 2012-03-06, 13:50
-
RE: A little more CHANGES.txt help on terms(), pleaseUwe Schindler 2012-03-06, 13:56
AtomicReader.fields()
-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: [EMAIL PROTECTED]
> -----Original Message-----
> From: Benson Margulies [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, March 06, 2012 2:50 PM
> To: [EMAIL PROTECTED]
> Subject: A little more CHANGES.txt help on terms(), please
>
> Under "LUCENE-1458, LUCENE-2111: Flexible Indexing", CHANGES.txt appears
> to be missing one critical hint. If you have existing code that called
> IndexReader.terms(), where do you start to get a FieldsEnum?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: [EMAIL PROTECTED]
> -----Original Message-----
> From: Benson Margulies [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, March 06, 2012 2:50 PM
> To: [EMAIL PROTECTED]
> Subject: A little more CHANGES.txt help on terms(), please
>
> Under "LUCENE-1458, LUCENE-2111: Flexible Indexing", CHANGES.txt appears
> to be missing one critical hint. If you have existing code that called
> IndexReader.terms(), where do you start to get a FieldsEnum?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
+
Uwe Schindler 2012-03-06, 13:56
-
Re: A little more CHANGES.txt help on terms(), pleaseBenson Margulies 2012-03-06, 14:14
On Tue, Mar 6, 2012 at 8:56 AM, Uwe Schindler <[EMAIL PROTECTED]> wrote:
> AtomicReader.fields()
I went and read up AtomicReader in CHANGES.txt. Should I call
SegmentReader.getReader(IOContext)?
I just posted a patch to CHANGES.txt to clarify before I read your
email, shall I improve it to use this instead of
MultiFields.getFields(indexReader).iterator();
which I came up with by fishing around for myself?
>
> -----
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: [EMAIL PROTECTED]
>
>
>> -----Original Message-----
>> From: Benson Margulies [mailto:[EMAIL PROTECTED]]
>> Sent: Tuesday, March 06, 2012 2:50 PM
>> To: [EMAIL PROTECTED]
>> Subject: A little more CHANGES.txt help on terms(), please
>>
>> Under "LUCENE-1458, LUCENE-2111: Flexible Indexing", CHANGES.txt appears
>> to be missing one critical hint. If you have existing code that called
>> IndexReader.terms(), where do you start to get a FieldsEnum?
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
> AtomicReader.fields()
I went and read up AtomicReader in CHANGES.txt. Should I call
SegmentReader.getReader(IOContext)?
I just posted a patch to CHANGES.txt to clarify before I read your
email, shall I improve it to use this instead of
MultiFields.getFields(indexReader).iterator();
which I came up with by fishing around for myself?
>
> -----
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: [EMAIL PROTECTED]
>
>
>> -----Original Message-----
>> From: Benson Margulies [mailto:[EMAIL PROTECTED]]
>> Sent: Tuesday, March 06, 2012 2:50 PM
>> To: [EMAIL PROTECTED]
>> Subject: A little more CHANGES.txt help on terms(), please
>>
>> Under "LUCENE-1458, LUCENE-2111: Flexible Indexing", CHANGES.txt appears
>> to be missing one critical hint. If you have existing code that called
>> IndexReader.terms(), where do you start to get a FieldsEnum?
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
+
Benson Margulies 2012-03-06, 14:14
-
RE: A little more CHANGES.txt help on terms(), pleaseUwe Schindler 2012-03-06, 14:34
Hi,
MultiFields should only be used (as it is slow) if you exactly know what you are doing and what the consequences are. There is a change in Lucene 4.0, so you can no longer terms and postings from a top-level (composite) reader. More info is also here: http://goo.gl/lMKTM
Uwe
-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: [EMAIL PROTECTED]
> -----Original Message-----
> From: Benson Margulies [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, March 06, 2012 3:15 PM
> To: [EMAIL PROTECTED]
> Subject: Re: A little more CHANGES.txt help on terms(), please
>
> On Tue, Mar 6, 2012 at 8:56 AM, Uwe Schindler <[EMAIL PROTECTED]> wrote:
> > AtomicReader.fields()
>
> I went and read up AtomicReader in CHANGES.txt. Should I call
> SegmentReader.getReader(IOContext)?
>
> I just posted a patch to CHANGES.txt to clarify before I read your email, shall I
> improve it to use this instead of
>
> MultiFields.getFields(indexReader).iterator();
>
> which I came up with by fishing around for myself?
>
> >
> > -----
> > Uwe Schindler
> > H.-H.-Meier-Allee 63, D-28213 Bremen
> > http://www.thetaphi.de
> > eMail: [EMAIL PROTECTED]
> >
> >
> >> -----Original Message-----
> >> From: Benson Margulies [mailto:[EMAIL PROTECTED]]
> >> Sent: Tuesday, March 06, 2012 2:50 PM
> >> To: [EMAIL PROTECTED]
> >> Subject: A little more CHANGES.txt help on terms(), please
> >>
> >> Under "LUCENE-1458, LUCENE-2111: Flexible Indexing", CHANGES.txt
> >> appears to be missing one critical hint. If you have existing code
> >> that called IndexReader.terms(), where do you start to get a FieldsEnum?
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
MultiFields should only be used (as it is slow) if you exactly know what you are doing and what the consequences are. There is a change in Lucene 4.0, so you can no longer terms and postings from a top-level (composite) reader. More info is also here: http://goo.gl/lMKTM
Uwe
-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: [EMAIL PROTECTED]
> -----Original Message-----
> From: Benson Margulies [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, March 06, 2012 3:15 PM
> To: [EMAIL PROTECTED]
> Subject: Re: A little more CHANGES.txt help on terms(), please
>
> On Tue, Mar 6, 2012 at 8:56 AM, Uwe Schindler <[EMAIL PROTECTED]> wrote:
> > AtomicReader.fields()
>
> I went and read up AtomicReader in CHANGES.txt. Should I call
> SegmentReader.getReader(IOContext)?
>
> I just posted a patch to CHANGES.txt to clarify before I read your email, shall I
> improve it to use this instead of
>
> MultiFields.getFields(indexReader).iterator();
>
> which I came up with by fishing around for myself?
>
> >
> > -----
> > Uwe Schindler
> > H.-H.-Meier-Allee 63, D-28213 Bremen
> > http://www.thetaphi.de
> > eMail: [EMAIL PROTECTED]
> >
> >
> >> -----Original Message-----
> >> From: Benson Margulies [mailto:[EMAIL PROTECTED]]
> >> Sent: Tuesday, March 06, 2012 2:50 PM
> >> To: [EMAIL PROTECTED]
> >> Subject: A little more CHANGES.txt help on terms(), please
> >>
> >> Under "LUCENE-1458, LUCENE-2111: Flexible Indexing", CHANGES.txt
> >> appears to be missing one critical hint. If you have existing code
> >> that called IndexReader.terms(), where do you start to get a FieldsEnum?
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
+
Uwe Schindler 2012-03-06, 14:34
-
Re: A little more CHANGES.txt help on terms(), pleaseBenson Margulies 2012-03-06, 14:39
On Tue, Mar 6, 2012 at 9:34 AM, Uwe Schindler <[EMAIL PROTECTED]> wrote:
> Hi,
>
> MultiFields should only be used (as it is slow) if you exactly know what you are doing and what the consequences are. There is a change in Lucene 4.0, so you can no longer terms and postings from a top-level (composite) reader. More info is also here: http://goo.gl/lMKTM
Uwe,
The 4.0 change is how I got here in the first place. Some code we have
here dumped all the terms using the old IndexReader.terms(), so I was
working on figuring out how to replace it. For my purposes, which are
a dev tool, I think that MultiFields will be fine.
--benson
>
> Uwe
>
> -----
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: [EMAIL PROTECTED]
>
>
>> -----Original Message-----
>> From: Benson Margulies [mailto:[EMAIL PROTECTED]]
>> Sent: Tuesday, March 06, 2012 3:15 PM
>> To: [EMAIL PROTECTED]
>> Subject: Re: A little more CHANGES.txt help on terms(), please
>>
>> On Tue, Mar 6, 2012 at 8:56 AM, Uwe Schindler <[EMAIL PROTECTED]> wrote:
>> > AtomicReader.fields()
>>
>> I went and read up AtomicReader in CHANGES.txt. Should I call
>> SegmentReader.getReader(IOContext)?
>>
>> I just posted a patch to CHANGES.txt to clarify before I read your email, shall I
>> improve it to use this instead of
>>
>> MultiFields.getFields(indexReader).iterator();
>>
>> which I came up with by fishing around for myself?
>>
>> >
>> > -----
>> > Uwe Schindler
>> > H.-H.-Meier-Allee 63, D-28213 Bremen
>> > http://www.thetaphi.de
>> > eMail: [EMAIL PROTECTED]
>> >
>> >
>> >> -----Original Message-----
>> >> From: Benson Margulies [mailto:[EMAIL PROTECTED]]
>> >> Sent: Tuesday, March 06, 2012 2:50 PM
>> >> To: [EMAIL PROTECTED]
>> >> Subject: A little more CHANGES.txt help on terms(), please
>> >>
>> >> Under "LUCENE-1458, LUCENE-2111: Flexible Indexing", CHANGES.txt
>> >> appears to be missing one critical hint. If you have existing code
>> >> that called IndexReader.terms(), where do you start to get a FieldsEnum?
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> For additional commands, e-mail: [EMAIL PROTECTED]
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> > For additional commands, e-mail: [EMAIL PROTECTED]
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
> Hi,
>
> MultiFields should only be used (as it is slow) if you exactly know what you are doing and what the consequences are. There is a change in Lucene 4.0, so you can no longer terms and postings from a top-level (composite) reader. More info is also here: http://goo.gl/lMKTM
Uwe,
The 4.0 change is how I got here in the first place. Some code we have
here dumped all the terms using the old IndexReader.terms(), so I was
working on figuring out how to replace it. For my purposes, which are
a dev tool, I think that MultiFields will be fine.
--benson
>
> Uwe
>
> -----
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: [EMAIL PROTECTED]
>
>
>> -----Original Message-----
>> From: Benson Margulies [mailto:[EMAIL PROTECTED]]
>> Sent: Tuesday, March 06, 2012 3:15 PM
>> To: [EMAIL PROTECTED]
>> Subject: Re: A little more CHANGES.txt help on terms(), please
>>
>> On Tue, Mar 6, 2012 at 8:56 AM, Uwe Schindler <[EMAIL PROTECTED]> wrote:
>> > AtomicReader.fields()
>>
>> I went and read up AtomicReader in CHANGES.txt. Should I call
>> SegmentReader.getReader(IOContext)?
>>
>> I just posted a patch to CHANGES.txt to clarify before I read your email, shall I
>> improve it to use this instead of
>>
>> MultiFields.getFields(indexReader).iterator();
>>
>> which I came up with by fishing around for myself?
>>
>> >
>> > -----
>> > Uwe Schindler
>> > H.-H.-Meier-Allee 63, D-28213 Bremen
>> > http://www.thetaphi.de
>> > eMail: [EMAIL PROTECTED]
>> >
>> >
>> >> -----Original Message-----
>> >> From: Benson Margulies [mailto:[EMAIL PROTECTED]]
>> >> Sent: Tuesday, March 06, 2012 2:50 PM
>> >> To: [EMAIL PROTECTED]
>> >> Subject: A little more CHANGES.txt help on terms(), please
>> >>
>> >> Under "LUCENE-1458, LUCENE-2111: Flexible Indexing", CHANGES.txt
>> >> appears to be missing one critical hint. If you have existing code
>> >> that called IndexReader.terms(), where do you start to get a FieldsEnum?
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> For additional commands, e-mail: [EMAIL PROTECTED]
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> > For additional commands, e-mail: [EMAIL PROTECTED]
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
+
Benson Margulies 2012-03-06, 14:39
-
RE: A little more CHANGES.txt help on terms(), pleaseUwe Schindler 2012-03-06, 14:46
Hi,
The recommended way to get an atomic reader from a composite reader is to use SlowCompositeReaderWrapper.wrap(reader). MultiFields is now purely internal. I think it's only public because the codecs package may need it, otherwise it should be pkg-private.
-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: [EMAIL PROTECTED]
> -----Original Message-----
> From: Benson Margulies [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, March 06, 2012 3:40 PM
> To: [EMAIL PROTECTED]
> Subject: Re: A little more CHANGES.txt help on terms(), please
>
> On Tue, Mar 6, 2012 at 9:34 AM, Uwe Schindler <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > MultiFields should only be used (as it is slow) if you exactly know
> > what you are doing and what the consequences are. There is a change in
> > Lucene 4.0, so you can no longer terms and postings from a top-level
> > (composite) reader. More info is also here: http://goo.gl/lMKTM
>
> Uwe,
>
> The 4.0 change is how I got here in the first place. Some code we have here
> dumped all the terms using the old IndexReader.terms(), so I was working on
> figuring out how to replace it. For my purposes, which are a dev tool, I think
> that MultiFields will be fine.
>
> --benson
>
>
> >
> > Uwe
> >
> > -----
> > Uwe Schindler
> > H.-H.-Meier-Allee 63, D-28213 Bremen
> > http://www.thetaphi.de
> > eMail: [EMAIL PROTECTED]
> >
> >
> >> -----Original Message-----
> >> From: Benson Margulies [mailto:[EMAIL PROTECTED]]
> >> Sent: Tuesday, March 06, 2012 3:15 PM
> >> To: [EMAIL PROTECTED]
> >> Subject: Re: A little more CHANGES.txt help on terms(), please
> >>
> >> On Tue, Mar 6, 2012 at 8:56 AM, Uwe Schindler <[EMAIL PROTECTED]> wrote:
> >> > AtomicReader.fields()
> >>
> >> I went and read up AtomicReader in CHANGES.txt. Should I call
> >> SegmentReader.getReader(IOContext)?
> >>
> >> I just posted a patch to CHANGES.txt to clarify before I read your
> >> email, shall I improve it to use this instead of
> >>
> >> MultiFields.getFields(indexReader).iterator();
> >>
> >> which I came up with by fishing around for myself?
> >>
> >> >
> >> > -----
> >> > Uwe Schindler
> >> > H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de
> >> > eMail: [EMAIL PROTECTED]
> >> >
> >> >
> >> >> -----Original Message-----
> >> >> From: Benson Margulies [mailto:[EMAIL PROTECTED]]
> >> >> Sent: Tuesday, March 06, 2012 2:50 PM
> >> >> To: [EMAIL PROTECTED]
> >> >> Subject: A little more CHANGES.txt help on terms(), please
> >> >>
> >> >> Under "LUCENE-1458, LUCENE-2111: Flexible Indexing", CHANGES.txt
> >> >> appears to be missing one critical hint. If you have existing code
> >> >> that called IndexReader.terms(), where do you start to get a FieldsEnum?
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >> >
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> > For additional commands, e-mail: [EMAIL PROTECTED]
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
The recommended way to get an atomic reader from a composite reader is to use SlowCompositeReaderWrapper.wrap(reader). MultiFields is now purely internal. I think it's only public because the codecs package may need it, otherwise it should be pkg-private.
-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: [EMAIL PROTECTED]
> -----Original Message-----
> From: Benson Margulies [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, March 06, 2012 3:40 PM
> To: [EMAIL PROTECTED]
> Subject: Re: A little more CHANGES.txt help on terms(), please
>
> On Tue, Mar 6, 2012 at 9:34 AM, Uwe Schindler <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > MultiFields should only be used (as it is slow) if you exactly know
> > what you are doing and what the consequences are. There is a change in
> > Lucene 4.0, so you can no longer terms and postings from a top-level
> > (composite) reader. More info is also here: http://goo.gl/lMKTM
>
> Uwe,
>
> The 4.0 change is how I got here in the first place. Some code we have here
> dumped all the terms using the old IndexReader.terms(), so I was working on
> figuring out how to replace it. For my purposes, which are a dev tool, I think
> that MultiFields will be fine.
>
> --benson
>
>
> >
> > Uwe
> >
> > -----
> > Uwe Schindler
> > H.-H.-Meier-Allee 63, D-28213 Bremen
> > http://www.thetaphi.de
> > eMail: [EMAIL PROTECTED]
> >
> >
> >> -----Original Message-----
> >> From: Benson Margulies [mailto:[EMAIL PROTECTED]]
> >> Sent: Tuesday, March 06, 2012 3:15 PM
> >> To: [EMAIL PROTECTED]
> >> Subject: Re: A little more CHANGES.txt help on terms(), please
> >>
> >> On Tue, Mar 6, 2012 at 8:56 AM, Uwe Schindler <[EMAIL PROTECTED]> wrote:
> >> > AtomicReader.fields()
> >>
> >> I went and read up AtomicReader in CHANGES.txt. Should I call
> >> SegmentReader.getReader(IOContext)?
> >>
> >> I just posted a patch to CHANGES.txt to clarify before I read your
> >> email, shall I improve it to use this instead of
> >>
> >> MultiFields.getFields(indexReader).iterator();
> >>
> >> which I came up with by fishing around for myself?
> >>
> >> >
> >> > -----
> >> > Uwe Schindler
> >> > H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de
> >> > eMail: [EMAIL PROTECTED]
> >> >
> >> >
> >> >> -----Original Message-----
> >> >> From: Benson Margulies [mailto:[EMAIL PROTECTED]]
> >> >> Sent: Tuesday, March 06, 2012 2:50 PM
> >> >> To: [EMAIL PROTECTED]
> >> >> Subject: A little more CHANGES.txt help on terms(), please
> >> >>
> >> >> Under "LUCENE-1458, LUCENE-2111: Flexible Indexing", CHANGES.txt
> >> >> appears to be missing one critical hint. If you have existing code
> >> >> that called IndexReader.terms(), where do you start to get a FieldsEnum?
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >> >
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> > For additional commands, e-mail: [EMAIL PROTECTED]
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
+
Uwe Schindler 2012-03-06, 14:46
-
Re: A little more CHANGES.txt help on terms(), pleaseBenson Margulies 2012-03-06, 14:59
On Tue, Mar 6, 2012 at 9:46 AM, Uwe Schindler <[EMAIL PROTECTED]> wrote:
> Hi,
>
> The recommended way to get an atomic reader from a composite reader is to use SlowCompositeReaderWrapper.wrap(reader). MultiFields is now purely internal. I think it's only public because the codecs package may need it, otherwise it should be pkg-private.
Oh! I'll rework the patch again, then. I might include some commentary
in MultiFields at all.
>
> -----
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: [EMAIL PROTECTED]
>
>
>> -----Original Message-----
>> From: Benson Margulies [mailto:[EMAIL PROTECTED]]
>> Sent: Tuesday, March 06, 2012 3:40 PM
>> To: [EMAIL PROTECTED]
>> Subject: Re: A little more CHANGES.txt help on terms(), please
>>
>> On Tue, Mar 6, 2012 at 9:34 AM, Uwe Schindler <[EMAIL PROTECTED]> wrote:
>> > Hi,
>> >
>> > MultiFields should only be used (as it is slow) if you exactly know
>> > what you are doing and what the consequences are. There is a change in
>> > Lucene 4.0, so you can no longer terms and postings from a top-level
>> > (composite) reader. More info is also here: http://goo.gl/lMKTM
>>
>> Uwe,
>>
>> The 4.0 change is how I got here in the first place. Some code we have here
>> dumped all the terms using the old IndexReader.terms(), so I was working on
>> figuring out how to replace it. For my purposes, which are a dev tool, I think
>> that MultiFields will be fine.
>>
>> --benson
>>
>>
>> >
>> > Uwe
>> >
>> > -----
>> > Uwe Schindler
>> > H.-H.-Meier-Allee 63, D-28213 Bremen
>> > http://www.thetaphi.de
>> > eMail: [EMAIL PROTECTED]
>> >
>> >
>> >> -----Original Message-----
>> >> From: Benson Margulies [mailto:[EMAIL PROTECTED]]
>> >> Sent: Tuesday, March 06, 2012 3:15 PM
>> >> To: [EMAIL PROTECTED]
>> >> Subject: Re: A little more CHANGES.txt help on terms(), please
>> >>
>> >> On Tue, Mar 6, 2012 at 8:56 AM, Uwe Schindler <[EMAIL PROTECTED]> wrote:
>> >> > AtomicReader.fields()
>> >>
>> >> I went and read up AtomicReader in CHANGES.txt. Should I call
>> >> SegmentReader.getReader(IOContext)?
>> >>
>> >> I just posted a patch to CHANGES.txt to clarify before I read your
>> >> email, shall I improve it to use this instead of
>> >>
>> >> MultiFields.getFields(indexReader).iterator();
>> >>
>> >> which I came up with by fishing around for myself?
>> >>
>> >> >
>> >> > -----
>> >> > Uwe Schindler
>> >> > H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de
>> >> > eMail: [EMAIL PROTECTED]
>> >> >
>> >> >
>> >> >> -----Original Message-----
>> >> >> From: Benson Margulies [mailto:[EMAIL PROTECTED]]
>> >> >> Sent: Tuesday, March 06, 2012 2:50 PM
>> >> >> To: [EMAIL PROTECTED]
>> >> >> Subject: A little more CHANGES.txt help on terms(), please
>> >> >>
>> >> >> Under "LUCENE-1458, LUCENE-2111: Flexible Indexing", CHANGES.txt
>> >> >> appears to be missing one critical hint. If you have existing code
>> >> >> that called IndexReader.terms(), where do you start to get a FieldsEnum?
>> >> >>
>> >> >> ---------------------------------------------------------------------
>> >> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> >> For additional commands, e-mail: [EMAIL PROTECTED]
>> >> >
>> >> >
>> >> > ---------------------------------------------------------------------
>> >> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> > For additional commands, e-mail: [EMAIL PROTECTED]
>> >> >
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> For additional commands, e-mail: [EMAIL PROTECTED]
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> > For additional commands, e-mail: [EMAIL PROTECTED]
>> >
>>
>> --------------------------------
> Hi,
>
> The recommended way to get an atomic reader from a composite reader is to use SlowCompositeReaderWrapper.wrap(reader). MultiFields is now purely internal. I think it's only public because the codecs package may need it, otherwise it should be pkg-private.
Oh! I'll rework the patch again, then. I might include some commentary
in MultiFields at all.
>
> -----
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: [EMAIL PROTECTED]
>
>
>> -----Original Message-----
>> From: Benson Margulies [mailto:[EMAIL PROTECTED]]
>> Sent: Tuesday, March 06, 2012 3:40 PM
>> To: [EMAIL PROTECTED]
>> Subject: Re: A little more CHANGES.txt help on terms(), please
>>
>> On Tue, Mar 6, 2012 at 9:34 AM, Uwe Schindler <[EMAIL PROTECTED]> wrote:
>> > Hi,
>> >
>> > MultiFields should only be used (as it is slow) if you exactly know
>> > what you are doing and what the consequences are. There is a change in
>> > Lucene 4.0, so you can no longer terms and postings from a top-level
>> > (composite) reader. More info is also here: http://goo.gl/lMKTM
>>
>> Uwe,
>>
>> The 4.0 change is how I got here in the first place. Some code we have here
>> dumped all the terms using the old IndexReader.terms(), so I was working on
>> figuring out how to replace it. For my purposes, which are a dev tool, I think
>> that MultiFields will be fine.
>>
>> --benson
>>
>>
>> >
>> > Uwe
>> >
>> > -----
>> > Uwe Schindler
>> > H.-H.-Meier-Allee 63, D-28213 Bremen
>> > http://www.thetaphi.de
>> > eMail: [EMAIL PROTECTED]
>> >
>> >
>> >> -----Original Message-----
>> >> From: Benson Margulies [mailto:[EMAIL PROTECTED]]
>> >> Sent: Tuesday, March 06, 2012 3:15 PM
>> >> To: [EMAIL PROTECTED]
>> >> Subject: Re: A little more CHANGES.txt help on terms(), please
>> >>
>> >> On Tue, Mar 6, 2012 at 8:56 AM, Uwe Schindler <[EMAIL PROTECTED]> wrote:
>> >> > AtomicReader.fields()
>> >>
>> >> I went and read up AtomicReader in CHANGES.txt. Should I call
>> >> SegmentReader.getReader(IOContext)?
>> >>
>> >> I just posted a patch to CHANGES.txt to clarify before I read your
>> >> email, shall I improve it to use this instead of
>> >>
>> >> MultiFields.getFields(indexReader).iterator();
>> >>
>> >> which I came up with by fishing around for myself?
>> >>
>> >> >
>> >> > -----
>> >> > Uwe Schindler
>> >> > H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de
>> >> > eMail: [EMAIL PROTECTED]
>> >> >
>> >> >
>> >> >> -----Original Message-----
>> >> >> From: Benson Margulies [mailto:[EMAIL PROTECTED]]
>> >> >> Sent: Tuesday, March 06, 2012 2:50 PM
>> >> >> To: [EMAIL PROTECTED]
>> >> >> Subject: A little more CHANGES.txt help on terms(), please
>> >> >>
>> >> >> Under "LUCENE-1458, LUCENE-2111: Flexible Indexing", CHANGES.txt
>> >> >> appears to be missing one critical hint. If you have existing code
>> >> >> that called IndexReader.terms(), where do you start to get a FieldsEnum?
>> >> >>
>> >> >> ---------------------------------------------------------------------
>> >> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> >> For additional commands, e-mail: [EMAIL PROTECTED]
>> >> >
>> >> >
>> >> > ---------------------------------------------------------------------
>> >> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> > For additional commands, e-mail: [EMAIL PROTECTED]
>> >> >
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> For additional commands, e-mail: [EMAIL PROTECTED]
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> > For additional commands, e-mail: [EMAIL PROTECTED]
>> >
>>
>> --------------------------------
+
Benson Margulies 2012-03-06, 14:59
-
Re: A little more CHANGES.txt help on terms(), pleaseBenson Margulies 2012-03-06, 14:16
Oh, ouch, there's no SegmentReader.getReader, I was reading IndexWriter. Sorry.
On Tue, Mar 6, 2012 at 9:14 AM, Benson Margulies <[EMAIL PROTECTED]> wrote:
> On Tue, Mar 6, 2012 at 8:56 AM, Uwe Schindler <[EMAIL PROTECTED]> wrote:
>> AtomicReader.fields()
---------------------------------------------------------------------
On Tue, Mar 6, 2012 at 9:14 AM, Benson Margulies <[EMAIL PROTECTED]> wrote:
> On Tue, Mar 6, 2012 at 8:56 AM, Uwe Schindler <[EMAIL PROTECTED]> wrote:
>> AtomicReader.fields()
---------------------------------------------------------------------
+
Benson Margulies 2012-03-06, 14:16
-
Re: A little more CHANGES.txt help on terms(), pleaseMichael McCandless 2012-03-06, 14:09
I think MIGRATE.txt talks about this?
Mike McCandless
http://blog.mikemccandless.com
On Tue, Mar 6, 2012 at 8:50 AM, Benson Margulies <[EMAIL PROTECTED]> wrote:
> Under "LUCENE-1458, LUCENE-2111: Flexible Indexing", CHANGES.txt
> appears to be missing one critical hint. If you have existing code
> that called IndexReader.terms(), where do you start to get a
> FieldsEnum?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
Mike McCandless
http://blog.mikemccandless.com
On Tue, Mar 6, 2012 at 8:50 AM, Benson Margulies <[EMAIL PROTECTED]> wrote:
> Under "LUCENE-1458, LUCENE-2111: Flexible Indexing", CHANGES.txt
> appears to be missing one critical hint. If you have existing code
> that called IndexReader.terms(), where do you start to get a
> FieldsEnum?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
+
Michael McCandless 2012-03-06, 14:09
-
Re: A little more CHANGES.txt help on terms(), pleaseBenson Margulies 2012-03-06, 14:18
On Tue, Mar 6, 2012 at 9:09 AM, Michael McCandless
<[EMAIL PROTECTED]> wrote:
> I think MIGRATE.txt talks about this?
Yes it does, but it doesn't actually answer the specific question. See
LUCENE-3853 where I added what seems to be missing. If it's somewhere
else in the file I apologize.
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
> On Tue, Mar 6, 2012 at 8:50 AM, Benson Margulies <[EMAIL PROTECTED]> wrote:
>> Under "LUCENE-1458, LUCENE-2111: Flexible Indexing", CHANGES.txt
>> appears to be missing one critical hint. If you have existing code
>> that called IndexReader.terms(), where do you start to get a
>> FieldsEnum?
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
<[EMAIL PROTECTED]> wrote:
> I think MIGRATE.txt talks about this?
Yes it does, but it doesn't actually answer the specific question. See
LUCENE-3853 where I added what seems to be missing. If it's somewhere
else in the file I apologize.
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
> On Tue, Mar 6, 2012 at 8:50 AM, Benson Margulies <[EMAIL PROTECTED]> wrote:
>> Under "LUCENE-1458, LUCENE-2111: Flexible Indexing", CHANGES.txt
>> appears to be missing one critical hint. If you have existing code
>> that called IndexReader.terms(), where do you start to get a
>> FieldsEnum?
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
+
Benson Margulies 2012-03-06, 14:18
-
Re: A little more CHANGES.txt help on terms(), pleaseBenson Margulies 2012-03-06, 14:19
Oh, I see, I didn't read far enough down. Well, the patch still
repairs a bug in the code fragment relative to the Term enumeration.
---------------------------------------------------------------------
repairs a bug in the code fragment relative to the Term enumeration.
---------------------------------------------------------------------
+
Benson Margulies 2012-03-06, 14:19
