Re: HBase Phoenix Integration

2016-02-26 Thread Amit Shah
Hi Murugesan, What preconditions would I need on the server to execute the python script? I have Python 2.7.5 installed on the zookeeper server. If I just copy the sqlline script to the /etc/hbase/conf directory and execute it I get the below import errors. Note this time I had 4.5.2-HBase-1.0

Re: Phoenix Query Server Avatica Upsert

2016-02-26 Thread James Taylor
Sorry for the delayed response, Lukáš. I still think it would be a good addition and the JSON/Protobuf issue you brought up is all the more reason to keep the JSON binding too. We have precedence for non Java code with our Spark integration. Sure, it makes it a bit more work to add this new

RE: Failed to dynamically load library 'libMJCloudConnector.so'.

2016-02-26 Thread Murugesan, Rani
I did pick up the client jar from the same location as server jars. Of the same version:(from the zookeeper server, where I also have the CM server) phoenix-1.2.0-client.jar phoenix-1.2.0-thin-client.jar phoenix-1.2.0-server.jar -Original Message- From: Thomas D'Silva

Re: Failed to dynamically load library 'libMJCloudConnector.so'.

2016-02-26 Thread Thomas D'Silva
What phoenix server jar version are you using? The 1.2.0 client jar is probably too old to use with your server jar. Its best if your client jar version is the same as the server jar. On Thu, Feb 25, 2016 at 3:55 PM, Murugesan, Rani wrote: > Hi, > > > > I used the open source

Re: to_date not working as expected

2016-02-26 Thread Binu Mathew
The patch resolved our issue. We just updated the jar file on all nodes in the cluster, and our test cases are now passing. This issue can be closed. Thank you. On Tue, Feb 2, 2016 at 3:45 PM, Thomas D'Silva wrote: > I have a patch out for PHOENIX-1769 >

HBase Phoenix Integration

2016-02-26 Thread Amit Shah
Hello, I have been trying to install phoenix on my cloudera hbase cluster. Cloudera version is CDH5.5.2 while HBase version is 1.0. I copied the server & core jar (version 4.6-HBase-1.0) on the master and region servers and restarted the hbase cluster. I copied the corresponding client jar on my