Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 8 Aug 2016 09:37:20 +0000 (UTC)
From: "Varun Saxena (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12830066.1431664091000.247570.1470649040506@Atlassian.JIRA>
In-Reply-To: <JIRA.12830066.1431664091000@Atlassian.JIRA>
References: <JIRA.12830066.1431664091000@Atlassian.JIRA> <JIRA.12830066.1431664091889@arcas>
Subject: [jira] [Commented] (YARN-3649) Allow configurable prefix for hbase
 table names (like prod, exp, test etc)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 08 Aug 2016 09:37:22 -0000


    [ https://issues.apache.org/jira/browse/YARN-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15411594#comment-15411594 ] 

Varun Saxena commented on YARN-3649:
------------------------------------

Thanks [~vrushalic] for the patch
Chekcstyle and javadoc is related.

{code}
| **`yarn.timeline-service.schema.prefix`** | The schema prefix for hbase tables. Defaults to ".dev". |
{code}
Should be dev. instead of .dev

I guess there can be differing opinions on this but should we have prod as default instead of dev ?


> 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: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org