OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

cmis message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Commented: (CMIS-144) Full text search syntaxand semantics

    [ http://tools.oasis-open.org/issues/browse/CMIS-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10200#action_10200 ] 

Al Brown commented on CMIS-144:

JCR supports: (AND, OR, NOT, Phrases)
- terms separated by space are AND'ed
- terms preceded by '-' are NOT
- terms can be separated by OR

If there is consensus that this is needed (for a usecase in scope), I can live with adding support for AND, OR, NOT and phrases.  I would like to defer this to 2.0.

From JCR:
A query satisfies a FullTextSearch constraint if the value (or values) of the full-text indexed properties within the full-text search scope satisfy the specified fullTextSearchExpression, evaluated as follows:
-	A term not preceded with "-" (minus sign) is satisfied only if the value contains that term.
-	A term preceded with "-" (minus sign) is satisfied only if the value does not contain that term.
-	Terms separated by whitespace are implicitly "ANDed".
-	Terms separated by "OR" are "ORed".
-	"AND" has higher precedence than "OR".
-	Within a term, each double quote ("), "-" (minus sign), and "\" (backslash) must be escaped by a preceding "\" (backslash).
The query is invalid if:
-	selectorName is not the name of a selector in the query, or
-	fullTextSearchExpression does not conform to the above grammar (as augmented by the implementation).

> Full text search syntax and semantics
> -------------------------------------
>                 Key: CMIS-144
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-144
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: Domain Model
>    Affects Versions: Draft 0.6
>            Reporter: David Caruana
>            Assignee: Ethan Gur-esh
> The text search expression is defined as a <character string literal> (as defined by SQL-92).  However, the syntax and semantics of the full text search expression are repo specific.
> I remember there was some resistance to defining a 'lowest common denominator' full text search language, but I don't remember why.
> Given that we define SQL, and that query is a key use case, I think there's value in a deeper FTS definition.
> As a starting point, JCR provides minimal definition. I'm not sure we would need to much further than that to start with.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]