[
https://jira.nuxeo.com/browse/CMIS-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Carsique updated CMIS-26:
--------------------------------
Component/s: CMIS
> Make it possible to use the CONTAINS predicate on non-default fulltext indexes
> ------------------------------------------------------------------------------
>
> Key: CMIS-26
> URL: https://jira.nuxeo.com/browse/CMIS-26
> Project: Nuxeo Chemistry
> Issue Type: New Feature
> Components: CMIS
> Affects Versions: opencmis-0.1.0
> Reporter: Olivier Grisel
> Assignee: Florent Guillaume
> Priority: Major
> Fix For: nuxeo-5.4.2
>
>
> Nuxeo offers several configurable fulltext indexes:
> - defaul that aggregates all text data related to a given document (text
> fields and binary text extractions)
> - title that indexes only the tokens from the dc:title field
> - other administrator defined indexes in default-repository-config.xml
> Nuxeo services might want to use the CMIS query maker to able to perform JOIN
> queries on the repository while filtering on such custom indexes. The
> proposed change is to make the CMISQueryMaker microparse the prefix of the
> text passed as argument to the CONTAINS predicate to select the right index
> in Nuxeo without having to change the grammar of the CMIS SQL language.
> Hence SELECT dc:title FROM cmis:document WHERE CONTAINS('nx:title:some tokens
> to search for') will restrict the search to the "title" custom index, while
> SELECT dc:title FROM cmis:document WHERE CONTAINS('some tokens to search
> for') will use the "default" fulltext index.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
ECM-tickets@lists.nuxeo.com
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
