[ http://issues.apache.org/jira/browse/JCR-196?page=all ] Marcel Reutegger resolved JCR-196: ----------------------------------
Resolution: Fixed WildcardQuery is now much faster and also works with patterns that match a large range of terms (e.g. a*). - The regexp pattern matcher is reused for term compare operations. - Resolving document id's is done on an unpositioned TermDocs using seek, instead of acquireing an instance for every term that matches. Implemented in revision: 239404 > jcr:like() does not scale well on large value ranges > ---------------------------------------------------- > > Key: JCR-196 > URL: http://issues.apache.org/jira/browse/JCR-196 > Project: Jackrabbit > Type: Improvement > Components: query > Environment: svn revision: 239389 > Reporter: Marcel Reutegger > Assignee: Marcel Reutegger > Priority: Minor > Fix For: 1.0 > > There are two major issues with the current WildcardQuery implementation: > 1) A wildcard expression is restricted to match at most 1024 terms, otherwise > a TooManyClauses exception is thrown. Similar to the RangeQuery issue: JCR-111 > 2) The enumeration over the terms that match the wildcard pattern is slow -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira