[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CMIS-661) Adopt a subset ofLucene Query Parser Syntax
[ http://tools.oasis-open.org/issues/browse/CMIS-661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20962#action_20962 ]
Florent Guillaume commented on CMIS-661:
----------------------------------------
Comment from David Choy of August 3 from CMIS-660 copied below:
As far as I can tell, the Lucene Query Parser Syntax differs from CMIS 1.0 fulltext syntax in at least the following ways:
• Double-quotes are used for phrase.
• Terms that are not separated by a Boolean operator are OR'ed rather than AND'ed.
• Negation is not allowed if there is only one term.
• Character escaping. (CMIS may have to differ in this aspect no matter what so long as the fulltext expression is embedded in a SQL statement.)
Arguments FOR adopting a subset of Lucene syntax:
• Why invent yet another standard for fulltext query? Is our syntax better? Do we have different requirements?
• Compatibility with Lucene would reduce confusion.
• The semantics of the fulltext expression was not defined in v1.0 and we need to fill that hole. Adopting both Lucene's syntax and semantics could be a clean fix, and it would simplify the spec also.
• The Lucene team probably have investigated fulltext query syntax deeper than we have.
• For implementations that use a Lucene engine, syntax conversion for fulltext query would be unnecessary.
• ...
Arguments AGAINST adopting Lucene syntax:
• Backward compatibility with v1.0.
• CMIS fulltext syntax is so simple that compatibility with Lucene is an over-concern.
• Conversion of a CMIS fulltext expression to a Lucene query is trivial.
• ...
> Adopt a subset of Lucene Query Parser Syntax
> --------------------------------------------
>
> Key: CMIS-661
> URL: http://tools.oasis-open.org/issues/browse/CMIS-661
> Project: OASIS Content Management Interoperability Services (CMIS) TC
> Issue Type: Improvement
> Components: Domain Model
> Affects Versions: Proposals for 2.0
> Reporter: David Choy
> Priority: Minor
>
> This is a spin-off from #660 for further discussion and separate tracking. It is likely a v2.0 item.
> The main differences between this Lucene subset and the CMIS v1.0 fulltext capability are summarized in a 3 August comment under #660.
--
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]