[
https://issues.apache.org/jira/browse/CMIS-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15865917#comment-15865917
]
Florian Müller commented on CMIS-1012:
--------------------------------------
The CMIS extension "Query on Secondary Type" allows the use of a plain
secondary type in the FROM clause. The query result can be a mix of different
types and even different base types.
This is similar to the result of getChildren. The property filter passed to
getChildren can contain properties that don't exist for all types. The server
must ignore all properties that don't applied to an object. For example, if the
property cmis:contentStreamLength is part of the filter, a folder object should
just ignore this property.
Unfortunately, neither the spec nor the extension document is very clear about
this detail. But relaxing the query parser doesn't hurt.
> OpenCMIS query parser does not allow selecting secondary properties in simple
> queries
> -------------------------------------------------------------------------------------
>
> Key: CMIS-1012
> URL: https://issues.apache.org/jira/browse/CMIS-1012
> Project: Chemistry
> Issue Type: Bug
> Components: opencmis-server
> Affects Versions: OpenCMIS 1.0.0
> Reporter: Jens Hübel
> Priority: Minor
>
> The query parser in OpenCMIS allows only to select properties which are part
> of a type that is mentioned in a FROM or JOIN statement. It is not possible
> to retrieve properties from secondary types when doing a simple query on a
> primary type (unless you use SELECT *).
> Example:
> SELECT cmis:name, cmis:objectId, mySecondaryProperty FROM cmis:document WHERE
> cmis:createdBy = 'joe'
> fails to parse with
> mySecondaryProperty is not a property query name in any of the types in from
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
