Hi Micah, I just sent a separate message to the mailing list about the
changes. The discussion is happening on the GitHub pull request and Jira.
On Nov 5, 2021 at 18:25:58, Micah Kornfield wrote:
>
> I added a note to the Arrow 6 release notes in
>
> https://github.com/apache/arrow-site/pull/15
>
> I added a note to the Arrow 6 release notes in
> https://github.com/apache/arrow-site/pull/153/files#r741928109.
Thank you.
> We plan to rewrite a lot of the API in Arrow 7
Sorry I missed them on the mailing list. Were these plans discussed here
(sorry if I missed them, sometimes I filter
Thank you, Micah. We plan to rewrite a lot of the API in Arrow 7 so I think
option 1 would add a lot of overhead. I added a note to the Arrow 6 release
notes in https://github.com/apache/arrow-site/pull/153/files#r741928109.
On Nov 2, 2021 at 22:30:01, Micah Kornfield wrote:
> I'd suggest maybe
Thank you, Micah. We plan to rewrite a lot of the API in Arrow 7 so I
think option 1 would add a lot of overhead. I added a note to the Arrow 6
release notes in
https://github.com/apache/arrow-site/pull/153/files#r741928109.
On Nov 2, 2021 at 22:30:01, Micah Kornfield wrote:
> I'd suggest maybe
I'd suggest maybe two things:
1. If possible add deprecation warnings for the next release, and delete
the release after (we don't have a formal policy but if would be good to
give user heads up before out-right deletion).
2. If 1 isn't an option then please add something to the 6.0.0 release
not
+1 from me as well.
That brings us to 3 times +1 and no -1 or +0.
Thank you, all. We will remove the compute code in the next Arrow version.
On Nov 2, 2021 at 16:12:02, Paul Taylor wrote:
> +1 from me as well
>
> On Oct 27, 2021, at 6:58 PM, Brian Hulette wrote:
>
>
> +1
>
> I don't think t
+1 from me as well
> On Oct 27, 2021, at 6:58 PM, Brian Hulette wrote:
>
>
> +1
>
> I don't think there's much reason to keep the compute code around when
> there's a more performant, easier to use alternative. I think the only unique
> feature of the arrow compute code was the ability to o
+1
I don't think there's much reason to keep the compute code around when
there's a more performant, easier to use alternative. I think the only
unique feature of the arrow compute code was the ability to optimize
queries on dictionary-encoded columns, but Jeff added this to Arquero
almost a year
Dear Arrow community,
We are proposing to remove the compute code from Arrow JS. Right now, the
compute code is encapsulated in a DataFrame class that extends Table. The
DataFrame implements a few functions such as filtering and counting with
expressions. However, the predicate code is not very ef
