Return-Path: 
 <commits-return-7654-apmail-phoenix-commits-archive=phoenix.apache.org@phoenix.apache.org>
X-Original-To: apmail-phoenix-commits-archive@minotaur.apache.org
Delivered-To: apmail-phoenix-commits-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id B33D318D95
	for <apmail-phoenix-commits-archive@minotaur.apache.org>;
 Fri, 11 Sep 2015 18:10:48 +0000 (UTC)
Received: (qmail 27746 invoked by uid 500); 11 Sep 2015 18:10:45 -0000
Delivered-To: apmail-phoenix-commits-archive@phoenix.apache.org
Received: (qmail 27657 invoked by uid 500); 11 Sep 2015 18:10:45 -0000
Mailing-List: contact commits-help@phoenix.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:commits-help@phoenix.apache.org>
List-Unsubscribe: <mailto:commits-unsubscribe@phoenix.apache.org>
List-Post: <mailto:commits@phoenix.apache.org>
List-Id: <commits.phoenix.apache.org>
Reply-To: dev@phoenix.apache.org
Delivered-To: mailing list commits@phoenix.apache.org
Received: (qmail 27643 invoked by uid 99); 11 Sep 2015 18:10:45 -0000
Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org)
 (140.211.11.23)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Sep 2015 18:10:45 +0000
Received: by git1-us-west.apache.org (ASF Mail Server at
 git1-us-west.apache.org, from userid 33)
	id 385EFDFA85; Fri, 11 Sep 2015 18:10:45 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: codymarcel@apache.org
To: commits@phoenix.apache.org
Date: Fri, 11 Sep 2015 18:10:47 -0000
Message-Id: <f0e18121bbec416d90d9ecb20b2e8a30@git.apache.org>
In-Reply-To: <ca38b8c406604632800cac64782c21e1@git.apache.org>
References: <ca38b8c406604632800cac64782c21e1@git.apache.org>
X-Mailer: ASF-Git Admin Mailer
Subject: [3/4] phoenix git commit: PHOENIX-2227 Adding comments to
 test_scenario.xml to explain new features added.

PHOENIX-2227 Adding comments to test_scenario.xml to explain new features added.


Project: http://git-wip-us.apache.org/repos/asf/phoenix/repo
Commit: http://git-wip-us.apache.org/repos/asf/phoenix/commit/1a8f522b
Tree: http://git-wip-us.apache.org/repos/asf/phoenix/tree/1a8f522b
Diff: http://git-wip-us.apache.org/repos/asf/phoenix/diff/1a8f522b

Branch: refs/heads/4.x-HBase-1.0
Commit: 1a8f522b57de7d183464a04d075a48b7cb3fb3ce
Parents: a3f6f26
Author: Jan <jfernando@salesforce.com>
Authored: Fri Sep 4 13:17:32 2015 -0700
Committer: Cody Marcel <cmarcel@cmarcel-wsl1.internal.salesforce.com>
Committed: Fri Sep 11 11:05:13 2015 -0700

----------------------------------------------------------------------
 .../src/test/resources/scenario/test_scenario.xml  | 17 +++++++++++++++--
 1 file changed, 15 insertions(+), 2 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/phoenix/blob/1a8f522b/phoenix-pherf/src/test/resources/scenario/test_scenario.xml
----------------------------------------------------------------------
diff --git a/phoenix-pherf/src/test/resources/scenario/test_scenario.xml b/phoenix-pherf/src/test/resources/scenario/test_scenario.xml
index 735e690..50a603e 100644
--- a/phoenix-pherf/src/test/resources/scenario/test_scenario.xml
+++ b/phoenix-pherf/src/test/resources/scenario/test_scenario.xml
@@ -220,10 +220,23 @@
                 <query id="q4" statement="select sum(SOME_INT) from PHERF.TEST_TABLE"/>
             </querySet>
         </scenario>
-        <!-- Test writing to a Multi-tenant View -->
+        <!-- To configure a Write Workload to write to a tenant specific view users need to
+             specify the tenantId attribute on the scenario, specifying the tenant they 
+             want to write data for as the attribute value. This tells Pherf to take out a 
+             tenant-specific connection for executing the write workload. 
+             The name of the tenant specific view to write to can then be specified as the value of
+             the tablename attribute. This assumes the tenant specific view has been created. To 
+             dynamically create the view see comments below with regard to the ddl attribute. 
+        -->
         <scenario tableName="PHERF.TEST_VIEW" tenantId="abcdefghijklmno" rowCount="100" name="testMTWriteScenario">
         </scenario>
-        <!--  Test scenario DDL -->
+        <!--  Scenario level DDL that is dynamically executed before the Write Workload is run.
+              This pattern is really useful when you want to write data to multi-tenant view and the tenant id is
+              tightly bound to the scenario. In such cases you can't create the view through the data model flow.
+              The value of the tableName attribute is name of the view that is dynamically created based on the DDL
+              in the ddl attribute. Queries accessing the View will need to manually make sure Pherf was run with the -l option at
+              least once. 
+         -->
         <scenario tableName="PHERF.TEST_MT_VIEW" tenantId="abcdefghijklmno" 
                     ddl="CREATE VIEW IF NOT EXISTS PHERF.TEST_MT_VIEW (field1 VARCHAR) AS SELECT * FROM PHERF.TEST_MULTI_TENANT_TABLE" 
                     rowCount="100" name="testMTDdlWriteScenario">