Hey All,
Apologies ahead of time for the potential spam. I have been working with
Jacques and co for about 6 months to bring Dremio to our front office
trading organisation at UBS. We are now expanding the team and I am looking
to hire some killer devs in London to work on Arrow, Gandiva and
Philipp Moritz created ARROW-2758:
-
Summary: [Plasma] Use Scope enum in Plasma
Key: ARROW-2758
URL: https://issues.apache.org/jira/browse/ARROW-2758
Project: Apache Arrow
Issue Type:
Philipp Moritz created ARROW-2757:
-
Summary: [Plasma] Huge pages test failing
Key: ARROW-2757
URL: https://issues.apache.org/jira/browse/ARROW-2757
Project: Apache Arrow
Issue Type:
Hi,
There has been a recent pr 2171 for ARROW-2015 to replace Joda time with
Java8 time.
I think this change is good as we move toward newer Java version and wonder
if we should include this in the 0.10 release.
The biggest concern is that this is a breaking change and could impact
downstream
I won't be able to make it today.
On Wed, Jun 27, 2018 at 10:48 AM Wes McKinney wrote:
> https://meet.google.com/vtm-teks-phx
>
Hello Wes, Antoine,
Thanks for your very detailed responses!
It is really good to know that what is in arrow/gpu now is already setup to
integrate into various GPU producer / consumers.
The other responses made sense (assume in-memory and rely on orchestration,
explicit over implicit, roadmap
https://meet.google.com/vtm-teks-phx
Krisztian Szucs created ARROW-2756:
--
Summary: [Python] Reduce redundant imports and minor fixes in
parquet tests
Key: ARROW-2756
URL: https://issues.apache.org/jira/browse/ARROW-2756
Project: Apache
Krisztian Szucs created ARROW-2755:
--
Summary: [Python] Allow using Ninja to build extension
Key: ARROW-2755
URL: https://issues.apache.org/jira/browse/ARROW-2755
Project: Apache Arrow
Issue
> I'm not sure this makes sense as an external stable api. I definitely think
> it is useful as an internal representation for use within a particular
> algorithm. I also think that can be informed by the particular algorithm that
> you're working on.
I agree that this is definitely needed in
Wes McKinney created ARROW-2754:
---
Summary: [Python] When installing pyarrow via pip, a debug build
is created
Key: ARROW-2754
URL: https://issues.apache.org/jira/browse/ARROW-2754
Project: Apache Arrow
Kouhei Sutou created ARROW-2753:
---
Summary: [GLib] Add garrow_schema_*_field()
Key: ARROW-2753
URL: https://issues.apache.org/jira/browse/ARROW-2753
Project: Apache Arrow
Issue Type: New
I am wondering if this can be considered as an opportunity to implement
support in Arrow for building high performance in-memory row stores for low
latency and high throughput key based queries. In other words, we can
design the in-memory record format keeping efficient RDMA reads as one of
the
Kouhei Sutou created ARROW-2752:
---
Summary: [GLib] Document garrow_decimal_data_type_new()
Key: ARROW-2752
URL: https://issues.apache.org/jira/browse/ARROW-2752
Project: Apache Arrow
Issue
Kouhei Sutou created ARROW-2751:
---
Summary: [GLib] Add garrow_table_replace_column()
Key: ARROW-2751
URL: https://issues.apache.org/jira/browse/ARROW-2751
Project: Apache Arrow
Issue Type: New
Sorry for the delay, Julian. My replies inline.
On Fri, Jun 22, 2018 at 11:39 PM Julian Hyde wrote:
> This is exciting. We have wanted to build an Arrow adapter in Calcite for
> some time and have a prototype (see
> https://issues.apache.org/jira/browse/CALCITE-2173 <
>
16 matches
Mail list logo
