Hi Anton, Good point!
I've been working at Telco(MNO) and semiconductor industry for last 3 years. Some prefers our way -- a kind of devops friendly but in enterprises, IT staffs want more managed environment for their big data. Sometimes we do not need the entire stack but management GUI and some selected components would be sufficient. also some people want to try bleeding edge technology and hardwares. I believe your idea is not harmful for this project. It would be rather complementary way for developers and users. Thanks, - Youngwoo On Tue, Dec 19, 2017 at 4:48 PM, Anton Chevychalov <[email protected]> wrote: > > The biggest problem with this kind of switch will be updating all the > software > > that sits on top of Hadoop and making sure it doesn't regress in > functionality. > > That is true and it seems to me it will be a lot of pain to switch version. > That is way it's better to start early. > > While our efforts seems to be too risky for Bigtop, I think it is good > chance to use us as early adopters. But we need to be sure that we are > moving in same direction. And any help would be nice. > > Our plan for next year is a switch from "Ambari way" with one big cluster > per installation to multiple small clusters with different versions. > For that paradigm it is nice to have not only solid rock version (like > 1.2). > > > On 18 December 2017 at 22:29, Roman Shaposhnik <[email protected]> > wrote: > > > On Mon, Dec 18, 2017 at 2:26 AM, Антон Чевычалов <[email protected]> > wrote: > > > Hi Everyone! > > > > > > Could someone tell me a vision about Bigtop's future. We are trying to > > > deliver software faster and intend to make some changes in our system > to > > > allow our customer have new versions as fast as it possible. Does it > make > > > sense for Bigtop Community or we should find our own way? > > > > > > As first and big move we intend to switch to Hadoop 3.x and start > working > > > with Ignite 2.x. Dead line is April 2018. > > > > The biggest problem with this kind of switch will be updating all the > > software > > that sits on top of Hadoop and making sure it doesn't regress in > > functionality. > > > > It isn't trivial, but if you're willing to do the work -- I'm sure > > we'll be more than > > happy to review patches. > > > > Thanks, > > Roman. > > > > > > -- > Anton B Chevychalov > CI/CD Engineer of ArenaData >
