You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Varun Saxena (JIRA)" <ji...@apache.org> on 2017/10/21 06:06:25 UTC
[jira] [Updated] (YARN-3649) Allow configurable prefix for hbase
table names (like prod, exp, test etc)
[ https://issues.apache.org/jira/browse/YARN-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Varun Saxena updated YARN-3649:
-------------------------------
Fix Version/s: 2.9.0
> Allow configurable prefix for hbase table names (like prod, exp, test etc)
> --------------------------------------------------------------------------
>
> Key: YARN-3649
> URL: https://issues.apache.org/jira/browse/YARN-3649
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Vrushali C
> Assignee: Vrushali C
> Labels: YARN-5355, atsv2-hbase
> Fix For: 2.9.0, YARN-5355, 3.0.0-beta1
>
> Attachments: YARN-3649-YARN-2928.01.patch, YARN-3649-YARN-5355.002.patch, YARN-3649-YARN-5355.003.patch, YARN-3649-YARN-5355.004.patch, YARN-3649-YARN-5355.005.patch, YARN-3649-YARN-5355.01.patch
>
>
> As per [~jrottinghuis]'s suggestion in YARN-3411, it will be a good idea to have a configurable prefix for hbase table names.
> This way we can easily run a staging, a test, a production and whatever setup in the same HBase instance / without having to override every single table in the config.
> One could simply overwrite the default prefix and you're off and running.
> For prefix, potential candidates are "tst" "prod" "exp" etc. Once can then still override one tablename if needed, but managing one whole setup will be easier.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org