[
https://issues.apache.org/jira/browse/HBASE-13991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14609376#comment-14609376
]
Enis Soztutar commented on HBASE-13991:
---------------------------------------
I don't like introducing a concept of "humongous tables". I can definitely
understand that you wanted to get the layout changes without affecting other
users, but adding another switch is not the way to go for operational concerns.
If we are doing a layout change, we should do it for all the tables, and find a
way to handle migrations automatically, etc.
What other areas that a "humongous table" differ from a regular table? What
happens if a table starts as a regular table, then becomes humongous?
I like where this is going. Sorry, [~benlau] this might again turn into a
bigger re-architect some parts kind of jira instead of a simpler patch. But I
agreed with Stack and Matteo that we should take a holistic view.
See:
https://issues.apache.org/jira/browse/HBASE-7806?focusedCommentId=13594284&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13594284
HBASE-13159 also talks about unifying reference files / file links and snapshot
files so that the soft links is much easier to maintain.
> Hierarchical Layout for Humongous Tables
> ----------------------------------------
>
> Key: HBASE-13991
> URL: https://issues.apache.org/jira/browse/HBASE-13991
> Project: HBase
> Issue Type: Sub-task
> Reporter: Ben Lau
> Assignee: Ben Lau
> Attachments: HBASE-13991-master.patch, HumongousTableDoc.pdf
>
>
> Add support for humongous tables via a hierarchical layout for regions on
> filesystem.
> Credit for most of this code goes to Huaiyu Zhu.
> Latest version of the patch is available on the review board:
> https://reviews.apache.org/r/36029/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
