Re: Dropping support for Guava versions earlier than 14

2016-09-03 Thread Andrew Purtell
I wouldn't call embedding Guava types in a public API either a service for users nor good API design, given the pain I've personally seen it inflict on multiple projects given Google's uncaring nature on cross version compatibility. > On Sep 3, 2016, at 5:35 PM, Jacques Nadeau

Re: Dropping support for Guava versions earlier than 14

2016-09-03 Thread Jacques Nadeau
Do you have a sense of how often we expose these? One random thought, shade Guava and continue to expose the shaded.guava classes in public APIs. People could choose to use the unshaded or shaded. On Sat, Sep 3, 2016 at 11:26 AM, Julian Hyde wrote: > I'm not keen on shading

Re: Dropping support for Guava versions earlier than 14

2016-09-03 Thread Michael Mior
Calcite will work with Guava 16 and currently does use the Cassandra 3.x driver. -- Michael Mior michael.m...@gmail.com On Sep 3, 2016 05:03, "CPC" wrote: > Cassandra driver 3.x require min guava 16.0.1. If it detects an earlier > version in classpath it stops working. > > On

Re: Dropping support for Guava versions earlier than 14

2016-09-03 Thread Julian Hyde
I'm not keen on shading Guava, because I want to include some of Guava's classes in Calcite's public API: for example ImmutableList and Function. Using these classes in APIs makes better APIs. They should be in the JDK, but sadly they're not, so we use Guava. Calcite's policy has been to support

Re: Dropping support for Guava versions earlier than 14

2016-09-03 Thread Andrew Purtell
Use hbase-shaded-client as Maven dep (1.1 and up) > On Sep 3, 2016, at 10:12 AM, James Taylor wrote: > > Does shading of protobuf on the HBase client work (or is that dependent on > that brave work Stack is doing)? > > On Sat, Sep 3, 2016 at 10:10 AM, Andrew Purtell

Re: Dropping support for Guava versions earlier than 14

2016-09-03 Thread James Taylor
Does shading of protobuf on the HBase client work (or is that dependent on that brave work Stack is doing)? On Sat, Sep 3, 2016 at 10:10 AM, Andrew Purtell wrote: > James - When Stack is finished coprocessors will work with shaded > protobuf. Not yet. > > > On Sep 3,

Re: Dropping support for Guava versions earlier than 14

2016-09-03 Thread Andrew Purtell
James - When Stack is finished coprocessors will work with shaded protobuf. Not yet. > On Sep 3, 2016, at 10:07 AM, James Taylor wrote: > > Also agree - shading of guava & protobuf would be super valuable. Phoenix > ended up not supporting shading of protobuf because

Re: Dropping support for Guava versions earlier than 14

2016-09-03 Thread James Taylor
Also agree - shading of guava & protobuf would be super valuable. Phoenix ended up not supporting shading of protobuf because of difficulties getting it to work (maybe because HBase dependency?). I think we support shading of Guava, though. Is that correct, Sergey? On Sat, Sep 3, 2016 at 10:02

Re: Dropping support for Guava versions earlier than 14

2016-09-03 Thread Jacques Nadeau
+1 on shading guava/protobuf. On Sat, Sep 3, 2016 at 9:48 AM, Andrew Purtell wrote: > Since Calcite should become a widely used library (smile) I think it would > be prudent to shade Guava and protobuf if Calcite depends on them. Then you > will play very nicely indeed

Re: Dropping support for Guava versions earlier than 14

2016-09-03 Thread Andrew Purtell
Since Calcite should become a widely used library (smile) I think it would be prudent to shade Guava and protobuf if Calcite depends on them. Then you will play very nicely indeed on the classpath no matter what versions are required by calling code. Jacques - Good lord. Let me see about

Re: Dropping support for Guava versions earlier than 14

2016-09-03 Thread Jacques Nadeau
It isn't a real solution but in Drill we solved the HBase incompatibility issue on the server side (for tests only) by patching Guava 18 to allow the HBase Guava calls that are missing. They are really quite trivial and support Andrew's arguments that Guava is the devil...

Re: Dropping support for Guava versions earlier than 14

2016-09-03 Thread Andrew Purtell
While that seems very unfriendly of them, the main issue is Guava is the devil (and protobuf is a minor demon). Would shading be an option? > On Sep 3, 2016, at 2:03 AM, CPC wrote: > > Cassandra driver 3.x require min guava 16.0.1. If it detects an earlier > version in

Re: Simple Streaming Senario

2016-09-03 Thread Γιώργος Θεοδωράκης
When I tried a query like SELECT STREAM ss.depts.deptno FROM ss.depts WHERE ss.depts.deptno < 30; it gave me a correct answer on the SDEPTS.cvs in sales folder with both my json and model-stream-table.json. I only had to declare better where to find the tables and the columns, because with only

Simple Streaming Senario

2016-09-03 Thread Γιώργος Θεοδωράκης
I am trying to create a simple streaming query ( like SELECT STREAM * FROM ORDERS WHERE units > 10). I have created a stream using a socket that saves the orders in an sOrders.csv file and I have changed the model-stream-table.json like this: { version: '1.0', defaultSchema: 'CUSTOM_TABLE',

Re: Dropping support for Guava versions earlier than 14

2016-09-03 Thread CPC
Cassandra driver 3.x require min guava 16.0.1. If it detects an earlier version in classpath it stops working. On Sep 3, 2016 04:26, "Julian Hyde" wrote: > James & Andrew, I hear you. We’ll stay on Guava 12 if we have to. > > But can we try an experiment to see if it’s