You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrey Mashenkov (Jira)" <ji...@apache.org> on 2021/10/20 13:38:00 UTC
[jira] [Commented] (IGNITE-15783) Mapper API and simple
implementation.
[ https://issues.apache.org/jira/browse/IGNITE-15783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17431242#comment-17431242 ]
Andrey Mashenkov commented on IGNITE-15783:
-------------------------------------------
1. What about fields and column names case sensitivity?
2. Type validation, one-to-one restriction?
> Mapper API and simple implementation.
> -------------------------------------
>
> Key: IGNITE-15783
> URL: https://issues.apache.org/jira/browse/IGNITE-15783
> Project: Ignite
> Issue Type: Sub-task
> Reporter: Andrey Mashenkov
> Priority: Major
> Labels: ignite-3
>
> Design Mapper API for user POJO classes for use in KvView and RecordView.
> NB: Most likely, there is no need to have different interfaces for Key/Value/Record mappers
> and the same implementation can be reused for all cases.
> Let's
> * Implement an IdentityMapper as a default one that binds the POJO field to the column with the same name.
> * Implement a simple mapper that allows binding the POJO field to the column with a different name.
> Field <--> column mapping expected to be one-to-one function.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)