hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7065) alter table with multiple actions should do just one schema update (shell)
Date Mon, 29 Oct 2012 23:14:13 GMT

    [ https://issues.apache.org/jira/browse/HBASE-7065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13486473#comment-13486473

Ted Yu commented on HBASE-7065:

I think one schema update is better.
The example above isn't syntactically correct though.
To change MAX_FILESIZE, here is the syntax:
  hbase> alter 't1', METHOD => 'table_att', MAX_FILESIZE => '134217728'
> alter table with multiple actions should do just one schema update (shell)
> --------------------------------------------------------------------------
>                 Key: HBASE-7065
>                 URL: https://issues.apache.org/jira/browse/HBASE-7065
>             Project: HBase
>          Issue Type: Improvement
>          Components: shell
>    Affects Versions: 0.96.0
>            Reporter: Sergey Shelukhin
>            Priority: Minor
> In the shell, when one runs alter command with multiple things to do (e.g. "alter 't1',
'f1', { NAME => 'f2', VERSIONS => 5 }, { 'delete' => 'f3' }, MAX_FILESIZE => 1232353")
the shell does the schema update after each action.
> I'd assume it takes a long time on large clusters, and can also be unexpected from the
logical perspective, especially if it fails in the middle for example.
> Should it do one schema update instead?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message