[ 
https://issues.apache.org/jira/browse/ASTERIXDB-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17771528#comment-17771528
 ] 

ASF subversion and git services commented on ASTERIXDB-3274:
------------------------------------------------------------

Commit 2edb32d743b2e9b4a5529fa7a0ae88907e3a718d in asterixdb's branch 
refs/heads/master from Wail Alkowaileet
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=2edb32d743 ]

[ASTERIXDB-3273][ASTERIXDB-3274][RT] Value embedder fixes

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

Details:
- Fix class exception issue when going more than 3 level
  deep when parsing nested values.
- Fix the issue when replacing nested values with
  scalar values.

Change-Id: I7c4f67deaf984132c3dfefc1bb7bbf894ce8a01c
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/17830
Integration-Tests: Jenkins <[email protected]>
Reviewed-by: Wail Alkowaileet <[email protected]>
Reviewed-by: Hussain Towaileb <[email protected]>
Tested-by: Jenkins <[email protected]>


> Nested values should be skipped when replaced with an external embedded value
> -----------------------------------------------------------------------------
>
>                 Key: ASTERIXDB-3274
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-3274
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: RT - Runtime
>    Affects Versions: 0.9.9
>            Reporter: Wail Y. Alkowaileet
>            Assignee: Wail Y. Alkowaileet
>            Priority: Major
>             Fix For: 0.9.9
>
>
> DDL:
> {noformat}
> CREATE TYPE TestType AS {
> };
> CREATE EXTERNAL DATASET Name(TestType) USING %adapter% (
>     %template%,
>     ("container"="playground"),
>     ("definition"="external-filter/embed/name/{name:string}"),
>     ("embed-filter-values" = "true"),
>     ("format"="json")
> );{noformat}
>  
> Sample data in external-filter/embed/name/{*}Jones{*}:
> {noformat}
> {"id": 1, "name": {"first": "Mike", "last": "Jones"}, "department": 
> "accounting"}
> {"id": 2, "name": {"first": "Alice"},"department": "engineering"}
> {"id": 3, "name": null, "department": "hr"} {noformat}
>  
> We can see that the filter value \{name:string} will replace the nested 
> values such as "name": \{"first": "Mike", "last": "Jones"}. Thus, the JSON 
> parser should skip those nested values as it will be replaced by the filter 
> value (i.e., "Jones" as in the example above)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to