Update/relax the hard pin of aws-sdk-cpp

[phoebusm]

Comment:

Hi team!

aws-sdk-cpp on conda forge has published v1.11.833. I have tried to update the lib on my project but failed because of the hard pin of aws-sdk-cpp on libarrow:

└─ libarrow [20.0.0|21.0.0|22.0.0|23.0.1|24.0.0] would require
            └─ aws-sdk-cpp >=1.11.747,<1.11.748.0a0 *, which conflicts with any installable versions previously reported.

Is it any chance to update the pin soon? Or would it be feasible to publish a variant of libarrow built without S3 support (ARROW_S3)? This would remove the aws-sdk-cpp runtime dependency entirely for users who do not need S3 filesystem access through Arrow directly.

Thank you very much

[h-vetinari]

Libarrow needs to be rebuilt for the new aws version; c.f.

• ENH: update package version to 1.11.833 aws-sdk-cpp-feedstock#1007
• Update pin for aws_sdk_cpp conda-forge-pinning-feedstock#8649
• relock w/ conda-lock conda-forge-bot#6266
• first bot-make-migrators run after pinning update in bot

The migrator will be created shortly, and then PRs will be opened here a little later. All this happened in the last few hours; please be patient.

Or would it be feasible to publish a variant of libarrow built without S3 support (ARROW_S3)?

This needs upstream work first, though it looks like it may actually be happening in the near future:

• [C++] Allow filesystems to be implemented in separate library (+ move remote filesystems out of libarrow into their own shared libraries) apache/arrow#49399
• [C++] Move S3 to its own shared library apache/arrow#50194
• GH-50194: [C++] Move S3 and AWS-SDK to its own libarrow_s3.so apache/arrow#50195