Reject cm:type in QuerySet file nicely

Description

When a query set file contains cm:type, the error should indicate that it is not needed as we are automatically able to search on the content type and the 5 standard audit properties. Currently the ERROR in the log is

ERROR ... Cannot find id for qname "{http://www.alfresco.org/model/content/1.0}type"

Also check the 5 standard audit properties are handled in a similar way.

Update:

  • Yes I have mixed up cm:type with the one that identifies the document type.

  • That said, should we really get this error if there just happen to be no nodes with the dublincore aspect applied? It is still part of the system’s model.

Environment

None

Activity

Show:
Nana Insaidoo
February 18, 2021, 1:28 AM

The query set only supports properties and aspects. In this scenario cm:type represents the dublicore aspect property which is not defined by default on new installation of the system. You get that error because the associated qname doesn’t exist (yet).

Bruno Bossola
February 18, 2021, 8:29 PM

may we have a sample JSON file we can use to recreate this issue please?

Bruno Bossola
February 18, 2021, 8:45 PM

As discussed on the standup, this happens because even if you have the DublinCore aspect in the system by default, if you do not have any node inserted yet with such property the respective qname is not added to the table.

The proposal is to update the documentation to add:

  • a first example that ALWAYS works, using properties that we know are in a new database (like cm:title)

  • clarify, for the following examples, that if a node with a property is not in the database the denormalisation may fail

No changes to the code, this is now a documentation issue

Bruno Bossola
7 days ago
Edited



A couple of very minor changes, most of it was already there.

Bruno Bossola
7 days ago

Done

Assignee

Unassigned

Reporter

Alan Davis

Labels

None

Regression

None

Bug Priority

Category 2

Delivery Team

Team 5

Release Train

Iver

Sprint

None

Affects versions