Mailing-List: contact dev-help@gora.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@gora.apache.org
Date: Sat, 3 Mar 2012 12:49:56 +0000 (UTC)
From: "Ferdy Galema (Closed) (JIRA)" <jira@apache.org>
To: dev@gora.apache.org
Message-ID: 
 <2100345326.17682.1330778996893.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1372644199.6882.1330599958345.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Closed] (GORA-101) HBaseStore should properly support
 multiple tables in the mapping file.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ferdy Galema closed GORA-101.
-----------------------------

    Resolution: Fixed
    
> 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-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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira