While I feel Storm SQL covers (and will cover in near future) all of the features what SQE has, I'd like to consider this as not only code donation but also having more contributors on Storm SQL.
As the one working on storm-sql now, I think Storm SQL should have more contributors who are experienced or expert on this area, or at least have a mind to contribute heavily. There're still many features to implement (join and windowing, parallelism, and so on) which needs some efforts so we can boost up if more contributors would play with Storm SQL. And "optimization" is at the heart of SQL and we haven't had time, and knowledge, and experience to address that. IMHO, Storm SQL seems to be going on the right track so I don't think we need to replace the codebase or merge. We can still apply the advanced areas of SQE to Storm SQL via normal pull requests (code donation resolves the IP clearance so should be easy to do). I'd be more appreciated if this is a signal for them to contribute Storm SQL directly. Thanks, Jungtaek Lim (HeartSaVioR) 2016년 8월 25일 (목) 오전 12:17, P. Taylor Goetz <[email protected]>님이 작성: > JW Player has offered to donate SQE (Streaming Query Engine) to the Storm > project. > > SQE is a query engine built on top of Trident that uses a SQL-like syntax > (currently JSON-based) to query streams. There is obvious overlap between > this and storm-sql, and this might be an opportunity to improve Storm’s SQL > support. > > The code and documentation can be found here [1]. > > -Taylor > > [1] https://github.com/jwplayer/SQE >
