Hello,
I am trying to weigh some ideas for implementing paged search functionality
in our system, which has these basic requirements:
- Using Solr is not an option (at the moment).
- Any Lucene 4.x version can be used.
- Result pagination is driven by the user application code.
- User
On Thu, Oct 10, 2013 at 2:19 PM, Benson Margulies wrote:
> Profile shows a lot of time in org.apache.lucene.search.BooleanScorer$
> BooleanScorerCollector.collect(int).
Ahh, that. We tried to optimize it in LUCENE-4366 but could not get
clear gains...
It's expected to be a hotspot: it "folds
On Wed, Oct 9, 2013 at 7:18 PM, Michael McCandless <
luc...@mikemccandless.com> wrote:
> On Wed, Oct 9, 2013 at 7:13 PM, Benson Margulies
> wrote:
> > On Tue, Oct 8, 2013 at 5:50 PM, Michael McCandless <
> > luc...@mikemccandless.com> wrote:
> >
> >> DirectPostingsFormat?
> >>
> >> It stores all
Are there any best practices for constructing Filters to search efficiently?
From my non-exhaustive experiments I cannot intuit how to construct my filters
to achieve best performance.
I have an index (Lucene 4.3) of about 1.8M documents which contain a field
acting as a flag (evidence:true). Init
Hi,
I have implemented Lucene to search for a single keyword across multiple fields
and it works great. I did this by concatenating all the fields into a
"contents" field and searching against this field.
When I give multiple keywords against this setup, Lucene by default does an OR
search, le
On Thu, 2013-10-10 at 16:02 +0530, Devi pulaparti wrote:
> toString output by queryparser.parse() for query TEST && USAGE is "
> content:TEST content:\"amp amp\" content:USAGE " .
> and for query TEST AND USAGE is "+content:TEST +content:USAGE"
> any idea why is analyzer treating && as conten
Looks like you've got some XML processing in there somewhere. Nothing
to do with lucene. This code:
public static void main(String[] _args) throws Exception {
QueryParser qp = new QueryParser(Version.LUCENE_44,
"x",
new StandardAnalyzer(Version.LUCENE_44));
for (String s : _args) {
System
toString output by queryparser.parse() for query TEST && USAGE is "
content:TEST content:\"amp amp\" content:USAGE " .
and for query TEST AND USAGE is "+content:TEST +content:USAGE"
any idea why is analyzer treating && as content?
On Thu, Oct 10, 2013 at 2:50 PM, Alan Burlison wrote:
> O
On 10/10/2013 09:27, Devi pulaparti wrote:
In our search application, queries like test && usage do not return
correct results but test AND usage works fine. So queries with "&&"
doesn't work but "AND" does. We are using default queryparser with standard
analyzer. Could some one please help
In our search application, queries like test && usage do not return
correct results but test AND usage works fine. So queries with "&&"
doesn't work but "AND" does. We are using default queryparser with standard
analyzer. Could some one please help me resolving this. please let me know
if you n
10 matches
Mail list logo