Hi Dan,
java.io.IOException: read past EOF
at org.apache.lucene.store.InputStream.refill(InputStream.java:154)
at org.apache.lucene.store.InputStream.readByte(InputStream.java:43)
at org.apache.lucene.store.InputStream.readBytes(InputStream.java
:57)
at org.apache.luc
: Indeed! I agree - I was temporarily blinded by the desire to hack
: QueryParser itself in perhaps a one-off way that I didn't consider
: the subclassing option.
if all you care about is aliasing term, and phrase queries yiu might even
be able to use the DisjunctionMaxQueryParser i wrote for So
On Jun 4, 2006, at 8:55 PM, Daniel Noll wrote:
Erik Hatcher wrote:
On Jun 4, 2006, at 5:57 PM, karl wettin wrote:
I was thinking it could be nice if the query parser handled
aliases by
passing a Map to the parser. The data could be compiled from the
index.
"name", "nam", "na" and "n" all
Erik Hatcher wrote:
On Jun 4, 2006, at 5:57 PM, karl wettin wrote:
I was thinking it could be nice if the query parser handled aliases by
passing a Map to the parser. The data could be compiled from the index.
"name", "nam", "na" and "n" all trigger on "name", taking there is no
other field st
On Jun 4, 2006, at 5:57 PM, karl wettin wrote:
I was thinking it could be nice if the query parser handled aliases by
passing a Map to the parser. The data could be compiled from the
index.
"name", "nam", "na" and "n" all trigger on "name", taking there is no
other field starting with an "n"
I was thinking it could be nice if the query parser handled aliases by
passing a Map to the parser. The data could be compiled from the index.
"name", "nam", "na" and "n" all trigger on "name", taking there is no
other field starting with an "n".
Did anyone implement this, or should I hack one u
I finally got back to doing my project. HitCollector solved my problem.
Thank you for all the help.
On 5/14/06, Beady Geraghty <[EMAIL PROTECTED]> wrote:
Thank you for the links. I will go through them, and hopefully solve my
problem.
On 5/14/06, Chris Hostetter <[EMAIL PROTECTED]> wrote
