Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ComplexPhraseQueryParser/Enumerating Wildcard Queries #9

Open
GoogleCodeExporter opened this issue Aug 3, 2015 · 3 comments
Open

Comments

@GoogleCodeExporter
Copy link

We are troubleshooting performance issues related to wildcard queries 
running against the ComplexPhraseQueryParser (introduced in Lucene 3.0). 
Some wildcard queries like "quality operations providing quality food 
services job requirements: click here to apply for this job*" require a 
maxClauseCount > 40K to match against the DBSight implementation that 
we're using (and run longer than 2 seconds too).

We'd like to understand what the 40K clauses are as we don't think we have 
nearly that many unique words that have job* as a prefix. 

Can Luke support the ComplexPhraseQueryParser or otherwise show the fully 
enumerated query for wildcard searches? 






Original issue reported on code.google.com by [email protected] on 1 Feb 2010 at 8:20

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant