If bigtop is really the "fedora" of bigdata distros, then moving to Java 7 is the natural thing to do.
Fedora integrates the trailblazing linux technology - without fear of consequences.... and I see BigTop as doing the exact same thing in the hadoop community.
For me -- BigTop is a platform to innovate and do cool new stuff on -- so I say keep it that way and keep fearlessly moving forward :) On Thu, Jun 26, 2014 at 6:34 PM, Roman Shaposhnik <[EMAIL PROTECTED]> wrote: jay vyas
I totally agree, I don't know if it makes sense to bring in the complexity of switching out major java version for Bigtop 0.8 at this point. On Thu, Jun 26, 2014 at 3:59 PM, jay vyas <[EMAIL PROTECTED]> wrote:
I beg to differ: Bigtop is a Debian of bigdata ;) Agree with the rest though. However, the question is about timing. I'd say: we can try to give it a full build attempt using nothing but JDK7 and see how the things are going. If something breaks - we can do 0.8.1. which will only be focused on JDK7 upgrade. Thought?
On Thu, Jun 26, 2014 at 7:03 PM, Andrew Purtell <[EMAIL PROTECTED]> wrote:
At this point, I'd suggest biting the bullet and declaring 0.8.0 JDK7+ only. Even for build. Three of the dozen or so projects already refuse to be built by anything but: * Hue 3.6 (can be hacked to stay with JDK6, but who will do it?) * Solr 4.9.0 (ditto) * Giraph 1.1.0 (not sure whether JDK7 specific functionality remains)
So, unless somebody volunteers to solve all three of the above, I think 0.8.0 is about to move to JDK7.
On Tue, Jul 1, 2014 at 10:39 AM, Mark Grover <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation projects and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext