Who is interested in starting a company to revive this project?

[imku...@gmail.com]

Can someone explain to me why this is abandoned from a technical standpoint?  I have looked around at many alternatives,  HDP, MAPR, Dremio, Splunk etc, and so far this tool seems to be still far more friendly after 4 years of ceasing development. 

Can Apache foundation take it over?  

Or maybe some people here are willing to create a small company to revive it?  I'm interested. 

[Aqe Pierre-A]

Maybe creating a small company will be for later on. But I am in to bring back this project to life.

[Marcus Mattson]

For what its worth, I was a prospective customer of Think Big Analytics - the small company that started Kylo. For several reasons, we could not adopt it. The primary issues being around authentication and authorization - it was not mature.Then Teradata purchased Think Big Analytics, they had intentions of growing it. Obviously that came to an end.

Kylo is primarily based on Apache NiFi. NiFi is API-driven, so it can definitely be orchestrated by wrap-around software, but any developers that work with Kylo will need to be focused not only on Kylo, but also on Apache NiFi.

Kylo has an audience, but based on my observation of this group, that audience primarily wants free (as in beer) software. If there were already two failed attempts to monetize it, it may be worth considering whether that is a worthwhile endeavor - if the desire is to monetize it.

[imku...@gmail.com]

Thank you for sharing your story. 

I am surprised that the main issues for your company were around security rather than functionality.  What did your company go for instead?

[TR]

this project looks to have a lot of use and promise.  I'm interested! 

[imku...@gmail.com]

It doesn't have to be a company either.   I'm not a programmer,   but I'm interested in participating.  

A plan of actions should probably include: 

1.  fork the current github repository,  so that motivated people can focus on bring it back to life. 

2.  deciding some milestones such as 

2.1 crucial bug fixes. 

2.1 bring all related backend dependencies especially nifi, spark etc to the latest versions. 

2.2 bring frontend dependencies such as angular to latest versions. 

2.3  design and implement  example cases and implement them as bundled test scenarios with docker. 

2.4  review and update all documentations etc.  

It seems a lot of work, lol.  

[TR]

Did anyone ever build a container for kylo? 

[Aaron Kramer]

Like others, I think company is the wrong word, but I am totally interested in reviving this. Do we know of any other open source competitors currently in the space?

[Fai Cheng]

Looking for a tools to process some data and sadly it's dead.

If revive Kylo, I think one issue maybe using ElasticSearch. In my understanding ES update so frequently so it will add difficulties for third parties.

But will try to install a Kylo and see how difficult to containerise it.