You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Gabriel Reid (JIRA)" <ji...@apache.org> on 2015/04/19 21:28:58 UTC

[jira] [Resolved] (PHOENIX-1733) sqlline.py doesn't allow connecting with a tenant-specific connection

     [ https://issues.apache.org/jira/browse/PHOENIX-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gabriel Reid resolved PHOENIX-1733.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 4.4.0
                   5.0.0

Pushed to master and 4.x branch. Thanks [~abisek@gmail.com]!

> sqlline.py doesn't allow connecting with a tenant-specific connection
> ---------------------------------------------------------------------
>
>                 Key: PHOENIX-1733
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1733
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Gabriel Reid
>            Assignee: Abhishek Sreenivasa
>              Labels: Newbie
>             Fix For: 5.0.0, 4.4.0
>
>
> Connecting with a client-specific connection via sqlline.py should work with a command like the following:
> {code}
> ./bin/sqlline.py 'localhost:2181;TenantId=t1'
> {code}
> However, the command that is built up within sqlline.py doesn't correctly quote the JDBC url, so the JDBC url parameter ends up as:
> {code}
> jdbc:phoenix:localhost:2181;TenantId=t1
> {code}
> without quoting. This causes the semicolon to be interpreted as a command separator by the shell, effectively ignoring it (and any other parameters).
> Proper parameter quoting (as done with the pipes module in psql.py) should be used for sqlline.py to get around this and similar issues.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)