[RESULT] Re: [VOTE][RUST] Release Apache Arrow Rust 28.0.0 RC1

[Andrew Lamb]

On Mon, Nov 28, 2022 at 5:08 PM Andrew Lamb  wrote:

> With 9 +1 (4 binding) the release is approved. Thank you as always for all
> your help
>
> The release is available here:
>   https://dist.apache.org/repos/dist/release/arrow/arrow-rs-28.0.0
>
> It has also been published to crates.io
>
> Thanks again!
> Andrew
>
>
> On Mon, Nov 28, 2022 at 8:17 AM Raphael Taylor-Davies
>  wrote:
>
>> +1 (binding)
>>
>> On 25/11/2022 19:42, Andrew Lamb wrote:
>> > To: dev@arrow.apache.org
>> > Subject: [VOTE][RUST] Release Apache Arrow Rust 28.0.0 RC1
>> >
>> > Hi,
>> >
>> > I would like to propose a release of Apache Arrow Rust Implementation,
>> > version 28.0.0.
>> >
>> > This release candidate is based on commit:
>> > eb91dac6e99b0bcbcbd8057b03233059089bbf27 [1]
>> >
>> > The proposed release tarball and signatures are hosted at [2].
>> >
>> > The changelog is located at [3].
>> >
>> > Please download, verify checksums and signatures, run the unit tests,
>> > and vote on the release. There is a script [4] that automates some of
>> > the verification.
>> >
>> > The vote will be open for at least 72 hours.
>> >
>> > [ ] +1 Release this as Apache Arrow Rust
>> > [ ] +0
>> > [ ] -1 Do not release this as Apache Arrow Rust  because...
>> >
>> > [1]:
>> >
>> https://github.com/apache/arrow-rs/tree/eb91dac6e99b0bcbcbd8057b03233059089bbf27
>> > [2]:
>> https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-rs-28.0.0-rc1
>> > [3]:
>> >
>> https://github.com/apache/arrow-rs/blob/eb91dac6e99b0bcbcbd8057b03233059089bbf27/CHANGELOG.md
>> > [4]:
>> >
>> https://github.com/apache/arrow-rs/blob/master/dev/release/verify-release-candidate.sh
>> >
>>
>

Re: [VOTE][RUST] Release Apache Arrow Rust 28.0.0 RC1

[Andrew Lamb]

With 9 +1 (4 binding) the release is approved. Thank you as always for all
your help

The release is available here:
  https://dist.apache.org/repos/dist/release/arrow/arrow-rs-28.0.0

It has also been published to crates.io

Thanks again!
Andrew


On Mon, Nov 28, 2022 at 8:17 AM Raphael Taylor-Davies
 wrote:

> +1 (binding)
>
> On 25/11/2022 19:42, Andrew Lamb wrote:
> > To: dev@arrow.apache.org
> > Subject: [VOTE][RUST] Release Apache Arrow Rust 28.0.0 RC1
> >
> > Hi,
> >
> > I would like to propose a release of Apache Arrow Rust Implementation,
> > version 28.0.0.
> >
> > This release candidate is based on commit:
> > eb91dac6e99b0bcbcbd8057b03233059089bbf27 [1]
> >
> > The proposed release tarball and signatures are hosted at [2].
> >
> > The changelog is located at [3].
> >
> > Please download, verify checksums and signatures, run the unit tests,
> > and vote on the release. There is a script [4] that automates some of
> > the verification.
> >
> > The vote will be open for at least 72 hours.
> >
> > [ ] +1 Release this as Apache Arrow Rust
> > [ ] +0
> > [ ] -1 Do not release this as Apache Arrow Rust  because...
> >
> > [1]:
> >
> https://github.com/apache/arrow-rs/tree/eb91dac6e99b0bcbcbd8057b03233059089bbf27
> > [2]:
> https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-rs-28.0.0-rc1
> > [3]:
> >
> https://github.com/apache/arrow-rs/blob/eb91dac6e99b0bcbcbd8057b03233059089bbf27/CHANGELOG.md
> > [4]:
> >
> https://github.com/apache/arrow-rs/blob/master/dev/release/verify-release-candidate.sh
> >
>

RE: [DISCUSS] JSON Canonical Extension Type

[Lee, David]

Can a logical extension be based on another logical extension?

HOCON support might be nice..

-Original Message-
From: Micah Kornfield  
Sent: Monday, November 28, 2022 11:50 AM
To: dev@arrow.apache.org
Subject: Re: [DISCUSS] JSON Canonical Extension Type

External Email: Use caution with links and attachments


This seems like a reasonable definition to me.  Since there hasn't been much 
feedback, I think maybe following through an implementation + this description 
in a PR would be the next steps.  If there isn't further feedback on this, once 
the PR is up we can have try to vote (which might bring up some more feedback, 
but hopefully wouldn't cause too much implementation churn).

Thanks,
Micah

On Thu, Nov 17, 2022 at 3:58 PM Pradeep Gollakota 
 wrote:

> Hi folks!
>
> I put together this specification for canonicalizing the JSON type in 
> Arrow.
>
> ## Introduction
> JSON is a widely used text based data interchange format. There are 
> many use cases where a user has a column whose contents are a JSON 
> encoded string. BigQuery's [JSON Type][1] and Parquet’s [JSON Logical 
> Type][2] are two such examples.
>
> The JSON specification is defined in [RFC-8259][3]. However, many of 
> the most popular parsers support non standard extensions. Examples of 
> non standard extensions to JSON include comments, unquoted keys, 
> trailing commas, etc.
>
> ## Extension Specification
> * The name of the extension is `arrow.json`
> * The storage type of the extension is `utf8`
> * The extension type has no parameters
> * The metadata MUST be either empty or a valid JSON object
> - There is no canonical metadata
> - Implementations MAY include implementation-specific metadata by 
> using a namespaced key. For example `{"google.bigquery": {"my": 
> "metadata"}}`
> * Implementations...
> - MUST produce valid UTF-8 encoded text
> - SHOULD produce valid standard JSON
> - MAY produce valid non-standard JSON
> - MUST support parsing standard JSON
> - MAY support parsing non standard JSON
> - SHOULD pass through contents that they do not understand
>
> ## Forward compatibility
> In the future we might allow this logical type to annotate a byte 
> storage type with a different text encoding.  Implementations 
> consuming JSON logical types should verify this.
>
> [1]:
>
> https://urldefense.com/v3/__https://cloud.google.com/bigquery/docs/reference/standard-sql/data-types*json_type__;Iw!!KSjYCgUGsB4!YhB-EpSLu8HTacaUsWvTVqF0kYh81UlVwNFBAc4-f95F7bGtdGuyWN_JObBkRSee-jTU20_MmGe2WUH8UMqTxPY$
> [2]:
> https://urldefense.com/v3/__https://github.com/apache/parquet-format/blob/master/LogicalTypes.md*json__;Iw!!KSjYCgUGsB4!YhB-EpSLu8HTacaUsWvTVqF0kYh81UlVwNFBAc4-f95F7bGtdGuyWN_JObBkRSee-jTU20_MmGe2WUH8RFfD8NY$
> [3]: 
> https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/rfc8259__;!!KSjYCgUGsB4!YhB-EpSLu8HTacaUsWvTVqF0kYh81UlVwNFBAc4-f95F7bGtdGuyWN_JObBkRSee-jTU20_MmGe2WUH8MGoes7Q$
>


This message may contain information that is confidential or privileged. If you 
are not the intended recipient, please advise the sender immediately and delete 
this message. See 
http://www.blackrock.com/corporate/compliance/email-disclaimers for further 
information.  Please refer to 
http://www.blackrock.com/corporate/compliance/privacy-policy for more 
information about BlackRock’s Privacy Policy.


For a list of BlackRock's office addresses worldwide, see 
http://www.blackrock.com/corporate/about-us/contacts-locations.

© 2022 BlackRock, Inc. All rights reserved.

Re: [DISCUSS] JSON Canonical Extension Type

[Micah Kornfield]

This seems like a reasonable definition to me.  Since there hasn't been
much feedback, I think maybe following through an implementation + this
description in a PR would be the next steps.  If there isn't further
feedback on this, once the PR is up we can have try to vote (which might
bring up some more feedback, but hopefully wouldn't cause too much
implementation churn).

Thanks,
Micah

On Thu, Nov 17, 2022 at 3:58 PM Pradeep Gollakota
 wrote:

> Hi folks!
>
> I put together this specification for canonicalizing the JSON type in
> Arrow.
>
> ## Introduction
> JSON is a widely used text based data interchange format. There are many
> use cases where a user has a column whose contents are a JSON encoded
> string. BigQuery's [JSON Type][1] and Parquet’s [JSON Logical Type][2] are
> two such examples.
>
> The JSON specification is defined in [RFC-8259][3]. However, many of the
> most popular parsers support non standard extensions. Examples of non
> standard extensions to JSON include comments, unquoted keys, trailing
> commas, etc.
>
> ## Extension Specification
> * The name of the extension is `arrow.json`
> * The storage type of the extension is `utf8`
> * The extension type has no parameters
> * The metadata MUST be either empty or a valid JSON object
> - There is no canonical metadata
> - Implementations MAY include implementation-specific metadata by using
> a namespaced key. For example `{"google.bigquery": {"my": "metadata"}}`
> * Implementations...
> - MUST produce valid UTF-8 encoded text
> - SHOULD produce valid standard JSON
> - MAY produce valid non-standard JSON
> - MUST support parsing standard JSON
> - MAY support parsing non standard JSON
> - SHOULD pass through contents that they do not understand
>
> ## Forward compatibility
> In the future we might allow this logical type to annotate a byte storage
> type with a different text encoding.  Implementations consuming JSON
> logical types should verify this.
>
> [1]:
>
> https://cloud.google.com/bigquery/docs/reference/standard-sql/data-types#json_type
> [2]:
> https://github.com/apache/parquet-format/blob/master/LogicalTypes.md#json
> [3]: https://datatracker.ietf.org/doc/html/rfc8259
>

Struct evolution

[Micah Kornfield]

Hi Matt,
I don't think we've discussed try to schema evolution formally to the
spec.  It would likely be something nice to have especially for simple
evolution like adding columns but it is probably a long process and would
need someone to drive it (create an RFC, gaining consensus and making sure
two implementations have implementation).  I can also see the argument that
these decisions belong with individual implementations.

I haven't had a chance to review Weston's doc but I imagine the work on
Datasets once implemented could cover your use case?

Thanks,
Micah

On Monday, November 28, 2022, Matthew Scanlon  wrote:

> Hi Micah,
> I was wondering where the arrow project stands on this issue, as it looks
> like there are not many work arounds to using
> pyarrow.list_(pyarrow.struct()) as many other datatypes that would "fit
> the
> bill" of what a list of structs achieves raises a
> pyarrow.lib.ArrowNotImplementedError when calling table_to_blocks().
>
> On Tue, Nov 8, 2022 at 12:53 PM Micah Kornfield 
> wrote:
>
> > Hi Matthew,
> > Could you give some more specifics about what language/component you are
> > using.  In general, Arrow at a specification level doesn't deal with
> schema
> > evolution.  Is this in regard to Datasets or a different component?
> >
> > Thanks,
> > Micah
> >
> > On Mon, Nov 7, 2022 at 5:06 PM Matthew Scanlon <
> > matthew.scan...@exosfinancial.com> wrote:
> >
> > > Good afternoon, I wanted to reach out and open a dialog about structs,
> > the
> > > evolution of them in schemas, and if support for such a feature is on
> the
> > > road map or a hard pass for the arrow team.
> > >
> > > Currently, it appears structs support removing a field, but will there
> be
> > > support for adding fields later on? Are there any recommended patterns
> > for
> > > supporting such a field. For example, if a field foo is a struct with
> > > sub_fields A, B and then later field C gets added, the old data can not
> > be
> > > loaded using the new schema.
> > >
> > > Thank you.
> > >
> > > Matthew Scanlon
> > >
> > > --
> > >
> > >
> > > Broker-Dealer services offered through Exos Securities LLC, member of
> > > SIPC  / FINRA  /
> > > BrokerCheck
> > > / 2022 Exos, inc.  For important
> > > disclosures, click here
> > > .
> > >
> > >
> > >
> > >
> >
>
> --
>
>
> Broker-Dealer services offered through Exos Securities LLC, member of
> SIPC  / FINRA  /
> BrokerCheck
> / 2022 Exos, inc.  For important
> disclosures, click here
> .
>
>
>
>

Re: [VOTE] Disable ASF Jira issue reporting

[Matthew Topol]

+1

On Fri, Nov 25, 2022 at 10:31 AM Alessandro Molina
 wrote:

> +1 as far as for "now" we actually mean "as soon as the necessary scripts
> have been ported to github"
>
> I mean, I doubt the plan is to disable jira before we can actually ship PRs
> from github issues and thus block development.
>
>
>
> Il Mer 23 Nov 2022, 22:37 Todd Farmer  ha
> scritto:
>
> > Hello,
> >
> > I would like to propose that issue reporting in ASF Jira for the Apache
> > Arrow project be disabled, and all users directed to use GitHub issues
> for
> > reporting going forward. GitHub issue reporting is now enabled [1] in
> > response to a recent Infra policy change eliminating self-service user
> > registration for ASF Jira accounts. The Apache Arrow project has already
> > voted in support of migrating issue tracking from ASF Jira to GitHub
> issues
> > [2], and migration work is ongoing [3].
> >
> > Disabling ASF Jira issue reporting will move all such work to GitHub
> > issues. I expect that usage of this new platform by all participants -
> not
> > just new community members lacking ASF Jira accounts - will expedite
> > further discovery and improvements to this platform. Furthermore, this
> will
> > prevent new users from being routed to a new, and potentially "lesser",
> > issue reporting experience.
> >
> > Please note that this proposal does NOT move work on existing ASF Jira
> > issues to GitHub - that work should continue in Jira until issues are
> > migrated and the Jira system set to read-only. There will be a separate
> > discussion when that activity is ready.
> >
> > The vote will be open for at least 72 hours.
> >
> > [ ] +1 Disable issue reporting on ASF Jira for the Apache Arrow project
> > [ ] -1 Leave issue reporting enabled on ASF Jira for the Apache Arrow
> > project because...
> >
> > [1] https://github.com/apache/arrow/issues/new/choose
> > [2] https://lists.apache.org/thread/l545m95xmf3w47oxwqxvg811or7b93tb
> > [3]
> >
> >
> https://docs.google.com/document/d/1UaSJs-oyuq8QvlUPoQ9GeiwP19LK5ZzF_5-HLfHDCIg/edit?usp=sharing
> >
> > Todd Farmer
> >
>

Re: [EXT] Re: Struct evolution

[Matthew Scanlon]

Hi Micah,
I was wondering where the arrow project stands on this issue, as it looks
like there are not many work arounds to using
pyarrow.list_(pyarrow.struct()) as many other datatypes that would "fit the
bill" of what a list of structs achieves raises a
pyarrow.lib.ArrowNotImplementedError when calling table_to_blocks().

On Tue, Nov 8, 2022 at 12:53 PM Micah Kornfield 
wrote:

> Hi Matthew,
> Could you give some more specifics about what language/component you are
> using.  In general, Arrow at a specification level doesn't deal with schema
> evolution.  Is this in regard to Datasets or a different component?
>
> Thanks,
> Micah
>
> On Mon, Nov 7, 2022 at 5:06 PM Matthew Scanlon <
> matthew.scan...@exosfinancial.com> wrote:
>
> > Good afternoon, I wanted to reach out and open a dialog about structs,
> the
> > evolution of them in schemas, and if support for such a feature is on the
> > road map or a hard pass for the arrow team.
> >
> > Currently, it appears structs support removing a field, but will there be
> > support for adding fields later on? Are there any recommended patterns
> for
> > supporting such a field. For example, if a field foo is a struct with
> > sub_fields A, B and then later field C gets added, the old data can not
> be
> > loaded using the new schema.
> >
> > Thank you.
> >
> > Matthew Scanlon
> >
> > --
> >
> >
> > Broker-Dealer services offered through Exos Securities LLC, member of
> > SIPC  / FINRA  /
> > BrokerCheck
> > / 2022 Exos, inc.  For important
> > disclosures, click here
> > .
> >
> >
> >
> >
>

-- 


Broker-Dealer services offered through Exos Securities LLC, member of 
SIPC  / FINRA  / BrokerCheck  
/ 2022 Exos, inc.  For important 
disclosures, click here 
. 

Re: Arrow sync call November 23 at 12:00 US/Eastern, 17:00 UTC

[Jacob Wujciak]

> The merge script would still be useful to flag issues such as a missing
component label, or to ensure the fix version (milestone) is set.

It would be possible to turn the current checks for these into a PR check
that is obligatory and will block merging until green. [1][2]

[1]:
https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Branchprotection
[2]:
https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule

On Mon, Nov 28, 2022 at 2:40 PM Antoine Pitrou  wrote:

>
> Also a note that discussing this in a thread entitled "Arrow sync call
> November 23" might not raise the attention of all interested parties :-)
>
>
> Le 28/11/2022 à 14:38, Antoine Pitrou a écrit :
> >
> > The merge script would still be useful to flag issues such as a missing
> > component label, or to ensure the fix version (milestone) is set.
> >
> >
> > Le 28/11/2022 à 12:09, Joris Van den Bossche a écrit :
> >> FYI: Raúl also already opened a PR to update the merge script to work
> >> with github issues: https://github.com/apache/arrow/pull/14731
> >>
> >> Personally I also think that we should consider using the merge button
> >> instead of our script (or at least re-evaluate what the script still
> >> does better, or might now we redundant). But so given that the merge
> >> script is almost ready to handle github issues, that is a discussion
> >> we can have separate from the direct action to start using github
> >> issues (it probably needs to wait until the actual JIRA->github
> >> migration of the issues has happened, anyway, since until then the
> >> script is needed to handle the mix of JIRA and github issues)
> >>
> >> Joris
> >>
> >> On Mon, 28 Nov 2022 at 11:44, Andrew Lamb  wrote:
> >>>
>  How do apache/arrow-rs, arrow-datafusion, arrow-julia, et al. handle
> this?
> >>>
> >>> arrow-rs and arrow-datafusion use the squash-and-merge button in the
> github
> >>> UI.
> >>>
> >>> In general we don't have the same level of curation in commit titles
> as the
> >>> main arrow repo. However, I have not heard anyone ask for better commit
> >>> titles and the github UI / API does a good job tying all commits back
> to
> >>> the PR they came from.
> >>>
> >>> Andrew
> >>>
> >>> On Fri, Nov 25, 2022 at 8:39 PM Neal Richardson <
> neal.p.richard...@gmail.com>
> >>> wrote:
> >>>
> > - This creates an immediate need to modify the PR merge script; Raúl
> > opened an issue for this after the call [6]; this also raises the
> > question of whether we still need the PR merge script or whether
> > committers can use the "Squash and merge" button in the GitHub web UI
> > instead
> >
> 
>  I think the only thing the merge script will do better than the UI
> button
>  is that the script always gets the merge commit title correct. IIRC
> in the
>  GitHub UI, if you merge a PR that has only one commit, it uses the
> commit
>  message from that commit and not the PR title. Maybe GitHub has fixed
> this
>  (or let it be configurable).
> 
>  How do apache/arrow-rs, arrow-datafusion, arrow-julia, et al. handle
> this?
> 
>  Neal
> 
>

Re: Arrow sync call November 23 at 12:00 US/Eastern, 17:00 UTC

[Antoine Pitrou]

Also a note that discussing this in a thread entitled "Arrow sync call 
November 23" might not raise the attention of all interested parties :-)



Le 28/11/2022 à 14:38, Antoine Pitrou a écrit :


The merge script would still be useful to flag issues such as a missing
component label, or to ensure the fix version (milestone) is set.


Le 28/11/2022 à 12:09, Joris Van den Bossche a écrit :

FYI: Raúl also already opened a PR to update the merge script to work
with github issues: https://github.com/apache/arrow/pull/14731

Personally I also think that we should consider using the merge button
instead of our script (or at least re-evaluate what the script still
does better, or might now we redundant). But so given that the merge
script is almost ready to handle github issues, that is a discussion
we can have separate from the direct action to start using github
issues (it probably needs to wait until the actual JIRA->github
migration of the issues has happened, anyway, since until then the
script is needed to handle the mix of JIRA and github issues)

Joris

On Mon, 28 Nov 2022 at 11:44, Andrew Lamb  wrote:



How do apache/arrow-rs, arrow-datafusion, arrow-julia, et al. handle this?


arrow-rs and arrow-datafusion use the squash-and-merge button in the github
UI.

In general we don't have the same level of curation in commit titles as the
main arrow repo. However, I have not heard anyone ask for better commit
titles and the github UI / API does a good job tying all commits back to
the PR they came from.

Andrew

On Fri, Nov 25, 2022 at 8:39 PM Neal Richardson 
wrote:


- This creates an immediate need to modify the PR merge script; Raúl
opened an issue for this after the call [6]; this also raises the
question of whether we still need the PR merge script or whether
committers can use the "Squash and merge" button in the GitHub web UI
instead



I think the only thing the merge script will do better than the UI button
is that the script always gets the merge commit title correct. IIRC in the
GitHub UI, if you merge a PR that has only one commit, it uses the commit
message from that commit and not the PR title. Maybe GitHub has fixed this
(or let it be configurable).

How do apache/arrow-rs, arrow-datafusion, arrow-julia, et al. handle this?

Neal

Re: Arrow sync call November 23 at 12:00 US/Eastern, 17:00 UTC

[Antoine Pitrou]

The merge script would still be useful to flag issues such as a missing 
component label, or to ensure the fix version (milestone) is set.



Le 28/11/2022 à 12:09, Joris Van den Bossche a écrit :

FYI: Raúl also already opened a PR to update the merge script to work
with github issues: https://github.com/apache/arrow/pull/14731

Personally I also think that we should consider using the merge button
instead of our script (or at least re-evaluate what the script still
does better, or might now we redundant). But so given that the merge
script is almost ready to handle github issues, that is a discussion
we can have separate from the direct action to start using github
issues (it probably needs to wait until the actual JIRA->github
migration of the issues has happened, anyway, since until then the
script is needed to handle the mix of JIRA and github issues)

Joris

On Mon, 28 Nov 2022 at 11:44, Andrew Lamb  wrote:



How do apache/arrow-rs, arrow-datafusion, arrow-julia, et al. handle this?


arrow-rs and arrow-datafusion use the squash-and-merge button in the github
UI.

In general we don't have the same level of curation in commit titles as the
main arrow repo. However, I have not heard anyone ask for better commit
titles and the github UI / API does a good job tying all commits back to
the PR they came from.

Andrew

On Fri, Nov 25, 2022 at 8:39 PM Neal Richardson 
wrote:


- This creates an immediate need to modify the PR merge script; Raúl
opened an issue for this after the call [6]; this also raises the
question of whether we still need the PR merge script or whether
committers can use the "Squash and merge" button in the GitHub web UI
instead



I think the only thing the merge script will do better than the UI button
is that the script always gets the merge commit title correct. IIRC in the
GitHub UI, if you merge a PR that has only one commit, it uses the commit
message from that commit and not the PR title. Maybe GitHub has fixed this
(or let it be configurable).

How do apache/arrow-rs, arrow-datafusion, arrow-julia, et al. handle this?

Neal

Re: [VOTE][RUST][DataFusion] Release DataFusion Python Bindings 0.7.0 RC2

[Martin Grigorov]

On Mon, Nov 28, 2022 at 11:24 AM Martin Grigorov 
wrote:

> +1 (non-binding)
>
> The build and tests pass successfully on Ubuntu 22.10 x86_64!
>
> "maturin develop" hangs on my openEuler (Linux) 22.03 aarch64 system:
>
> =
> (venv) [mgrigorov@euler-arm-22 apache-arrow-datafusion-python-0.7.0]$
> maturin develop
>  Building a mixed python/rust project
> ^C
> (venv) [mgrigorov@euler-arm-22 apache-arrow-datafusion-python-0.7.0]$
> which maturin
> /tmp/apache-arrow-datafusion-python-0.7.0/venv/bin/maturin
> (venv) [mgrigorov@euler-arm-22 apache-arrow-datafusion-python-0.7.0]$
> maturin --help
> maturin 0.13.1
> Build and publish crates with pyo3, rust-cpython and cffi bindings as well
> as rust binaries as python packages
>
> USAGE:
> maturin 
>
> OPTIONS:
> -h, --help   Print help information
> -V, --versionPrint version information
>
> SUBCOMMANDS:
> build  Build the crate into python packages
> publishBuild and publish the crate as python packages to pypi
> list-pythonSearch and list the available python installations
> developInstall the crate as module in the current virtualenv
> sdist  Build only a source distribution (sdist) without
> compiling
> init   Create a new cargo project in an existing directory
> newCreate a new cargo project
> upload Upload python packages to pypi
> help   Print this message or the help of the given
> subcommand(s)
> (venv) [mgrigorov@euler-arm-22 apache-arrow-datafusion-python-0.7.0]$
> maturin build
>  Building a mixed python/rust project
> ^C
> =
>
> I'll try to find out what is the problem there!
>

Everything works fine with maturin 0.14.2.
https://github.com/apache/arrow-datafusion-python/pull/85


>
> On Sat, Nov 26, 2022 at 7:01 PM Andy Grove  wrote:
>
>> Hi,
>>
>> I would like to propose a release of Apache Arrow DataFusion Python
>> Bindings,
>> version 0.7.0.
>>
>> This release candidate is based on commit:
>> bd1b78b6d444b7ab172c6aec23fa58c842a592d7 [1]
>> The proposed release tarball and signatures are hosted at [2].
>> The changelog is located at [3].
>> The Python wheels are available on testpypi [4].
>>
>> Please download, verify checksums and signatures, run the unit tests, and
>> vote
>> on the release. The vote will be open for at least 72 hours.
>>
>> Only votes from PMC members are binding, but all members of the community
>> are
>> encouraged to test the release and vote with "(non-binding)".
>>
>> [ ] +1 Release this as Apache Arrow DataFusion Python 0.7.0
>> [ ] +0
>> [ ] -1 Do not release this as Apache Arrow DataFusion Python 0.7.0
>> because...
>>
>> Here is my vote:
>>
>> +1
>>
>> [1]:
>>
>> https://github.com/apache/arrow-datafusion-python/tree/bd1b78b6d444b7ab172c6aec23fa58c842a592d7
>> [2]:
>>
>> https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-datafusion-python-0.7.0-rc2
>> [3]:
>>
>> https://github.com/apache/arrow-datafusion-python/blob/bd1b78b6d444b7ab172c6aec23fa58c842a592d7/CHANGELOG.md
>> [4] https://test.pypi.org/project/datafusion/0.7.0/
>>
>

Re: Arrow sync call November 23 at 12:00 US/Eastern, 17:00 UTC

[Weston Pace]

One thing to note is that you need to have something like "closes #123" in
the PR description or a comment in order for GitHub to close the relevant
issue when the PR is merged.  This isn't too much of a burden to check I
think but took a bit of getting used to for me in Substrait where we use
the merge button.

On Mon, Nov 28, 2022, 3:20 AM Joris Van den Bossche <
jorisvandenboss...@gmail.com> wrote:

> On Mon, 28 Nov 2022 at 12:09, Joris Van den Bossche
>  wrote:
> >
> > FYI: Raúl also already opened a PR to update the merge script to work
> > with github issues: https://github.com/apache/arrow/pull/14731
>
> (sorry, that PR is to update the github actions workflow (the bot that
> comments on PRs), not the merge script)
>
> >
> > Personally I also think that we should consider using the merge button
> > instead of our script (or at least re-evaluate what the script still
> > does better, or might now we redundant). But so given that the merge
> > script is almost ready to handle github issues, that is a discussion
> > we can have separate from the direct action to start using github
> > issues (it probably needs to wait until the actual JIRA->github
> > migration of the issues has happened, anyway, since until then the
> > script is needed to handle the mix of JIRA and github issues)
> >
> > Joris
> >
> > On Mon, 28 Nov 2022 at 11:44, Andrew Lamb  wrote:
> > >
> > > > How do apache/arrow-rs, arrow-datafusion, arrow-julia, et al. handle
> this?
> > >
> > > arrow-rs and arrow-datafusion use the squash-and-merge button in the
> github
> > > UI.
> > >
> > > In general we don't have the same level of curation in commit titles
> as the
> > > main arrow repo. However, I have not heard anyone ask for better commit
> > > titles and the github UI / API does a good job tying all commits back
> to
> > > the PR they came from.
> > >
> > > Andrew
> > >
> > > On Fri, Nov 25, 2022 at 8:39 PM Neal Richardson <
> neal.p.richard...@gmail.com>
> > > wrote:
> > >
> > > > > - This creates an immediate need to modify the PR merge script;
> Raúl
> > > > > opened an issue for this after the call [6]; this also raises the
> > > > > question of whether we still need the PR merge script or whether
> > > > > committers can use the "Squash and merge" button in the GitHub web
> UI
> > > > > instead
> > > > >
> > > >
> > > > I think the only thing the merge script will do better than the UI
> button
> > > > is that the script always gets the merge commit title correct. IIRC
> in the
> > > > GitHub UI, if you merge a PR that has only one commit, it uses the
> commit
> > > > message from that commit and not the PR title. Maybe GitHub has
> fixed this
> > > > (or let it be configurable).
> > > >
> > > > How do apache/arrow-rs, arrow-datafusion, arrow-julia, et al. handle
> this?
> > > >
> > > > Neal
> > > >
>

Re: [VOTE][RUST] Release Apache Arrow Rust 28.0.0 RC1

[Raphael Taylor-Davies]

+1 (binding)

On 25/11/2022 19:42, Andrew Lamb wrote:

To: dev@arrow.apache.org
Subject: [VOTE][RUST] Release Apache Arrow Rust 28.0.0 RC1

Hi,

I would like to propose a release of Apache Arrow Rust Implementation,
version 28.0.0.

This release candidate is based on commit:
eb91dac6e99b0bcbcbd8057b03233059089bbf27 [1]

The proposed release tarball and signatures are hosted at [2].

The changelog is located at [3].

Please download, verify checksums and signatures, run the unit tests,
and vote on the release. There is a script [4] that automates some of
the verification.

The vote will be open for at least 72 hours.

[ ] +1 Release this as Apache Arrow Rust
[ ] +0
[ ] -1 Do not release this as Apache Arrow Rust  because...

[1]:
https://github.com/apache/arrow-rs/tree/eb91dac6e99b0bcbcbd8057b03233059089bbf27
[2]: https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-rs-28.0.0-rc1
[3]:
https://github.com/apache/arrow-rs/blob/eb91dac6e99b0bcbcbd8057b03233059089bbf27/CHANGELOG.md
[4]:
https://github.com/apache/arrow-rs/blob/master/dev/release/verify-release-candidate.sh

Re: Arrow sync call November 23 at 12:00 US/Eastern, 17:00 UTC

[Joris Van den Bossche]

On Mon, 28 Nov 2022 at 12:09, Joris Van den Bossche
 wrote:
>
> FYI: Raúl also already opened a PR to update the merge script to work
> with github issues: https://github.com/apache/arrow/pull/14731

(sorry, that PR is to update the github actions workflow (the bot that
comments on PRs), not the merge script)

>
> Personally I also think that we should consider using the merge button
> instead of our script (or at least re-evaluate what the script still
> does better, or might now we redundant). But so given that the merge
> script is almost ready to handle github issues, that is a discussion
> we can have separate from the direct action to start using github
> issues (it probably needs to wait until the actual JIRA->github
> migration of the issues has happened, anyway, since until then the
> script is needed to handle the mix of JIRA and github issues)
>
> Joris
>
> On Mon, 28 Nov 2022 at 11:44, Andrew Lamb  wrote:
> >
> > > How do apache/arrow-rs, arrow-datafusion, arrow-julia, et al. handle this?
> >
> > arrow-rs and arrow-datafusion use the squash-and-merge button in the github
> > UI.
> >
> > In general we don't have the same level of curation in commit titles as the
> > main arrow repo. However, I have not heard anyone ask for better commit
> > titles and the github UI / API does a good job tying all commits back to
> > the PR they came from.
> >
> > Andrew
> >
> > On Fri, Nov 25, 2022 at 8:39 PM Neal Richardson 
> > 
> > wrote:
> >
> > > > - This creates an immediate need to modify the PR merge script; Raúl
> > > > opened an issue for this after the call [6]; this also raises the
> > > > question of whether we still need the PR merge script or whether
> > > > committers can use the "Squash and merge" button in the GitHub web UI
> > > > instead
> > > >
> > >
> > > I think the only thing the merge script will do better than the UI button
> > > is that the script always gets the merge commit title correct. IIRC in the
> > > GitHub UI, if you merge a PR that has only one commit, it uses the commit
> > > message from that commit and not the PR title. Maybe GitHub has fixed this
> > > (or let it be configurable).
> > >
> > > How do apache/arrow-rs, arrow-datafusion, arrow-julia, et al. handle this?
> > >
> > > Neal
> > >

Re: Arrow sync call November 23 at 12:00 US/Eastern, 17:00 UTC

[Joris Van den Bossche]

FYI: Raúl also already opened a PR to update the merge script to work
with github issues: https://github.com/apache/arrow/pull/14731

Personally I also think that we should consider using the merge button
instead of our script (or at least re-evaluate what the script still
does better, or might now we redundant). But so given that the merge
script is almost ready to handle github issues, that is a discussion
we can have separate from the direct action to start using github
issues (it probably needs to wait until the actual JIRA->github
migration of the issues has happened, anyway, since until then the
script is needed to handle the mix of JIRA and github issues)

Joris

On Mon, 28 Nov 2022 at 11:44, Andrew Lamb  wrote:
>
> > How do apache/arrow-rs, arrow-datafusion, arrow-julia, et al. handle this?
>
> arrow-rs and arrow-datafusion use the squash-and-merge button in the github
> UI.
>
> In general we don't have the same level of curation in commit titles as the
> main arrow repo. However, I have not heard anyone ask for better commit
> titles and the github UI / API does a good job tying all commits back to
> the PR they came from.
>
> Andrew
>
> On Fri, Nov 25, 2022 at 8:39 PM Neal Richardson 
> wrote:
>
> > > - This creates an immediate need to modify the PR merge script; Raúl
> > > opened an issue for this after the call [6]; this also raises the
> > > question of whether we still need the PR merge script or whether
> > > committers can use the "Squash and merge" button in the GitHub web UI
> > > instead
> > >
> >
> > I think the only thing the merge script will do better than the UI button
> > is that the script always gets the merge commit title correct. IIRC in the
> > GitHub UI, if you merge a PR that has only one commit, it uses the commit
> > message from that commit and not the PR title. Maybe GitHub has fixed this
> > (or let it be configurable).
> >
> > How do apache/arrow-rs, arrow-datafusion, arrow-julia, et al. handle this?
> >
> > Neal
> >

Re: [VOTE][RUST][DataFusion] Release DataFusion Python Bindings 0.7.0 RC2

[Andrew Lamb]

+1

On Mon, Nov 28, 2022 at 5:49 AM Andrew Lamb  wrote:

> I verified the signatures and tried installing the dev wheel on mac OS
> x86_64 and running some examples
>
> It worked great!
>
> Thanks for doing this Andy
>
> pip install -i https://test.pypi.org/simple/ datafusion==0.7.0
>
> ...
>
> Python 3.10.8 (main, Nov 15 2022, 05:25:54) [Clang 14.0.0
> (clang-1400.0.29.202)] on darwin
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import datafusion
> >>> from datafusion import col
> >>> import pyarrow
> >>>
> >>> # create a context
> >>> ctx = datafusion.SessionContext()
> >>> df = ctx.read_parquet('/Users/alamb/Downloads/cpu.parquet')
> >>> df.limit(10).show()
>
> +---+---+-+-+--+-+--+---++---+-++---+
> | cpu   | host  | time|
> usage_guest | usage_guest_nice | usage_idle  | usage_iowait |
> usage_irq | usage_nice | usage_softirq | usage_steal | usage_system   |
> usage_user|
>
> +---+---+-+-+--+-+--+---++---+-++---+
> | cpu-total | MacBook-Pro-8.hsd1.ma.comcast.net | 2022-09-30T12:45:50 | 0
>   | 0| 88.22131916285875   | 0| 0
>   | 0  | 0 | 0   | 7.92122538297707   |
> 3.857455454801022 |
> | cpu-total | MacBook-Pro-8.hsd1.ma.comcast.net | 2022-09-30T12:46:00 | 0
>   | 0| 32.20033554948997   | 0| 0
>   | 0  | 0 | 0   | 16.199589883629166 |
> 51.60007456610322 |
> | cpu-total | MacBook-Pro-8.hsd1.ma.comcast.net | 2022-09-30T12:46:10 | 0
>   | 0| 0.20071504695935447 | 0| 0
>   | 0  | 0 | 0   | 14.614564385643801 |
> 85.18472056714127 |
> | cpu-total | MacBook-Pro-8.hsd1.ma.comcast.net | 2022-09-30T12:46:20 | 0
>   | 0| 0.2313367513523604  | 0| 0
>   | 0  | 0 | 0   | 13.967737901756506 |
> 85.80092534727326 |
> | cpu-total | MacBook-Pro-8.hsd1.ma.comcast.net | 2022-09-30T12:46:30 | 0
>   | 0| 0.8125507843064688  | 0| 0
>   | 0  | 0 | 0   | 9.569348084258632  |
> 89.61810113119842 |
> | cpu-total | MacBook-Pro-8.hsd1.ma.comcast.net | 2022-09-30T12:46:40 | 0
>   | 0| 0.700087511006769   | 0| 0
>   | 0  | 0 | 0   | 9.744968120985714  |
> 89.55494436780741 |
> | cpu-total | MacBook-Pro-8.hsd1.ma.comcast.net | 2022-09-30T12:46:50 | 0
>   | 0| 3.7204128301494865  | 0| 0
>   | 0  | 0 | 0   | 19.522897225075514 |
> 76.75668994472105 |
> | cpu-total | MacBook-Pro-8.hsd1.ma.comcast.net | 2022-09-30T12:47:00 | 0
>   | 0| 0.19592971785649965 | 0| 0
>   | 0  | 0 | 0   | 18.986221716745344 |
> 80.8178485658948  |
> | cpu-total | MacBook-Pro-8.hsd1.ma.comcast.net | 2022-09-30T12:47:10 | 0
>   | 0| 2.2297170696832063  | 0| 0
>   | 0  | 0 | 0   | 13.821747548435754 |
> 83.94853538128119 |
> | cpu-total | MacBook-Pro-8.hsd1.ma.comcast.net | 2022-09-30T12:47:20 | 0
>   | 0| 1.5260491584825744  | 0| 0
>   | 0  | 0 | 0   | 11.851898180099917 |
> 86.62205266189078 |
>
> +---+---+-+-+--+-+--+---++---+-++---+
>
> On Mon, Nov 28, 2022 at 4:25 AM Martin Grigorov 
> wrote:
>
>> +1 (non-binding)
>>
>> The build and tests pass successfully on Ubuntu 22.10 x86_64!
>>
>> "maturin develop" hangs on my openEuler (Linux) 22.03 aarch64 system:
>>
>> =
>> (venv) [mgrigorov@euler-arm-22 apache-arrow-datafusion-python-0.7.0]$
>> maturin develop
>>  Building a mixed python/rust project
>> ^C
>> (venv) [mgrigorov@euler-arm-22 apache-arrow-datafusion-python-0.7.0]$
>> which
>> maturin
>> /tmp/apache-arrow-datafusion-python-0.7.0/venv/bin/maturin
>> (venv) [mgrigorov@euler-arm-22 apache-arrow-datafusion-python-0.7.0]$
>> maturin --help
>> maturin 0.13.1
>> Build and publish crates with pyo3, rust-cpython and cffi bindings as well
>> as rust binaries as python packages
>>
>> USAGE:
>> maturin 
>>
>> OPTIONS:
>> -h, --help   Print help information
>> -V, --versionPrint version 

Re: [VOTE][RUST][DataFusion] Release DataFusion Python Bindings 0.7.0 RC2

[Andrew Lamb]

I verified the signatures and tried installing the dev wheel on mac OS
x86_64 and running some examples

It worked great!

Thanks for doing this Andy

pip install -i https://test.pypi.org/simple/ datafusion==0.7.0

...

Python 3.10.8 (main, Nov 15 2022, 05:25:54) [Clang 14.0.0
(clang-1400.0.29.202)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import datafusion
>>> from datafusion import col
>>> import pyarrow
>>>
>>> # create a context
>>> ctx = datafusion.SessionContext()
>>> df = ctx.read_parquet('/Users/alamb/Downloads/cpu.parquet')
>>> df.limit(10).show()
+---+---+-+-+--+-+--+---++---+-++---+
| cpu   | host  | time|
usage_guest | usage_guest_nice | usage_idle  | usage_iowait |
usage_irq | usage_nice | usage_softirq | usage_steal | usage_system   |
usage_user|
+---+---+-+-+--+-+--+---++---+-++---+
| cpu-total | MacBook-Pro-8.hsd1.ma.comcast.net | 2022-09-30T12:45:50 | 0
| 0| 88.22131916285875   | 0| 0
| 0  | 0 | 0   | 7.92122538297707   |
3.857455454801022 |
| cpu-total | MacBook-Pro-8.hsd1.ma.comcast.net | 2022-09-30T12:46:00 | 0
| 0| 32.20033554948997   | 0| 0
| 0  | 0 | 0   | 16.199589883629166 |
51.60007456610322 |
| cpu-total | MacBook-Pro-8.hsd1.ma.comcast.net | 2022-09-30T12:46:10 | 0
| 0| 0.20071504695935447 | 0| 0
| 0  | 0 | 0   | 14.614564385643801 |
85.18472056714127 |
| cpu-total | MacBook-Pro-8.hsd1.ma.comcast.net | 2022-09-30T12:46:20 | 0
| 0| 0.2313367513523604  | 0| 0
| 0  | 0 | 0   | 13.967737901756506 |
85.80092534727326 |
| cpu-total | MacBook-Pro-8.hsd1.ma.comcast.net | 2022-09-30T12:46:30 | 0
| 0| 0.8125507843064688  | 0| 0
| 0  | 0 | 0   | 9.569348084258632  |
89.61810113119842 |
| cpu-total | MacBook-Pro-8.hsd1.ma.comcast.net | 2022-09-30T12:46:40 | 0
| 0| 0.700087511006769   | 0| 0
| 0  | 0 | 0   | 9.744968120985714  |
89.55494436780741 |
| cpu-total | MacBook-Pro-8.hsd1.ma.comcast.net | 2022-09-30T12:46:50 | 0
| 0| 3.7204128301494865  | 0| 0
| 0  | 0 | 0   | 19.522897225075514 |
76.75668994472105 |
| cpu-total | MacBook-Pro-8.hsd1.ma.comcast.net | 2022-09-30T12:47:00 | 0
| 0| 0.19592971785649965 | 0| 0
| 0  | 0 | 0   | 18.986221716745344 |
80.8178485658948  |
| cpu-total | MacBook-Pro-8.hsd1.ma.comcast.net | 2022-09-30T12:47:10 | 0
| 0| 2.2297170696832063  | 0| 0
| 0  | 0 | 0   | 13.821747548435754 |
83.94853538128119 |
| cpu-total | MacBook-Pro-8.hsd1.ma.comcast.net | 2022-09-30T12:47:20 | 0
| 0| 1.5260491584825744  | 0| 0
| 0  | 0 | 0   | 11.851898180099917 |
86.62205266189078 |
+---+---+-+-+--+-+--+---++---+-++---+

On Mon, Nov 28, 2022 at 4:25 AM Martin Grigorov 
wrote:

> +1 (non-binding)
>
> The build and tests pass successfully on Ubuntu 22.10 x86_64!
>
> "maturin develop" hangs on my openEuler (Linux) 22.03 aarch64 system:
>
> =
> (venv) [mgrigorov@euler-arm-22 apache-arrow-datafusion-python-0.7.0]$
> maturin develop
>  Building a mixed python/rust project
> ^C
> (venv) [mgrigorov@euler-arm-22 apache-arrow-datafusion-python-0.7.0]$
> which
> maturin
> /tmp/apache-arrow-datafusion-python-0.7.0/venv/bin/maturin
> (venv) [mgrigorov@euler-arm-22 apache-arrow-datafusion-python-0.7.0]$
> maturin --help
> maturin 0.13.1
> Build and publish crates with pyo3, rust-cpython and cffi bindings as well
> as rust binaries as python packages
>
> USAGE:
> maturin 
>
> OPTIONS:
> -h, --help   Print help information
> -V, --versionPrint version information
>
> SUBCOMMANDS:
> build  Build the crate into python packages
> publishBuild and publish the crate as python packages to pypi
> list-pythonSearch and list the available python installations
> developInstall the crate 

Re: Arrow sync call November 23 at 12:00 US/Eastern, 17:00 UTC

[Andrew Lamb]

> How do apache/arrow-rs, arrow-datafusion, arrow-julia, et al. handle this?

arrow-rs and arrow-datafusion use the squash-and-merge button in the github
UI.

In general we don't have the same level of curation in commit titles as the
main arrow repo. However, I have not heard anyone ask for better commit
titles and the github UI / API does a good job tying all commits back to
the PR they came from.

Andrew

On Fri, Nov 25, 2022 at 8:39 PM Neal Richardson 
wrote:

> > - This creates an immediate need to modify the PR merge script; Raúl
> > opened an issue for this after the call [6]; this also raises the
> > question of whether we still need the PR merge script or whether
> > committers can use the "Squash and merge" button in the GitHub web UI
> > instead
> >
>
> I think the only thing the merge script will do better than the UI button
> is that the script always gets the merge commit title correct. IIRC in the
> GitHub UI, if you merge a PR that has only one commit, it uses the commit
> message from that commit and not the PR title. Maybe GitHub has fixed this
> (or let it be configurable).
>
> How do apache/arrow-rs, arrow-datafusion, arrow-julia, et al. handle this?
>
> Neal
>

Re: [VOTE][RUST][DataFusion] Release DataFusion Python Bindings 0.7.0 RC2

[Martin Grigorov]

+1 (non-binding)

The build and tests pass successfully on Ubuntu 22.10 x86_64!

"maturin develop" hangs on my openEuler (Linux) 22.03 aarch64 system:

=
(venv) [mgrigorov@euler-arm-22 apache-arrow-datafusion-python-0.7.0]$
maturin develop
 Building a mixed python/rust project
^C
(venv) [mgrigorov@euler-arm-22 apache-arrow-datafusion-python-0.7.0]$ which
maturin
/tmp/apache-arrow-datafusion-python-0.7.0/venv/bin/maturin
(venv) [mgrigorov@euler-arm-22 apache-arrow-datafusion-python-0.7.0]$
maturin --help
maturin 0.13.1
Build and publish crates with pyo3, rust-cpython and cffi bindings as well
as rust binaries as python packages

USAGE:
maturin 

OPTIONS:
-h, --help   Print help information
-V, --versionPrint version information

SUBCOMMANDS:
build  Build the crate into python packages
publishBuild and publish the crate as python packages to pypi
list-pythonSearch and list the available python installations
developInstall the crate as module in the current virtualenv
sdist  Build only a source distribution (sdist) without
compiling
init   Create a new cargo project in an existing directory
newCreate a new cargo project
upload Upload python packages to pypi
help   Print this message or the help of the given subcommand(s)
(venv) [mgrigorov@euler-arm-22 apache-arrow-datafusion-python-0.7.0]$
maturin build
 Building a mixed python/rust project
^C
=

I'll try to find out what is the problem there!

On Sat, Nov 26, 2022 at 7:01 PM Andy Grove  wrote:

> Hi,
>
> I would like to propose a release of Apache Arrow DataFusion Python
> Bindings,
> version 0.7.0.
>
> This release candidate is based on commit:
> bd1b78b6d444b7ab172c6aec23fa58c842a592d7 [1]
> The proposed release tarball and signatures are hosted at [2].
> The changelog is located at [3].
> The Python wheels are available on testpypi [4].
>
> Please download, verify checksums and signatures, run the unit tests, and
> vote
> on the release. The vote will be open for at least 72 hours.
>
> Only votes from PMC members are binding, but all members of the community
> are
> encouraged to test the release and vote with "(non-binding)".
>
> [ ] +1 Release this as Apache Arrow DataFusion Python 0.7.0
> [ ] +0
> [ ] -1 Do not release this as Apache Arrow DataFusion Python 0.7.0
> because...
>
> Here is my vote:
>
> +1
>
> [1]:
>
> https://github.com/apache/arrow-datafusion-python/tree/bd1b78b6d444b7ab172c6aec23fa58c842a592d7
> [2]:
>
> https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-datafusion-python-0.7.0-rc2
> [3]:
>
> https://github.com/apache/arrow-datafusion-python/blob/bd1b78b6d444b7ab172c6aec23fa58c842a592d7/CHANGELOG.md
> [4] https://test.pypi.org/project/datafusion/0.7.0/
>

[ANNOUNCE] Apache Arrow 10.0.1 released

[Sutou Kouhei]

The Apache Arrow community is pleased to announce the 10.0.1 release.
The release includes 30 resolved issues ([1]) since the 10.0.0 release.

The release is available now from our website, [2] and [3]:
https://arrow.apache.org/install/

Release notes are available at:
https://arrow.apache.org/release/10.0.1.html

What is Apache Arrow?
-

Apache Arrow is a columnar in-memory analytics layer designed to accelerate big
data. It houses a set of canonical in-memory representations of flat and
hierarchical data along with multiple language-bindings for structure
manipulation. It also provides low-overhead streaming and batch messaging,
zero-copy interprocess communication (IPC), and vectorized in-memory analytics
libraries.
Languages currently supported include C, C++, C#, Go, Java, JavaScript, Julia,
MATLAB, Python, R, Ruby, and Rust.

Please report any feedback to the mailing lists ([4], [5])

Regards,
The Apache Arrow community


[1]: 
https://issues.apache.org/jira/issues/?jql=project+%3D+ARROW+AND+fixVersion+%3D+10.0.1
[2]: https://www.apache.org/dyn/closer.cgi/arrow/arrow-10.0.1/
[3]: https://apache.jfrog.io/artifactory/arrow/
[4]: https://lists.apache.org/list.html?u...@arrow.apache.org
[5]: https://lists.apache.org/list.html?dev@arrow.apache.org

[ANNOUNCE] Apache Arrow 10.0.0 released

[Sutou Kouhei]

The Apache Arrow community is pleased to announce the 10.0.0 release.
The release includes 536 resolved issues ([1]) since the 9.0.0 release.

The release is available now from our website, [2] and [3]:
https://arrow.apache.org/install/

Release notes are available at:
https://arrow.apache.org/release/10.0.0.html

What is Apache Arrow?
-

Apache Arrow is a columnar in-memory analytics layer designed to accelerate big
data. It houses a set of canonical in-memory representations of flat and
hierarchical data along with multiple language-bindings for structure
manipulation. It also provides low-overhead streaming and batch messaging,
zero-copy interprocess communication (IPC), and vectorized in-memory analytics
libraries.
Languages currently supported include C, C++, C#, Go, Java, JavaScript, Julia,
MATLAB, Python, R, Ruby, and Rust.

Please report any feedback to the mailing lists ([4], [5])

Regards,
The Apache Arrow community


[1]: 
https://issues.apache.org/jira/issues/?jql=project+%3D+ARROW+AND+fixVersion+%3D+10.0.0
[2]: https://www.apache.org/dyn/closer.cgi/arrow/arrow-10.0.0/
[3]: https://apache.jfrog.io/artifactory/arrow/
[4]: https://lists.apache.org/list.html?u...@arrow.apache.org
[5]: https://lists.apache.org/list.html?dev@arrow.apache.org