RE: problem to run phoenix client 4.13.1 for CDH5.11.2 on windows

2017-12-05 Thread Bulvik, Noam 
One more on this when using the client from the regular release (4.13 for HBase 
)1.3 it works fine on same pc

From: Bulvik, Noam
Sent: Thursday, November 30, 2017 11:22 AM
To: user@phoenix.apache.org
Subject: problem to run phoenix client 4.13.1 for CDH5.11.2 on windows

Hi
I am using JDBC UI client on windows. After I upgrade to latest parcel of 
phonix I got the following error (it did not happened on older parcels either 
when I compiled myself or when I used ones supplied by cloudera [4.7])

SEVERE: Failed to locate the winutils binary in the hadoop binary path
java.io.IOException: Could not locate executable null\bin\winutils.exe in the 
Hadoop binaries.
at org.apache.hadoop.util.Shell.getQualifiedBinPath(Shell.java:404)
at org.apache.hadoop.util.Shell.getWinUtilsPath(Shell.java:419)
at org.apache.hadoop.util.Shell.(Shell.java:412)
at org.apache.hadoop.util.StringUtils.(StringUtils.java:79)
at org.apache.hadoop.security.Groups.parseStaticMapping(Groups.java:168)
at org.apache.hadoop.security.Groups.(Groups.java:132)
at org.apache.hadoop.security.Groups.(Groups.java:100)
at 
org.apache.hadoop.security.Groups.getUserToGroupsMappingService(Groups.java:435)
at 
org.apache.hadoop.security.UserGroupInformation.initialize(UserGroupInformation.java:337)
at 
org.apache.hadoop.security.UserGroupInformation.ensureInitialized(UserGroupInformation.java:304)
at 
org.apache.hadoop.security.UserGroupInformation.loginUserFromSubject(UserGroupInformation.java:891)
at 
org.apache.hadoop.security.UserGroupInformation.getLoginUser(UserGroupInformation.java:857)
   at 
org.apache.hadoop.security.UserGroupInformation.getCurrentUser(UserGroupInformation.java:724)
at 
org.apache.hadoop.hbase.security.User$SecureHadoopUser.(User.java:293)
at org.apache.hadoop.hbase.security.User.getCurrent(User.java:191)
at 
org.apache.phoenix.jdbc.PhoenixEmbeddedDriver$ConnectionInfo.(PhoenixEmbeddedDriver.java:504)
at 
org.apache.phoenix.jdbc.PhoenixEmbeddedDriver$ConnectionInfo.create(PhoenixEmbeddedDriver.java:312)
at 
org.apache.phoenix.jdbc.PhoenixDriver.getConnectionQueryServices(PhoenixDriver.java:232)
at 
org.apache.phoenix.jdbc.PhoenixEmbeddedDriver.createConnection(PhoenixEmbeddedDriver.java:150)
at org.apache.phoenix.jdbc.PhoenixDriver.connect(PhoenixDriver.java:221)
at workbench.db.DbDriver.connect(DbDriver.java:513)
at workbench.db.ConnectionMgr.connect(ConnectionMgr.java:255)
at workbench.db.ConnectionMgr.getConnection(ConnectionMgr.java:182)
at 
workbench.gui.profiles.ConnectionGuiHelper$1.run(ConnectionGuiHelper.java:142)









Noam




PRIVILEGED AND CONFIDENTIAL
PLEASE NOTE: The information contained in this message is privileged and 
confidential, and is intended only for the use of the individual to whom it is 
addressed and others who have been specifically authorized to receive it. If 
you are not the intended recipient, you are hereby notified that any 
dissemination, distribution or copying of this communication is strictly 
prohibited. If you have received this communication in error, or if any 
problems occur with transmission, please contact sender. Thank you.

class not found when running sql qlline-thin.py from 4.13 parcel version for CDH 5.11.2

2017-12-05 Thread Bulvik, Noam 
Hi,

When running  sql qlline-thin.py  from 4.13 parcel version for CDH 5.11.2 you 
get class not found error. This does not happened when you run it from the 
regular phonix release (4.13 for HBase 1.3)


java.lang.NoClassDefFoundError: 
org/apache/phoenix/shaded/org/apache/http/config/Lookup
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:190)
at 
org.apache.calcite.avatica.remote.AvaticaHttpClientFactoryImpl.instantiateClient(AvaticaHttpClientFactoryImpl.java:112)
at 
org.apache.calcite.avatica.remote.AvaticaHttpClientFactoryImpl.getClient(AvaticaHttpClientFactoryImpl.java:68)
at 
org.apache.calcite.avatica.remote.Driver.getHttpClient(Driver.java:160)
at 
org.apache.calcite.avatica.remote.Driver.createService(Driver.java:123)
at org.apache.calcite.avatica.remote.Driver.createMeta(Driver.java:97)
at 
org.apache.calcite.avatica.AvaticaConnection.(AvaticaConnection.java:121)
at 
org.apache.calcite.avatica.AvaticaJdbc41Factory$AvaticaJdbc41Connection.(AvaticaJdbc41Factory.java:105)
at 
org.apache.calcite.avatica.AvaticaJdbc41Factory.newConnection(AvaticaJdbc41Factory.java:62)
at 
org.apache.calcite.avatica.UnregisteredDriver.connect(UnregisteredDriver.java:138)
at org.apache.calcite.avatica.remote.Driver.connect(Driver.java:165)
at sqlline.DatabaseConnection.connect(DatabaseConnection.java:157)
at sqlline.DatabaseConnection.getConnection(DatabaseConnection.java:203)
at sqlline.Commands.connect(Commands.java:1064)
at sqlline.Commands.connect(Commands.java:996)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:38)
at sqlline.SqlLine.dispatch(SqlLine.java:809)
at sqlline.SqlLine.initArgs(SqlLine.java:588)
at sqlline.SqlLine.begin(SqlLine.java:661)
at sqlline.SqlLine.start(SqlLine.java:398)
at sqlline.SqlLine.main(SqlLine.java:291)
at 
org.apache.phoenix.queryserver.client.SqllineWrapper.main(SqllineWrapper.java:93)
Caused by: java.lang.ClassNotFoundException: 
org.apache.phoenix.shaded.org.apache.http.config.Lookup
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
... 27 more





PRIVILEGED AND CONFIDENTIAL
PLEASE NOTE: The information contained in this message is privileged and 
confidential, and is intended only for the use of the individual to whom it is 
addressed and others who have been specifically authorized to receive it. If 
you are not the intended recipient, you are hereby notified that any 
dissemination, distribution or copying of this communication is strictly 
prohibited. If you have received this communication in error, or if any 
problems occur with transmission, please contact sender. Thank you.

Re: Boolean condition doesn't support IS operator

2017-12-05 Thread Flavio Pompermaier 
Ok, fine for me :)
Thanks for the discussion anyway

On Tue, Dec 5, 2017 at 5:54 PM, James Taylor  wrote:

> In SQL, you use IS with NULL or NOT NULL as a way to test for null since
> column = NULL will never return true. I’ve never seen a SQL dialect that
> allows column IS true or column IS 4 as some kind of alternative to using
> an equality expression. More on that here: https://stackoverflow.
> com/questions/859762/is-this-the-proper-way-to-do-boolean-test-in-sql
>
> On Tue, Dec 5, 2017 at 8:28 AM Flavio Pompermaier 
> wrote:
>
>> At the moment I'm usign VALID = true but IMHO Phoenix should support the
>> IS syntax for boolean columns as well..of course this is just a +1 on this
>> topic
>> If no other one ask for this feature you could ignore this :)
>>
>> On Tue, Dec 5, 2017 at 4:31 PM, James Taylor 
>> wrote:
>>
>>> How about just using VALID = true or just VALID like this: select * from
>>> t where VALID
>>>
>>> On Tue, Dec 5, 2017 at 2:52 AM Flavio Pompermaier 
>>> wrote:
>>>
 Hi to all,
 I'm using Phoenix 4.7 and I cannot use IS operator on boolean values
 (e.g. VALID IS TRUE)
 Would it be that difficult to support it?

 Best,
 Flavio

>>>
>>
>>
>> --
>> Flavio Pompermaier
>> Development Department
>>
>> OKKAM S.r.l.
>> Tel. +(39) 0461 041809 <+39%200461%20041809>
>>
>


-- 
Flavio Pompermaier
Development Department

OKKAM S.r.l.
Tel. +(39) 0461 041809

Re: Boolean condition doesn't support IS operator

2017-12-05 Thread James Taylor 
In SQL, you use IS with NULL or NOT NULL as a way to test for null since
column = NULL will never return true. I’ve never seen a SQL dialect that
allows column IS true or column IS 4 as some kind of alternative to using
an equality expression. More on that here:
https://stackoverflow.com/questions/859762/is-this-the-proper-way-to-do-boolean-test-in-sql

On Tue, Dec 5, 2017 at 8:28 AM Flavio Pompermaier 
wrote:

> At the moment I'm usign VALID = true but IMHO Phoenix should support the
> IS syntax for boolean columns as well..of course this is just a +1 on this
> topic
> If no other one ask for this feature you could ignore this :)
>
> On Tue, Dec 5, 2017 at 4:31 PM, James Taylor 
> wrote:
>
>> How about just using VALID = true or just VALID like this: select * from
>> t where VALID
>>
>> On Tue, Dec 5, 2017 at 2:52 AM Flavio Pompermaier 
>> wrote:
>>
>>> Hi to all,
>>> I'm using Phoenix 4.7 and I cannot use IS operator on boolean values
>>> (e.g. VALID IS TRUE)
>>> Would it be that difficult to support it?
>>>
>>> Best,
>>> Flavio
>>>
>>
>
>
> --
> Flavio Pompermaier
> Development Department
>
> OKKAM S.r.l.
> Tel. +(39) 0461 041809
>

Re: Boolean condition doesn't support IS operator

2017-12-05 Thread Flavio Pompermaier 
At the moment I'm usign VALID = true but IMHO Phoenix should support the IS
syntax for boolean columns as well..of course this is just a +1 on this
topic
If no other one ask for this feature you could ignore this :)

On Tue, Dec 5, 2017 at 4:31 PM, James Taylor  wrote:

> How about just using VALID = true or just VALID like this: select * from t
> where VALID
>
> On Tue, Dec 5, 2017 at 2:52 AM Flavio Pompermaier 
> wrote:
>
>> Hi to all,
>> I'm using Phoenix 4.7 and I cannot use IS operator on boolean values
>> (e.g. VALID IS TRUE)
>> Would it be that difficult to support it?
>>
>> Best,
>> Flavio
>>
>


-- 
Flavio Pompermaier
Development Department

OKKAM S.r.l.
Tel. +(39) 0461 041809

Re: Boolean condition doesn't support IS operator

2017-12-05 Thread James Taylor 
How about just using VALID = true or just VALID like this: select * from t
where VALID

On Tue, Dec 5, 2017 at 2:52 AM Flavio Pompermaier 
wrote:

> Hi to all,
> I'm using Phoenix 4.7 and I cannot use IS operator on boolean values (e.g.
> VALID IS TRUE)
> Would it be that difficult to support it?
>
> Best,
> Flavio
>

Boolean condition doesn't support IS operator

2017-12-05 Thread Flavio Pompermaier 
Hi to all,
I'm using Phoenix 4.7 and I cannot use IS operator on boolean values (e.g.
VALID IS TRUE)
Would it be that difficult to support it?

Best,
Flavio

Add automatic/default SALT

2017-12-05 Thread Flavio Pompermaier 
Hi to all,
as stated by at the documentation[1] "for optimal performance, number of
salt buckets should match number of region servers".
So, why not to add an option AUTO/DEFAULT for salting that defaults this
parameter to the number of region servers?
Otherwise I have to manually connect to HBase, retrieve that number and
pass to Phoenix...
What do you think?

[1] https://phoenix.apache.org/performance.html#Salting

Best,
Flavio