AQL query processor should ignore data with lifecycle_state = incomplete.
Raise CR
Analysis
Execution
Raise CR
Analysis
Execution
Description
Activity
Show:
Bjørn Næss August 24, 2020 at 9:44 AM
This seems reasonable for us.
Seref Arikan June 15, 2020 at 2:08 PM
this makes sense to me. if everybody agrees this should be the default behaviour, we’re then looking at a section in the spec dedicated to default behaviour, or so I think. We’d need to specify expected behaviour like this and how and under which conditions it would change. What comes to mind is queries retrieving latest versions of compositions for example. It is pretty much the default behaviour across implementations as far as I know but it would be nice to have this specified under a default behaviour section. Based on what and think, we can either open a new issue or create a topic under discourse for discussion.
Details
Details
Created June 15, 2020 at 1:34 PM
Updated January 25, 2021 at 6:45 AM
TBD
Basically: when gathering data for query result, ignore all VERSIONs (of e.g. VERSIONED_COMPOSITIONs) with lifecycle_state=incomplete, unless the query author expresses awareness of presence of incomplete data in results. She does so by referencing v/lifecycle_state attribute (where v is a VERSION) in either SELECT or WHERE part of the query.