We are still having the issue where ComplexPhraseQueryParser fails on
quoted expressions that include stop words. Does the original
developer of this class still contribute to Lucene?
On Fri, Oct 26, 2012 at 3:37 PM, Brandon Mintern wrote:
> We recently switched from QueryParser
We recently switched from QueryParser to ComplexPhraseQueryParser
(from lucene-queryparser-3.6.0.jar), and we've come across two
separate problems.
The first is that because it parses quoted expressions twice, it is
necessary to double-escape any escaped characters. So if I do not want
to allow us
On Mon, Apr 23, 2012 at 1:25 PM, Jong Kim wrote:
> Thanks for the reply.
>
> Our metadata is not stored in a single field, but is rather a collection of
> fields. So, it requires a boolean search that spans multiple fields. My
> understanding is that it is not possible to iterate over the matching
Another good reference is this one: http://unicode.org/reports/tr29/
Since the latest Lucene uses this for the basis of its text
segmentation, it's worth getting familiar with it.
On Fri, Mar 30, 2012 at 10:09 AM, Robert Muir wrote:
> On Fri, Mar 30, 2012 at 1:03 PM, Denis Brodeur wrote:
>> Tha
On Tue, Mar 27, 2012 at 12:21 AM, jianwen lou wrote:
> I want to store the long type value to my index files like follwing:
>
> NumericField priceField = new NumericField("price");
> priceField.setDoubleValue(temp.getCurrentprice());
> document.add(pric
Everything that we've read seems to indicate that heavy Lucene users
inevitably write their own Filter streams. We just did this ourselves
a month or two ago, and it really wasn't too bad. Just make sure that
you reference the latest Lucene release when you're writing your own
filter. There's a spl
A QueryParser has to actually parse your text and build up the
BooleanQuery exactly as you do in your second example. Since the
QueryParser is doing extra work that you don't have to do considering
that you already know everything about the query, your second example
is faster.
On Mon, Jan 30, 201
>
>
> On Wed, Dec 7, 2011 at 8:46 PM, Brandon Mintern wrote:
>> We have a document tagging system where documents are composed of two
>> types of data:
>>
>> Rarely changed (hereafter: "immutable") data - document text and
>> metadata that we upl
We have a document tagging system where documents are composed of two
types of data:
Rarely changed (hereafter: "immutable") data - document text and
metadata that we upload and almost never change. The text can be
hundreds of pages.
User created (hereafter: "mutable") data - document properties
