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

Ankur Maheshwari commented on PHOENIX-6554:
-------------------------------------------

[~stoty] [~kiran.maturi] I am newbie in Pheonix/Hbase contributions. I was 
following this [https://phoenix.apache.org/pherf.html] to replicate above 
stated scenario. Two questions:

 

1) On running

*bin/pherf-standalone.py* -It gave me location of both Schema Files and 
Scenario Files {*}as stated below{*}. Is it fine to use this schema file ?Can 
you provide any other schema file to me as well for testing ?

{*}Schema Files{*}: 
/Users/ankur.maheshwari/Documents/Open_Source/SourceCode/phoenix/phoenix-pherf/config/datamodel/user_defined_schema.sql

{*}Scenario 
Files{*}:/Users/ankur.maheshwari/Documents/Open_Source/SourceCode/phoenix/phoenix-pherf/config/scenario/user_defined_scenario.xml

 

2) I ran 

 *bin/pherf-standalone.py -drop all -l -q -z localhost*

*It seems to run successfully with :*

WARN impl.MetricsSystemImpl: Phoenix metrics system already initialized!

Trying to match resource pattern: .*.sql

File resourceList Loaded: 
[/Users/ankur.maheshwari/Documents/Open_Source/SourceCode/phoenix/phoenix-pherf/config/datamodel/user_defined_schema.sql]
 

 

*But* 

*bin/pherf-standalone.py -drop all -l -q -z localhost -schemaFile 
/Users/ankur.maheshwari/Documents/Open_Source/SourceCode/phoenix/phoenix-pherf/config/datamodel/user_defined_schema.sql*

 

fails with *Could not load Schema Files*

*Following is call stack:*

Trying to match resource pattern: 
/Users/ankur.maheshwari/Documents/Open_Source/SourceCode/phoenix/phoenix-pherf/config/datamodel/user_defined_schema.sql

File resourceList Loaded: []

org.apache.phoenix.pherf.exception.FileLoaderException: Could not load Schema 
Files

 at org.apache.phoenix.pherf.schema.SchemaReader.read(SchemaReader.java:99)

 at org.apache.phoenix.pherf.schema.SchemaReader.<init>(SchemaReader.java:55)

 at org.apache.phoenix.pherf.schema.SchemaReader.<init>(SchemaReader.java:48)

 at org.apache.phoenix.pherf.Pherf.run(Pherf.java:301)

 at org.apache.phoenix.pherf.Pherf.main(Pherf.java:249)

22/05/16 11:02:53 ERROR pherf.Pherf: Something went wrong.

org.apache.phoenix.pherf.exception.FileLoaderException: Could not load Schema 
Files

 at org.apache.phoenix.pherf.schema.SchemaReader.read(SchemaReader.java:99)

 at org.apache.phoenix.pherf.schema.SchemaReader.<init>(SchemaReader.java:55)

 at org.apache.phoenix.pherf.schema.SchemaReader.<init>(SchemaReader.java:48)

 at org.apache.phoenix.pherf.Pherf.run(Pherf.java:301)

 at org.apache.phoenix.pherf.Pherf.main(Pherf.java:249)

 

 

 

Can you please tell how to run  pherf with option -schemaFile properly and 
resolve above queries ?

> Pherf CLI option long/short option names do not follow conventions
> ------------------------------------------------------------------
>
>                 Key: PHOENIX-6554
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6554
>             Project: Phoenix
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 5.2.0
>            Reporter: Istvan Toth
>            Assignee: Ankur Maheshwari
>            Priority: Minor
>
> The Pherf script does not use long and short option names consistently.
> for example:
> -t and --thin are for specifying the the thin PQS URL, 
> and 
> -z and --zookeeper are for the ZK quorum
> but 
> -schemaFile is used to specify the schema file, and 
> --schemaFile does not work.
> IMO options that look like long options should also be accepted with double 
> dash, or we could just invent new short options  for them (which would break 
> backwards compatibility).
> i.e. instead of 
> {code:java}
> options.addOption("schemaFile", true,
>                 "Regex or file name for the Test phoenix table schema .sql to 
> use.");
> {code}
> we could have one of the following:
> {code:java}
> options.addOption("sf", "schemaFile", true,
>                 "Regex or file name for the Test phoenix table schema .sql to 
> use.");
> options.addOption("schemaFile", "schemaFile", true,
>                 "Regex or file name for the Test phoenix table schema .sql to 
> use.");
> {code}



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to