tree 70d2fa0444f44161550c0d88226c22ba52d6be12
parent 0e3f06c86412801c9fa02bbf099620693e97df9c
author Xikui Wang <xkkwww@gmail.com> 1599157677 -0700
committer Dmitry Lychagin <dmitry.lychagin@couchbase.com> 1599176725 +0000

[ASTERIXDB-2771][*DB] Enabling LSM filters on datasets with meta records

- user model changes: no
- storage format changes: no
- interface changes: no

Details:
This patch enables LSM filters on datasets with meta records. It
introduces a filterSourceIndicator that indicates where the filter value
comes from, (null - no filter, 0 - from the record, 1 - from the meta
record). In LangExpressionToPlanTranslator, filter and meta handling
are pushed into the translate(Insert/Upsert/Delete) methods separately.
Currently, only UPSERTs are allowed on datasets with meta records, and
only in this case, the filter value may come from the meta records.
This patch also renamed an existing test case with where on change feed
to avoid confuison. Legacy datasets without filterSourceIndicator will
have 0 (pointing to record) by default.

Change-Id: I6189169cafab9d99b8662ec91cbdd801cfae9dba
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/7647
Integration-Tests: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Reviewed-by: Ali Alsuliman <ali.al.solaiman@gmail.com>