[
https://issues.apache.org/jira/browse/YARN-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vrushali C updated YARN-3649:
-----------------------------
Attachment: YARN-3649-YARN-5355.005.patch
Uploading v5 that addresses Varun's suggestions.
Diff between this patch and the one before this:
{noformat}
$ diff YARN-3649-YARN-5355.004.patch YARN-3649-YARN-5355.005.patch
2c2
< index 3bb73f5..9e95d68 100644
---
> index 3bb73f5..925f626 100644
28c28
< + TIMELINE_SERVICE_PREFIX + "schema.prefix";
---
> + TIMELINE_SERVICE_PREFIX + "hbase-schema.prefix";
32a33,55
> diff --git
> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/resources/yarn-default.xml
>
> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/resources/yarn-default.xml
> index ed220c0..f1fd85b 100644
> ---
> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/resources/yarn-default.xml
> +++
> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/resources/yarn-default.xml
> @@ -2258,6 +2258,18 @@
> <value>259200000</value>
> </property>
>
> + <property>
> + <description>
> + The value of this parameter sets the prefix for all tables that are part
> of
> + timeline service in the hbase storage schema. It can be set to "dev."
> + or "staging." if it is to be used for development or staging instances.
> + This way the data in production tables stays in a separate set of tables
> + prefixed by "prod.".
> + </description>
> + <name>yarn.timeline-service.hbase-schema.prefix</name>
> + <value>prod.</value>
> + </property>
> +
> <!-- Shared Cache Configuration -->
>
> <property>
$
{noformat}
> 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
> 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.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
