On Thu, Mar 2, 2017 at 2:08 PM, Alan Gates wrote:
> I think the issues you point out fall into a couple of different buckets:
>
> 1) Spark forking Hive code. As you point out, based on the license,
> there's nothing wrong with this (see naming concerns below). I agree it's
> crappy technical pr
I think the issues you point out fall into a couple of different buckets:
1) Spark forking Hive code. As you point out, based on the license, there's
nothing wrong with this (see naming concerns below). I agree it's crappy
technical practice because in the long term Hive and Spark will diverge
On Thu, Mar 2, 2017 at 12:35 PM, Gopal Vijayaraghavan
wrote:
>
> > Had the original Spark proposal implied they wished to fork portions of
> the hive
> > code base, I would have considered it a hostile fork. (this is open to
> interpretation).
>
> FYI, I did ask bluntly whether Spark intends to c
> Had the original Spark proposal implied they wished to fork portions of the
> hive
> code base, I would have considered it a hostile fork. (this is open to
> interpretation).
FYI, I did ask bluntly whether Spark intends to cut-paste Hive code into their
repos previously & got an affirmative
All,
I have compiled a short (non exhaustive) list of items related to Spark's
forking of Apache Hive code and usage of Apache Hive trademarks.
1)
The original spark proposal repeatedly claims that Spark "inter operates"
with hive.
https://wiki.apache.org/incubator/S
