I am sorry. I did not notice the issues have already been assigned.
Best,
Liya Fan
On Sat, Jan 4, 2020 at 12:15 PM Fan Liya wrote:
> Hi Jacques,
>
> I am interested in the issues, and if it is possible, I would like to try
> to resolve them.
>
> Thanks.
>
> Liya Fan
>
> On Sat, Jan 4, 2020 at
Hi Jacques,
I am interested in the issues, and if it is possible, I would like to try
to resolve them.
Thanks.
Liya Fan
On Sat, Jan 4, 2020 at 7:16 AM Jacques Nadeau wrote:
> I identified three things in the java library that I think are top of mind
> and should be fixed before 1.0 to avoid
Hi, Jacques Nadeau
I only found two tickets[1][2], and I am interested in these issues. If you
don't mind, I would like to take a close watch and try to resolve later.
Thanks,
Ji Liu
[1] https://issues.apache.org/jira/browse/ARROW-7494
[2] https://issues.apache.org/jira/browse/ARROW-7495
-
Thanks for reviewing, Jacques. Re: Jira tagging, the convention I've seen
is to use "Fix Version" for open tickets to indicate a target release
(that's what the confluence board draws from, for example). So by my
understanding, Fix Version == 1.0.0 and Priority == Blocker says that
they're things w
I identified three things in the java library that I think are top of mind
and should be fixed before 1.0 to avoid weird incompatibility changes in
the java apis (technical debt). I've tagged them as pre-1.0 as I don't
exactly see what is the right way to tag/label a target release for a
ticket.
ht
Jacques Nadeau created ARROW-7495:
-
Summary: [Java] Remove "empty" concept from ArrowBuf, replace with
custom referencemanager
Key: ARROW-7495
URL: https://issues.apache.org/jira/browse/ARROW-7495
Pro
Jacques Nadeau created ARROW-7494:
-
Summary: [Java] Remove reader index and writer index from ArrowBuf
Key: ARROW-7494
URL: https://issues.apache.org/jira/browse/ARROW-7494
Project: Apache Arrow
Hi Wolfram,
The effort hasn’t stalled. As a volunteer-driven project with developers
coming from modestly funded organizations the progress has not been
overnight. My team (Ursa Labs) has been building infrastructure in support
of this effort (for example, the datasets API and filesystem API, both
Hi.
I’m interested in leveraging (or if does not yet existent co-building) an
"Apache Arrow Query Engine” in C++.
I found various references on the web, eg.
https://docs.google.com/document/d/10RoUZmiMQRi_J1FcPeVAUAMJ6d_ZuiEbaM2Y33sNPu4/edit#heading=h.2k6k5a4y9b8y,
or Gandiva (for Dremio’s eng
Uwe Korn created ARROW-7493:
---
Summary: [Python] Expose sum kernel in pyarrow.compute and support
ChunkedArray inputs
Key: ARROW-7493
URL: https://issues.apache.org/jira/browse/ARROW-7493
Project: Apache Arr
Homebrew has been failing for about a week so I ticketed it here:
https://issues.apache.org/jira/browse/ARROW-7492
On Fri, Jan 3, 2020 at 6:18 AM Crossbow wrote:
>
> Arrow Build Report for Job nightly-2020-01-03-0
>
> All tasks:
> https://github.com/ursa-labs/crossbow/branches/all?query=nightly-
Neal Richardson created ARROW-7492:
--
Summary: [CI][Crossbow] Nightly homebrew-cpp job fails on Python
installation
Key: ARROW-7492
URL: https://issues.apache.org/jira/browse/ARROW-7492
Project: Apach
Arrow Build Report for Job nightly-2020-01-03-0
All tasks:
https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-03-0
Failed Tasks:
- debian-stretch:
URL:
https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-01-03-0-azure-debian-stretch
- gandiva-jar-osx:
Hi Yibo
We’ve found flakiness with protobuf_ep when building in parallel with GNU
Make. There are comments about this in ThirdpartyToolchain.cmake I think
and prior JIRA issues related to this.
For faster builds we generally are focused on using -GNinja so recommend
using the ninja build tool ins
14 matches
Mail list logo
