[
https://issues.apache.org/jira/browse/YARN-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421838#comment-15421838
]
Vrushali C commented on YARN-3649:
----------------------------------
Thanks [~varun_saxena]! I will upload a patch shortly that addresses the
documentation changes and the checkstyle ones.
bq. I guess there can be differing opinions on this but should we have prod as
default instead of dev ?
Yes, so my thinking is that if a new person wants to try this out in their
setup and then tries out something to run with default options and if it is set
to default to "prod.", then they will start writing to prod tables
unintentionally.
But when the param on the cluster configs on client nodes is explicitly set to
"prod.", then that is fine and that would mean any user writing to timeline
service will write to production tables, which is what we would want on those
client nodes.
> 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.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: [email protected]
For additional commands, e-mail: [email protected]
