phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-4449) Incorrect behavior of sqlline after PHOENIX-3567
Date Tue, 12 Dec 2017 22:01:00 GMT


Josh Elser commented on PHOENIX-4449:

bq. But do we really need to log a message that there is no system argparse? That would be
quite annoying 

Nah, I don't think we need to. I was mostly trying to save future-Josh some pain and agony
if/when this breaks. It's really something I'd like to see at a {{DEBUG}} level -- not all
the time. I think that means we just nuke it instead.

> Incorrect behavior of sqlline after PHOENIX-3567
> ------------------------------------------------
>                 Key: PHOENIX-4449
>                 URL:
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.10.0, 4.13.0, 5.0.0
>            Reporter: Sergey Soldatov
>            Assignee: Josh Elser
>            Priority: Critical
>             Fix For: 5.0.0, 4.14.0
>         Attachments: PHOENIX-4449.001.patch
> In PHOENIX-3567 we have introduced a usage of argparse in sqlline as well as some default
values for the parameters. That's not good because of:
> 1. argparse is not a default package in old versions of python like 2.6.6 which is using
in centos 6 distribution. 
> 2. We should not set a default value for zookeeper parent because if it's not specified
in the command line, those values should be obtained from hbase client (hbase-site.xml or
default values if it's not in the classpath).

This message was sent by Atlassian JIRA

View raw message