ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexei Scherbakov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-3385) Improve schema import utility
Date Tue, 28 Jun 2016 12:48:57 GMT

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

Alexei Scherbakov commented on IGNITE-3385:
-------------------------------------------

For affinity key mapping it may generate single field annotated with @AffinityKeyMapped if
only one field was selected by user
or delegate to AffnityKeyMapper for multiple selected fields like:

{code}
 private static class MyMapper implements AffinityKeyMapper {
        @Override public Object affinityKey(Object o) {
            if (o instanceof PersonKey)
                return new PersonAffkey(((PersonKey)o).getOrganizationId(), ((PersonKey)o).getManagerId()));
            return o;
        }

        @Override public void reset() {

        }
    }
{code}

> Improve schema import utility
> -----------------------------
>
>                 Key: IGNITE-3385
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3385
>             Project: Ignite
>          Issue Type: Bug
>          Components: general
>            Reporter: Alexei Scherbakov
>            Priority: Minor
>
> It would be useful to add more code generation capabilities to
> schema import utility to reduce amount of hand-written boilerplate code.
> * Affinity key mapping
> * SQL query fields and indexes



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

Mime
View raw message