[
https://issues.apache.org/jira/browse/GORA-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500565#comment-13500565
]
Enis Soztutar commented on GORA-186:
------------------------------------
Great question. On other projects that I work on (hadoop and hbase), we have a
"Patch available" status for the issues. Once you submit a patch, you mark it
as patch available, so that the committers can review & commit. I've tried to
add that workflow to GORA, but was not able to do so. I think we should open an
INFRA ticket to do that. Lewis/Chris, you are also admins in jira, did you
tried anything like that?
> Show better errors when a field is missing in HBase mapping
> -----------------------------------------------------------
>
> Key: GORA-186
> URL: https://issues.apache.org/jira/browse/GORA-186
> Project: Apache Gora
> Issue Type: Improvement
> Components: storage-hbase
> Affects Versions: 0.2, 0.2.1
> Environment: Ubuntu 12.04, avro 1.3.2, hbase 0.92.0, gora 0.2.1
> Reporter: Alfonso Nishikawa
> Assignee: Alfonso Nishikawa
> Priority: Trivial
> Attachments: GORA-186.patch, GORA-186v2.patch
>
>
> When a field is wrong typed or missing in gora-hbase-mapping.xml, a
> NullPointerException is raised in org.apache.gora.hbase.store.HBaseStore:235
> Just control this to know which field is missing/wrong.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
