Re: [DISCUSS] ORC separate project

2015-04-15 Thread Owen O'Malley
On Mon, Apr 13, 2015 at 10:43 PM, Sergey Shelukhin wrote: > The 2nd concern about fixing issue quickly doesn¹t make sense - it can > happen with any dependency. What if guava or Kryo or Spark or Tez have a > bug? We can still ship Hive as long as the dependency can be updated to > correct version

Re: [DISCUSS] ORC separate project

2015-04-15 Thread Owen O'Malley
On Mon, Apr 13, 2015 at 10:43 PM, Sergey Shelukhin wrote: > The 2nd concern about fixing issue quickly doesn¹t make sense - it can > happen with any dependency. What if guava or Kryo or Spark or Tez have a > bug? We can still ship Hive as long as the dependency can be updated to > correct version

Re: [DISCUSS] ORC separate project

2015-04-13 Thread Sergey Shelukhin
IMHO there are 2 separate concerns, forking ORC and Hive using ³new² ORC. The first one does not really require vote, as discussed on private/board - anyone can fork part of code (in this case, at least). Then, for Hive switching to ³new² ORC, I¹m not sure that requires a vote either. We didn¹t vot

Re: [DISCUSS] ORC separate project

2015-04-11 Thread Lefty Leverenz
Speaking of the C++ ORC reader and writer, could they be included in the Hive project or do they have to be separate because they aren't Java code? By the way, gmail thwarts adding [DISCUSS] to the subject line. It shows up in the mail archives, although pre- & post-DISCUSS threads are separate.

Re: [DISCUSS] ORC separate project

2015-04-10 Thread Gopal Vijayaraghavan
On 4/10/15, 8:05 PM, "Xuefu Zhang" wrote: >To Owen's explanation - Thanks. I guess my major concern is that we >seemingly are breaking apart Hive's integrity and making it hard to >release >and maintain due to increasing number of external dependents. Let's say >that Hive depends on a certain v

Re: [DISCUSS] ORC separate project

2015-04-10 Thread Xuefu Zhang
To Lefty's comment - Yes, anyone can take Apache code and make another project at will. However, for changes made to an existing project as part of that process, such as what Owen described for ORC in Hive, it is certainly something that Hive PMC can control or vote on. Nevertheless, that's not my

Re: [DISCUSS] ORC separate project

2015-04-08 Thread Owen O'Malley
On Tue, Apr 7, 2015 at 8:49 PM, Xuefu Zhang wrote: > If I understood Allen's #2 comment, we are moving existing ORC code out of > Hive and make it a separate project, which I definitely missed. > I'm sorry that wasn't clear. Yes, most of the code that is currently in org.apache.hadoop.hive.ql.io

Re: [DISCUSS] ORC separate project

2015-04-08 Thread Owen O'Malley
On Mon, Apr 6, 2015 at 11:26 PM, Brock Noland wrote: > Hey guys, > > Good discussion here. One point of order, I feel like this should be a > [DISCUSS] thread. Ok, I've edited the subject on this reply. At the very least, this will hit people's filters. .. Owen