Looks good. I would suggest calling out that it's not like some ancient
version of a record might be picked up; it's just that if a small change
is happening concurrently with a (large) index-only query, the proposed
approach doesn't prevent the before-value rather than the after-value of
the concurrent update from being the value used by the query. This is
fine since the AsterixDB guarantee is record-level atomicity (and the
query will either see the before- or after- value, not something in
between). I would also suggest removing the index-only hint from the
writeup; it's hopefully unnecessary and definitely a distraction if so. :-)
On 8/1/25 9:58 AM, Shahrzad Haji Amin Shirazi wrote:
Hi All,
Initiating a discussion to propose the change in index-only
query plans in AsterixDB.
*Feature:*: Simplifying the index-only query plans
*Details:* In the current version of AsterixDB, index-only
query plans are complex and challenging to maintain.
They involve a complex query plan that enforces strict consistency
guarantees. The proposed feature will simplify these plans by
relaxing those guarantees, which would significantly enhance
maintainability and usability.
*Changeset*:https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/17729
*APE*:
https://cwiki.apache.org/confluence/display/ASTERIXDB/APE+24%3A+Index-only+plans
Sincerely,
Shahrzad
