stack-encrypt: JSON operators Contains, ContainedBy and AtPath #1187

Background

ADR-0009 decision 1 adds JSON operators: Contains and ContainedBy (@> and <@), and the accessor AtPath<Op>, which applies another operator at a JSON path. AtPath<Op> inherits the fidelity of its leaf (decision 4).

Problem

stack-encrypt has no JSON index, and EQL v4 has no JSON type that Stack Encrypt produces, so there is nothing for these operators to query.

Proposal

• The operator types Contains, ContainedBy and AtPath<Op>.
• AtPath<Eq> as a value-selector term, and AtPath<Lt> and the other orderings as a selector plus a leaf term, exposed as two parts for the SQL col -> selector < term.
• AtPath<Op> is Probabilistic when Op is, and its verify applies Op at the path of the decrypted document.
• ADR-0009's code matches what this ships.

Blocked by

• A JSON index in stack-encrypt, and EQL v4 Json produced by Stack Encrypt.

Related

• Go SDK: the json index as a stash tag, with one generated query method per form #1061: the Go SDK's JSON index tag.
• stack-encrypt: name the operator, not the index, in a query (Eq and Matches) #1182: the operator-typed query.
• Tracking: implement ADR-0009, operator-typed query terms for Stack Encrypt #1178: tracks ADR-0009.