Re: Improving PR workload management for Arrow maintainers

2021-07-01 Thread Adam Lippai
Not sure if it's applicable, but GitHub is improving: https://github.blog/changelog/2021-06-23-whats-new-with-github-issues/ That spreadsheet-like issue tracking looks concise. Best regards, Adam Lippai On Wed, Jun 30, 2021, 10:28 Antoine Pitrou wrote: > > Le 30/06/2021 à 10:04, Wes McKinney

Re: [VOTE] Arrow should state a convention for encoding instants as Timestamp with "UTC" as the time zone

2021-07-01 Thread Eduardo Ponce
+1 (non-binding) ~Eduardo From: Rok Mihevc Sent: Thursday, July 1, 2021 4:21:49 AM To: dev@arrow.apache.org Subject: Re: [VOTE] Arrow should state a convention for encoding instants as Timestamp with "UTC" as the time zone +1 (non-binding) On Thu, Jul 1,

Re: [Discuss] Consider renaming "Arrow" in HO2 benchmarks?

2021-07-01 Thread Jorge Cardoso Leitão
Hi, I did not know what to change there for renaming the bench, as the bench name seems to be used in different places. I thus started with an issue, https://github.com/h2oai/db-benchmark/issues/229. Best, Jorge On Fri, Jun 25, 2021 at 1:04 PM Wes McKinney wrote: > I recommend sending a PR

Re: [Python] ascii_trim bug & documentation

2021-07-01 Thread Joris Van den Bossche
Hi, I think this is fixed on the master branch. With master, I get: >>> pc.utf8_trim("aba", characters="a") >>> pc.ascii_trim("aba", characters="a") while with released pyarrow 4.0.1, the second one indeed raises an error (not directly sure when it was fixed). For the documentation,

Re: [VOTE] Arrow should state a convention for encoding instants as Timestamp with "UTC" as the time zone

2021-07-01 Thread Rok Mihevc
+1 (non-binding) On Thu, Jul 1, 2021 at 6:40 AM Bryan Cutler wrote: > +1 non-binding > > On Wed, Jun 30, 2021, 2:53 AM Weston Pace wrote: > > > This vote is a result of previous discussion[1][2]. This vote is also > > a prerequisite for the PR in [5]. > > > > --- > > Some date & time