[GitHub] [arrow-datafusion] ovr commented on issue #2679: Proposal: remove automated ballista CI checks from DataFusion

[GitBox <gi...@apache.org>]

ovr commented on issue #2679:
URL: https://github.com/apache/arrow-datafusion/issues/2679#issuecomment-1144922939

   > I would be interested to hear how others keep up with pre-release DataFusion as well (maybe @ovr and cube-js?)
   
   We have two separate projects in the company which use DF as a Query Engine, and we came to the decision to maintain two different versions in the forked repository because it's impossible to use the latest version, there are some problems:
   
   It's hard to contribute back to the upstream. We had subqueries before DF introduced it, We have ANY and UDTFs, etc. We tried to push it back to the upstream, but It's not merged and probably, will not be merged soon.
   
   https://github.com/apache/arrow-datafusion/pull/2549
   https://github.com/apache/arrow-datafusion/pull/2177
   
   Rebasing PRs/Forks when someone loves to move functions/doing breaking changes on daily basis is funny 😄 
   Don't forget that DF relies on the SQL parser & Arrow which we already forked. The same story, it requires rebasing each time :D
   
   For my project, we rebase every 1-2 months. While rebasing we choose the latest commit from the `master` branch (We don't wait for releases).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org