houqp commented on pull request #1795:
URL: 
https://github.com/apache/arrow-datafusion/pull/1795#issuecomment-1061541786


   @Igosuki that's great, I tried to manually unsquash the previous commit 
commits, but it turned out to be too much work and not worth it. I took a quick 
look at your arrow2 branch and it looks clean without those two squashed 
commits. I think we can just force push your arrow2 branch into the one in 
datafusion's repo, then use merge commits going forward for future catch ups. 
If you are ok with this approach, please feel free to send a PR, once reviewed 
by the community, I can help perform the force push to replace the current 
arrow2 branch.
   
   https://git-scm.com/docs/gitfaq#long-running-squash-merge has guidance on 
how to best maintain long running branches, which should help explain why merge 
commits will help make future merges easier.
   
   Once we have the arrow2 branch updated, I will get back to performance 
testing. I remember running into a performance regression around window 
queries, so that would be the next thing I will dig into.


-- 
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-unsubscr...@arrow.apache.org

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


Reply via email to