Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
7.1.0
-
1
Description
Currently when specifying the "pattern" option to these functions it is matched against the composite names. To filter against specific individual field names requires multiple expressions to cater for all ways the field name may appear in the composite name.
This is to add ability to limit pattern matching space to individual field names instead of the composite names.
Attachments
| For Gerrit Dashboard: MB-47980 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 159378,4 | MB-47980 Add ability to limit pattern matching space to individual field names. | master | query | Status: MERGED | +2 | +1 |
| 159497,2 | MB-47980 Correct option case. | master | query | Status: MERGED | +2 | +1 |
Activity
Build couchbase-server-7.1.0-1159 contains query commit eaa90b7 with commit message:
MB-47980 Correct option case.
To verify, run a statement such as:
select object_pairs_nested(eg,{"pattern":"^c$"}) from {"a":{"b":{"c":1},"cc":2},"ccc":3} eg;
|
and compare it with:
select object_pairs_nested(eg,{"pattern":"^c$","patternspace":"field"}) from {"a":{"b":{"c":1},"cc":2},"ccc":3} eg;
|
Valid values for "patternspace" are "field" and "path" [edit: was "composite" but a later change revised this] (which is the default if not specified).
Build couchbase-server-7.1.0-1158 contains query commit 30cbf0b with commit message:
MB-47980Add ability to limit pattern matching space to individual field names.