[
https://issues.apache.org/jira/browse/GORA-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696539#comment-13696539
]
Hudson commented on GORA-101:
-----------------------------
Integrated in goraOracle #6 (See [https://builds.apache.org/job/goraOracle/6/])
GORA-101 HBaseStore should properly support multiple tables in the mapping
file. (Revision c066b1666df0db7872a062529de62fb206a3d91f)
GORA-101 HBaseStore should properly support multiple tables in the mapping
file. (part2) (Revision cea6c41780719d5cfff77d880b2519399b2e24e8)
Result = FAILURE
ferdy :
Files :
* gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java
* gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseMapping.java
* CHANGES.txt
* gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseColumn.java
ferdy :
Files :
* gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java
> HBaseStore should properly support multiple tables in the mapping file.
> -----------------------------------------------------------------------
>
> Key: GORA-101
> URL: https://issues.apache.org/jira/browse/GORA-101
> Project: Apache Gora
> Issue Type: Bug
> Components: gora-hbase
> Reporter: Ferdy Galema
> Priority: Minor
> Attachments: GORA-101-part2.patch, GORA-101.patch
>
>
> When a client requests a schema name with a prefix (Nutchgora is doing this
> with crawlid) then the family properties like compression and maxVersions are
> not properly read. Those are only set on the default table. I will fix this
> so that somehow all tables that share the same mapping definition all use the
> *same family properties*.
--
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
