Population fails for cm:created property

Description

When you have a query set with cm:created property the table table is created successfully, when you create a document, the cm_created column will be populated. But when the population is triggered it will fail with the following error:

Environment

None

Activity

Show:
Nana Insaidoo
February 5, 2021, 12:21 PM

After an iteration of PR review, we’ve figured out that it is pointless to edit the population code to cater for auditable properties as these are always selected by the accelerated query

The right changes need to happen in DefaultQuerySetConfigValidator where properties we decide to ignore get filtered out from the QuerySetDetail object that is validated (as of now this happens for any MLText property we detect), and in DBQueryEngineEnterprise where the predicates found in a given query are checked against available query sets to figure out whether they can be accelerated. Here, any auditable predicate that is found in the query will not be considered to determine whether they are supported by a given query set.

Bruno Bossola
January 29, 2021, 9:41 AM

These columns have to be treated differently as they belong to the alf_node table. During the population, a specific select has to be used that loads the data from alf_node rather than look into the node properties.

Bruno Bossola
January 29, 2021, 9:22 AM

From the 150M the ‘created’ is not present in alf_qname:

Done

Assignee

Unassigned

Reporter

Adina Ababei

Labels

None

Regression

None

Bug Priority

Category 2

Delivery Team

Team 5

Release Train

Iver

Sprint

None

Fix versions

Affects versions