[
https://issues.apache.org/jira/browse/PHOENIX-6554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17542326#comment-17542326
]
Ankur Maheshwari commented on PHOENIX-6554:
-------------------------------------------
[~stoty] The file is already there is classpath .One of the file in classpath
is
/Users/ankur.maheshwari/Documents/Open_Source/SourceCode/phoenix/bin/../phoenix-pherf/config/user_defined_schema.sql
but command mentioned in
https://github.com/apache/phoenix/tree/master/phoenix-pherf
./pherf-standalone.py -drop all -l -q -z localhost -schemaFile
.*user_defined_schema.sql
errors out and gives :
zsh: no matches found: .*user_defined_scenario.xml
and when I run
./pherf-standalone.py -drop all -l -q -z localhost -schemaFile
user_defined_schema.sql
On debugging I found it doesn't match the pattern(user_defined_schema.sql )
with
/Users/ankur.maheshwari/Documents/Open_Source/SourceCode/phoenix/bin/../phoenix-pherf/config/user_defined_schema.sql
org.apache.phoenix.pherf.exception.FileLoaderException: Could not load Schema
Files
Can you please tell if anything changed in pattern matching and above command
?how to fire command successfully with -schemaFile option ??
> 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)
