Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Java build instructions to mention Arrow S3 and Docker #8867

Merged
merged 1 commit into from
Jul 27, 2021

Conversation

jlowe
Copy link
Member

@jlowe jlowe commented Jul 27, 2021

Updates the Java build instructions to mention the CUDF_ENABLE_ARROW_S3=OFF setting when statically linking Arrow. The README now also points to the Java CI Docker environment and build script for building a Java jar that can run on any modern Linux system.

@jlowe jlowe added doc Documentation Java Affects Java cuDF API. improvement Improvement / enhancement to an existing function non-breaking Non-breaking change labels Jul 27, 2021
@jlowe jlowe self-assigned this Jul 27, 2021
@jlowe jlowe requested a review from a team as a code owner July 27, 2021 19:35
@jlowe jlowe added Java Affects Java cuDF API. and removed Java Affects Java cuDF API. improvement Improvement / enhancement to an existing function labels Jul 27, 2021
@jlowe
Copy link
Member Author

jlowe commented Jul 27, 2021

@gpucibot merge

@rapids-bot rapids-bot bot merged commit 279f9a4 into rapidsai:branch-21.10 Jul 27, 2021
@jlowe jlowe deleted the update-java-build-docs branch September 10, 2021 15:47
@bdice bdice mentioned this pull request Aug 4, 2022
3 tasks
rapids-bot bot pushed a commit that referenced this pull request Aug 8, 2022
This PR is a breaking change that disables Arrow S3 support by default. Enabling this feature by default has caused build issues for many downstream consumers, all of whom (to my knowledge) manually disable support for this feature. Most commonly, that build error appears as `fatal error: aws/core/Aws.h: No such file or directory`. In my understanding, several downstream consumers of cudf no longer rely on Arrow S3 support from this library and instead get S3 access via fsspec. I am not aware of any users of libcudf who rely on this being enabled by default (or enabled at all).

See related issues and discussions: #8617, #11333, #8867, #10644 (comment), NVIDIA/spark-rapids#2827. Build errors caused by this default behavior have also been reported internally.

cc: @rjzamora @beckernick @jdye64 @randerzander @robertmaynard @jlowe @quasiben if you have comments following our previous discussion.

Authors:
  - Bradley Dice (https://github.com/bdice)

Approvers:
  - Nghia Truong (https://github.com/ttnghia)
  - GALI PREM SAGAR (https://github.com/galipremsagar)
  - Vyas Ramasubramani (https://github.com/vyasr)
  - AJ Schmidt (https://github.com/ajschmidt8)

URL: #11470
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc Documentation Java Affects Java cuDF API. non-breaking Non-breaking change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants