hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-9898) Have a way to set a different default compression on HCD
Date Wed, 27 Nov 2013 22:48:37 GMT

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

Andrew Purtell updated HBASE-9898:
----------------------------------

    Fix Version/s:     (was: 0.98.0)

No patch, moving out of 0.98. Put back if you feel otherwise.

> Have a way to set a different default compression on HCD
> --------------------------------------------------------
>
>                 Key: HBASE-9898
>                 URL: https://issues.apache.org/jira/browse/HBASE-9898
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Jean-Daniel Cryans
>
> I was exploring if there would be a nice way to set the compression by default to a different
algorithm but I didn't find any that I can implement right now, dumping my ideas so that others
can chime in.
> I think the best place to take it into account would be on the master's side. Basically
you run a check when creating a new table to see if compression wasn't set, and if so then
set it to the new default. The important thing is you don't want to replace NONE, because
that might be the user's goal to set it like that.
> The main problem is that the normal HCD constructor calls the deprecated constructor
that sets most of the properties to their defaults, including compression, which means that
it will always be NONE instead of null.
> It appears that this constructor has been deprecated since February 2012 (https://github.com/apache/hbase/blame/0.94/src/main/java/org/apache/hadoop/hbase/HColumnDescriptor.java#L292)
so maybe we can remove it in the next major version and make our life easier?



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message