I have several related questions about migration, at the file format level.
1. Having gotten my 3.x codebase working with 4.x APIs, is it OK just to
open existing files created by 3.x and keep on indexing? The answer
appears to be yes, with some performance hit, per
http://lucene.apache.org/core
I am seeing a situation with Lucene 3.3.0 where this *may* have happened.
Thanks,
Stu
Problem found. Implementation inheritance + java.lang.Cloneable for the
lose. :-)
Sorry for the noise.
On Mon, Jan 7, 2013 at 5:23 PM, Michael McCandless <
luc...@mikemccandless.com> wrote:
> On Mon, Jan 7, 2013 at 2:34 PM, Stuart Halloway
> wrote:
> > Still no joy isola
of that ring bells?
Stu
On Mon, Jan 7, 2013 at 11:25 AM, Stuart Halloway
wrote:
> Beyond it, and it seems to read after that too. I am re-running the
> (large, cumbersome) test case I have in hand with the infoStream spout
> turned on and will be back with more detail in a bit...
>
Hmm good question!
>
> Are you seeing ConjunctionScorer seek to exactly the end-of-file (ie,
> == length), or beyond it?
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
> On Mon, Jan 7, 2013 at 10:57 AM, Stuart Halloway
> wrote:
> > I have implemente
I have implemented a custom Lucene directory, and I think I am seeing
Lucene's ConjunctionScorer seek off the end of IndexInput, which I have
implemented to throw an exception. One example stack trace leading to this
is:
at org.apache.lucene.index.SegmentTermDocs.skipTo(SegmentTermDocs.java:197)
