arrow-cpp v10.0.1

[regro-cf-autotick-bot]

It is very likely that the current package version for this feedstock is out of date.

Checklist before merging this PR:

• Dependencies have been updated if changed: see upstream
• Tests have passed
• Updated license if changed and license_file is packaged

Closes #158
Closes #862
Closes #867
Closes #866
Closes #880
Closes #890
Closes #894

Information about this PR:

1. Feel free to push to the bot's branch to update this PR if needed.
2. The bot will almost always only open one PR per version.
3. The bot will stop issuing PRs if more than 3 version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.
4. If you want these PRs to be merged automatically, make an issue with @conda-forge-admin,please add bot automerge in the title and merge the resulting PR. This command will add our bot automerge feature to your feedstock.
5. If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

Pending Dependency Version Updates

Here is a list of all the pending dependency version updates for this repo. Please double check all dependencies before merging.

Name	Upstream Version	Current Version
arrow-cpp	10.0.0

Dependency Analysis

We couldn't run dependency analysis due to an internal error in the bot. :/ Help is very welcome!

_{This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/autotick-bot/actions/runs/3327188129, please use this URL for debugging.}

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[jakirkham]

Please see PR ( #866 )

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I was trying to look for recipes to lint for you, but it appears we have a merge conflict.
Please try to merge or rebase with the base branch to resolve this conflict.

Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.

[xhochy]

@h-vetinari You can also mark PRs as draft to stop the bot from reopening them.

[h-vetinari]

@h-vetinari You can also mark PRs as draft to stop the bot from reopening them.

Cool, didn't know that!

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[h-vetinari]

So, this PR is doing a couple of things:

• version bump
• sync with upstream recipe
• unpin aws-sdk-cpp (see discussion here)
• build for openssl 3
• remove python as a host-dep from arrow-cpp 🥳
  • this causes the bot to collapse the python-jobs into one per aarch -> no more insane build matrix sizes 🚀
  • needs a little massaging to make sure we split jobs by openssl version
• figure out the following on windows (upstream issue):

  import: 'pyarrow.parquet'
  [FATAL] 2022-11-08 00:12:43.210 WinHttpSyncHttpClient [2936] Failed setting secure crypto protocols with error code: 87
  

  update: seems to not be critical
• re-enable CUDA builds on aarch/ppc; this needs cross-compilation support, more discussion on the why here
• follow through on the ancient arrow-cpp -> libarrow rename plans, where @xhochy said (cf. above):

  I would delay the renaming until we can split libarrow and libarrow_python into separate outputs. This will then probably still be a build with a full Python matrix but at least the libarrow output would then be Python independent.

While we figure out these issues (help appreciated!), this is a draft.

[h-vetinari]

@xhochy @pitrou @kou
Do we actually still need numpy (for the C-API?) to build arrow-cpp?

I'm getting

WARNING (libarrow): run-exports library package conda-forge::numpy-1.20.3-py39h139494b_2 in requirements/run but it is not used (i.e. it is overdepending or perhaps statically linked? If that is what you want then add it to `build/ignore_run_exports`)

on all platforms...

Also, has someone seen the following error before (which happens on windows, but doesn't fail the test section apparently):

import: 'pyarrow'
import: 'pyarrow.dataset'
import: 'pyarrow.flight'
import: 'pyarrow.gandiva'
import: 'pyarrow.parquet'
[FATAL] 2022-11-07 07:27:02.824 WinHttpSyncHttpClient [4232] Failed setting secure crypto protocols with error code: 87
import: 'pyarrow.fs'
import: 'pyarrow._s3fs'

PS. Link to previous CI run (since I'm about to force-push)

[xhochy]

Do we actually still need numpy (for the C-API?) to build arrow-cpp?

I would have to look into the source but as long as there is no Python dependency, there should also be no NumPy dependency.

Due to the nature of NumPy's linking mechanism (which is really great!), you should never see an actual linkage against it. If the warning isn't always showing up, I would be very curious why it happens. All references are filled at runtime through the C function import_numpy().

[h-vetinari]

Just hoping there is a way here, versus loosing out on PyArrow and Conda/Conda-forge. !

It's technically possible. Assuming the CI passes it would not add an extreme maintenance burden, though it depends also whether the other maintainers agree (w.r.t. precedent etc.). But this will be a topic for a separate PR.

In any case (and without knowing your constraints obviously), python upgrades have become much less painless, and it should be part of regular dependency hygiene; it's getting high time to move away from 3.7, where the dependency landscape is bitrotting with each passing week (and it's easier to move incrementally than to do 3.7->3.11).

[rxm7706]

Just hoping there is a way here, versus loosing out on PyArrow and Conda/Conda-forge. !

It's technically possible. Assuming the CI passes it would not add an extreme maintenance burden, though it depends also whether the other maintainers agree (w.r.t. precedent etc.). But this will be a topic for a separate PR.

Thank you for explaining @h-vetinari , understand the overhead and potential path available. I will raise as a separate PR. Yes, would have loved to not be in the situation we are, still reliant on Python 3.7, monolith systems and Vendor/3rd Party system dependencies. Appreciate your time and direction.

[h-vetinari]

I will raise as a separate PR.

Please do this only after this PR is merged and if you know (at least roughly) how to insert this into conda_build_config.yaml. otherwise I'm planning to open that PR after this one is merged :)

[h-vetinari]

@conda-forge/arrow-cpp
Barring further comments, I'm planning to merge this on the weekend. :)