CMIS query is querying Relationship instead of Type - Naming clash for Alfresco Type and Association

[patquinn00]

Executing this simple query using CMIS Workbench fails:

SELECT * FROM tdm:publicManual
‍‍‍

We get this log output:

Mar 26, 2014 5:11:42 PM org.apache.solr.common.SolrException log
SEVERE: org.apache.chemistry.opencmis.commons.exceptions.CmisInvalidArgumentException: Type is not queryable tdm:publicManual -> R:tdm:publicManual
        at org.alfresco.opencmis.search.CMISQueryParser.buildSource(CMISQueryParser.java:1417)
‍‍‍‍‍

Using CMIS Workbench, I can see that <em>R:tdmublicManual</em> is a cmis:relationship…not a type as I had expected. I can see <em>D:tdmublicManual</em> exists with a Base Type of cmis:document…this is what I want to query on.

Inspecting the model we have a type and relationship with the same name.

   <type name="tdm:publicManual">
      ……
   </type>
   <aspect name="tdm:staged">
      ….
      <associations>
         <association name="tdm:publicManual">
            ……
         </association>
         ……
      </associations>
   </aspect>
‍‍‍‍‍‍‍‍‍‍‍‍‍‍

This model has been deployed in production since mid 2013 with no problems. e.g. Lucene queries work fine, model deploys without error, we can create content of type tdmublicManual and also associations with the name tdmublicManual.

We are just starting to use the CMIS API for new client apps, and this has raised it's head now.

<ul>
<li>
Does anyone know if there a way to request CMIS to explicitly query against the type and not the relationship?
</li>
<li>
Is it a case that our model is inherently flawed, and should be changed, by having a type and relationship with the same name?
</li>
</ul>

Thanks,
Patrick

[patquinn00]

From debugging through the CMISQueryParser, it looks up the Type Definition using the CMIS Dictionary Service (CMISStrictDictionaryService and CMISAbstractDictionaryService) using

findTypeByQueryName(tableName)‍

. tableName is "tdmublicManual"

The dictionary service uses a registry which is mapping names to Type definitions…so more than likely, the mapping of tdmublicManual to the Type named "tdmublicManual" is being overwritten in the Map by the association named "tdmublicManual".

Whether the model is inherently flawed or not, I'm not sure, but certainly the CMIS Query Parser is not compatible with it as it is.
This is looking like an update to the model and a data fix script.

[kaynezhang]

In CMIS Specification a relationship object MAY be queryable,but now alfresco does not support queries for relationship type.
So in my opinion ,you'd better avoid defining an association with same name as a a type.