metamodel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kasper Sørensen (JIRA) <j...@apache.org>
Subject [jira] [Resolved] (METAMODEL-92) ColumnNameAsKeysRowConverter should be able to traverse nested columns
Date Mon, 10 Nov 2014 18:37:34 GMT

     [ https://issues.apache.org/jira/browse/METAMODEL-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kasper Sørensen resolved METAMODEL-92.
--------------------------------------
       Resolution: Fixed
    Fix Version/s: 4.3.0-incubating

Fixed as of commit: a2f97111044949998005b049bb375682cd9b262e

> ColumnNameAsKeysRowConverter should be able to traverse nested columns
> ----------------------------------------------------------------------
>
>                 Key: METAMODEL-92
>                 URL: https://issues.apache.org/jira/browse/METAMODEL-92
>             Project: Metamodel
>          Issue Type: Improvement
>    Affects Versions: 4.2.0-incubating
>            Reporter: Kasper Sørensen
>            Assignee: Kasper Sørensen
>             Fix For: 4.3.0-incubating
>
>
> In some modules we have rows/documents that can have nested objects. For instance in
the JSON module. Often these modules will use the ColumnNameAsKeysRowConverter class to extract
values from it's row/document objects into MetaModel's rows.
> It would be a big improvement if we allow the user to specify column names with a syntax
that allows them to denormalize their data and extract information even from nested objects.
For instance if you have this document:
> {
> "name":{ "first":"Joe", "last":"Sixpack" },
> "gender":"MALE",
> "verified":false,
> "userImage":"Rm9vYmFyIQ=="
> }
> Then a column with the name "name.first" should resolve "Joe" from this particular document.
I believe we have similar functionality in some of the NoSQL modules, so consider how we can
best reuse it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message