You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gora.apache.org by "Ferdy Galema (Created) (JIRA)" <ji...@apache.org> on 2012/03/01 12:05:58 UTC
[jira] [Created] (GORA-101) HBaseStore should properly support
multiple tables in the mapping file.
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
Reporter: Ferdy Galema
Priority: Minor
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
[jira] [Updated] (GORA-101) HBaseStore should properly support
multiple tables in the mapping file.
Posted by "Ferdy Galema (Updated) (JIRA)" <ji...@apache.org>.
[ 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-part2.patch
> 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
[jira] [Commented] (GORA-101) HBaseStore should properly support
multiple tables in the mapping file.
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GORA-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13221564#comment-13221564 ]
Hudson commented on GORA-101:
-----------------------------
Integrated in gora-trunk #168 (See [https://builds.apache.org/job/gora-trunk/168/])
GORA-101 HBaseStore should properly support multiple tables in the mapping file. (part2) (Revision 1296607)
Result = SUCCESS
ferdy :
Files :
* /gora/trunk/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: 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
[jira] [Closed] (GORA-101) HBaseStore should properly support
multiple tables in the mapping file.
Posted by "Ferdy Galema (Closed) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (GORA-101) HBaseStore should properly support
multiple tables in the mapping file.
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GORA-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220125#comment-13220125 ]
Hudson commented on GORA-101:
-----------------------------
Integrated in gora-trunk #164 (See [https://builds.apache.org/job/gora-trunk/164/])
GORA-101 HBaseStore should properly support multiple tables in the mapping file. (Revision 1295608)
Result = FAILURE
ferdy :
Files :
* /gora/trunk/CHANGES.txt
* /gora/trunk/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseColumn.java
* /gora/trunk/gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseMapping.java
* /gora/trunk/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: 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
[jira] [Updated] (GORA-101) HBaseStore should properly support
multiple tables in the mapping file.
Posted by "Ferdy Galema (Updated) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (GORA-101) HBaseStore should properly support
multiple tables in the mapping file.
Posted by "Ferdy Galema (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GORA-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ferdy Galema updated GORA-101:
------------------------------
Component/s: storage-hbase
> 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
>
> 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