Why shaded Datastax java-driver?

[Tomas Repik <tr...@redhat.com>]

Hello list,
why is datastax java-driver so tightly fixed to the cassandra base?
Is there any reason to have it as a shaded dependency?
And what even a shaded dependency is?

I'd be glad for any response.

Thanks Tomas

Re: Why shaded Datastax java-driver?

[Tomas Repik <tr...@redhat.com>]

Well good to know. Then I think the optional="true" attribute of the java driver in build.xml is misleading. If you didn't include the java driver, you're not able to build cassandra as far as I'm trying. I've already suggested a cassandra-common.jar in another topic (Cassandra client) and I'm glad that I'm not the only one thinking about such thing. Is there any chance that the idea would be considered by upstream? 

----- Original Message -----
> Some of the tools use the driver, and there is some reliance on classes
> for user defined types that come from the driver. I suppose ideally
> these would get split out into a cassandra-common.jar, or such.
> 
> 
> "Shaded" in this case means that the jar contains code from netty, but
> the package structure is changed so that there are no conflicts with a
> real netty jar.
> 

Re: Why shaded Datastax java-driver?

[Dave Brosius <db...@mebigfatguy.com>]

Some of the tools use the driver, and there is some reliance on classes 
for user defined types that come from the driver. I suppose ideally 
these would get split out into a cassandra-common.jar, or such.


"Shaded" in this case means that the jar contains code from netty, but 
the package structure is changed so that there are no conflicts with a 
real netty jar.


On 01/30/2017 11:26 AM, Tomas Repik wrote:
> Hello list,
> why is datastax java-driver so tightly fixed to the cassandra base?
> Is there any reason to have it as a shaded dependency?
> And what even a shaded dependency is?
>
> I'd be glad for any response.
>
> Thanks Tomas
>