[ https://issues.apache.org/jira/browse/PHOENIX-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15302804#comment-15302804 ]
Alicia Ying Shu commented on PHOENIX-2931: ------------------------------------------ [~jamestaylor] [~elserj] [~sergey.soldatov] Thanks for the discussion! Let me step back a little bit to explain why we had suggested using a keyword "default" or position-based checking existence of a file. The main reason is that we had hoped to avoid adding any directive that changes current behavior. If allow adding a directive such as "-connection", the solution becomes simple. We would require all sqlline.py and psql.py usages to add "-connection" if they would like to provide zookeeper quorum. If we did not find this directive, we would add zookeeper quorum from hbase-site.xml. But be aware that currently there is no requirement to use "-connnection" for either sqlline.py or psql.py. If users did not use it, we may wrongly replace their quorum with the one in hbase-site.xml. This solution is not backward compatible. Is it acceptable? > Phoenix client asks users to provide configs in cli that are present on the > machine in hbase conf > ------------------------------------------------------------------------------------------------- > > Key: PHOENIX-2931 > URL: https://issues.apache.org/jira/browse/PHOENIX-2931 > Project: Phoenix > Issue Type: Bug > Reporter: Alicia Ying Shu > Assignee: Alicia Ying Shu > Priority: Minor > Attachments: PHOENIX-2931.patch > > > Users had complaints on running commands like > {code} > phoenix-sqlline > pre-prod-poc-2.novalocal,pre-prod-poc-10.novalocal,pre-prod-poc-1.novalocal:/hbase-unsecure > service-logs.sql > {code} > However the zookeeper quorum and the port are available in hbase configs. > Phoenix should read these configs from the system instead of having the user > supply them every time. > What we can do is to introduce a keyword "default". If it is specified, > default zookeeper quorum and port will be taken from hbase configs. > Otherwise, users can specify their own. -- This message was sent by Atlassian JIRA (v6.3.4#6332)