On Thu, Jul 25, 2013 at 9:48 PM, Edward Capriolo <edlinuxg...@gmail.com>wrote:
> I have been developing my laptop on a duel core 2 GB Ram laptop for years > now. With the addition of hcatalog, hive-thrift2, and some other growth > trying to develop hive in a eclipse on this machine craws, especially if > 'build automatically' is turned on. As we look to add on more things this > is only going to get worse. > > I am also noticing issues like this: > > https://issues.apache.org/jira/browse/HIVE-4849 > > What I think we should do is strip down/out optional parts of hive. > > 1) Hive Hbase > This should really be it's own project to do this right we really have to > have multiple branches since hbase is not backwards compatible. > > 2) Hive Web Interface > Now really a big project but not really critical can be just as easily be > build separately > > 3) hive thrift 1 > We have hive thrift 2 now, it is time for the sun to set on hivethrift1, > > 4) odbc > Not entirely convinced about this one but it is really not critical to > running hive. > > What I think we should do is create sub-projects for the above things or > simply move them into directories that do not build with hive. Ideally they > would use maven to pull dependencies. > > What does everyone think? > I agree that projects like the HBase handler and probably others as well should somehow be "downstream" projects which simply depend on the hive jars. I see a couple alternatives for this: * Take the "module" in question to the Apache Incubator * Move the "module" in question to the Apache Extras * Breakup the projects within our own source tree I'd prefer the third option at this point. Brock Brock
