Process "noderef" in accelerated engine

Description

If a query contains in criteria a noderef expression then such query could be accelerated as the noderef is resolved early in the query accelerator. Please make sure this corner case is handled, and a noderef does not exclude the table to be accelerated.

Environment

None

Activity

Show:
Nana Insaidoo
7 days ago
Edited

The noderef is given by protocol + store + uuid, eg. "workspace://SpacesStore/ed538bd3-b18a-4611-edca-d04a3482128". As the noderef and the uuid point to the same node with a unique dbid, we decided that whatever is going to be done to process the noderef at the query engine level should be done for the dbid and the uuid too.

 

At the moment it is not possible to query the noderef and the dbid, respective queries fail to execute in general:

So for there are no further changes to apply to the query engine as far as noderef and dbid.

Querying the uuid works

and there may be some work to do on the query engine to ensure the query predicate does not prevent a query to be accelerate.

Nana Insaidoo
6 days ago

The uuid query predicate doesn’t prevent an eligible query to be accelerated. In the resulting SQL query this predicate resolves to the column “node.uuid”.

Given a compatible query set the following query is accelerated as it should. No changes are needed as the accelerated query template already selects the column node.uuid.

Done

Assignee

Unassigned

Reporter

Bruno Bossola

Labels

None

Regression

None

Bug Priority

Category 2

Delivery Team

Team 5

Release Train

None

Sprint

None

Affects versions