That’s interesting question and we will have to think from feature/performance perspective as well as what versions of platforms do we want to support (and this could be dependent on immediate users of Metron)
Since we are just starting, its good opportunity to think and make better choice. Changing versions later becomes difficult. I am inlined towards using newer (not necessarily the latest) stable releases for these reasons 1. There have been bunch of performance and stability improvements gone in almost all components recently (Storm, HDFS, HBase etc), and performance could be critical for scale 2. Most of hadoop projects try to be backward API compatible, so if someone needs to make it work with older versions, it may not be too painful 3. There are new features such as hive steaming ingest, that would be very helpful for both performance as well as hive analytics 4. Since Metron depends on many different platform components, its going to be as stable and reliable as the weakest component it. So newer stable release would make it better. ~ Sheetal On 12/9/15, 11:48 AM, "Bryan Taylor" <[email protected]> wrote: > >Seems like a good list. I'm probably not your UI guy, but I'll be happy to >help with any of the others. Test coverage is probably a good place for me >to start learning my way around. Do we have CI set up? I see a travis file >in the code. > >Regarding automation deployments, are we targeting Ambari or something >else? > >On the hadoop component compatibility, I see from the opens-streaming pom >that we are using Storm-0.9.2, Kafka 0.8.0, Hadoop 2.2.0, and HBase >0.98.0-hadoop2. These are all several iterations old. How aggressive do we >want to be, generally, with tracking new releases? Are Hive, Flume, and >Spark also going to up rev for us? > >Bryan > >On 12/9/15 12:22 PM, "James Sirota" <[email protected]> wrote: > >>Hi Brian, >> >>Welcome. Glad to have you contribute. There will be changes to the code >>base that the community will contribute back shortly. We are waiting for >>the Jira to be setup so the backlog can be created and voted on. I think >>the overall feeling is that we need to make the code base compatible with >>the latest version of HDP, automate deployments, increase test coverage, >>and start working on a new UI. There may be more significant >>architectural changes to the code base, but we need to get the essential >>items knocked out before we go there. >> >>Thanks, >>James >> >> >> >> >>On 12/9/15, 11:52 AM, "Bryan Taylor" <[email protected]> wrote: >> >>>Hi Folks, >>> >>>I just joined the list and thought I'd say "hi". I work at Rackspace and >>>will be joining Andrew Hartnett's team there and hacking on metron. This >>>is my first ASF project and I'm looking forward to being part of this >>>community. >>> >>>I'm curious what the development vision is for metron. What do people >>>like and not like about the codebase? I gather this code transitioned >>>from a Cisco internal project and is incubating now at the ASF. Are >>>there any code changes that need to be made to support incubation? >>> >>>Bryan > >
