Arrow policy on rewriting git history?

I've noticed that specific commits sometimes disappear from the master branch. Is this an inevitable consequence of the way Arrow does releases? Or would it be possible to avoid removing commits from the master branch? Of course once we start using Arrow releases this won't be an issue. At the mom

[jira] [Created] (ARROW-2002) use pyarrow download file will raise queue.FULL exceptions sometimes

kmiku7 created ARROW-2002: - Summary: use pyarrow download file will raise queue.FULL exceptions sometimes Key: ARROW-2002 URL: https://issues.apache.org/jira/browse/ARROW-2002 Project: Apache Arrow

Re: Trying to build to build pyarrow for python 2.7

hi Simba -- the PyPI / pip wheels will only be updated when there is a new release. We'll either make a 0.8.1 release or 0.9.0 sometime in February depending on how development is progressing. - Wes On Sun, Jan 14, 2018 at 9:19 AM, simba nyatsanga wrote: > Thanks a lot. I see that there's a PR

[jira] [Created] (ARROW-2001) Add getInitReservation() to BufferAllocator interface similar to getLimit(), getHeadRoom() APIs

Siddharth Teotia created ARROW-2001: --- Summary: Add getInitReservation() to BufferAllocator interface similar to getLimit(), getHeadRoom() APIs Key: ARROW-2001 URL: https://issues.apache.org/jira/browse/ARROW-200