On Fri, Jun 25, 2010 at 12:17, Alexander Klimetschek wrote: > in the end, the part in the contains function gets delegated to the > Lucene QueryParser. So, you can use Lucene query syntax in contains, > for example query time boosting like 'myterm^10' (unless it does not > get swallowed by the xpath/sql parser of jackrabbit, like the ~ fuzzy > char). > > Anyways, a colon means in lucene query parser that you search within a > specific field, see [1] at *Fields* > > At the end of that page, it is explained how to escape special chars ( use > \ ) > ... > > [1] http://lucene.apache.org/java/2_4_0/queryparsersyntax.html > > Section 6.7.19 of the JCR 2.0 Specification [2] states that each minus sign, double-quote and blackslash characters within the full-text search expression of a JCR-SQL2's CONTAINS clause must be escaped. However, it also states in the same section:
The grammar and semantics described above defines the *minimal* requirement, meaning that any search string accepted as valid by an implementation must conform to this grammar. An implementation may, however, restrict acceptable search strings further by augmenting this grammar and expanding the semantics appropriately." Thus, requiring ':' characters to be escaped is a non-standard augmentation of Jackrabbit, correct? Is there documentation on the Jackrabbit-specific grammar for the full-text search expression? Best regards, Randall
