gora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ferdy Galema (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (GORA-101) HBaseStore should properly support multiple tables in the mapping file.
Date Thu, 01 Mar 2012 15:11:57 GMT

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

Ferdy Galema updated GORA-101:
------------------------------

    Attachment: GORA-101.patch

Tested patch with both prefix and no prefix. This patch does not change compatibilty of the
mapping file. (Though I was tempted to do this: I created a TODO for this.)
                
> 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: storage-hbase
>            Reporter: Ferdy Galema
>            Priority: Minor
>         Attachments: 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message