You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@gora.apache.org by "Kevin Ratnasekera (JIRA)" <ji...@apache.org> on 2017/06/04 07:22:04 UTC

[jira] [Assigned] (GORA-512) Fail at the time of error logging if KeyClass in gora-hbase-mapping is not the same as the one in the data bean

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

Kevin Ratnasekera reassigned GORA-512:
--------------------------------------

    Assignee: Nishadi Kirielle

> Fail at the time of error logging if KeyClass in gora-hbase-mapping is not the same as the one in the data bean
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: GORA-512
>                 URL: https://issues.apache.org/jira/browse/GORA-512
>             Project: Apache Gora
>          Issue Type: Improvement
>          Components: gora-hbase
>            Reporter: Nishadi Kirielle
>            Assignee: Nishadi Kirielle
>            Priority: Minor
>
> In the current implementation, when reading the HBase mapping file, if the HBase mapping file does not have a matching key class and name to the data bean, it only logs that information.[1] It does not fail at the time of detecting it. It fails only at the time of building the mapper [2] when it detects the table name is null. It will be better if it can fail at the time of detecting that mapping file is missing the corresponding class. 
> [1]. https://github.com/apache/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L797
> [2]. https://github.com/apache/gora/blob/master/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java#L815



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)