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 rapids jni and private dependency version to 24.02.1 #10511

Merged
merged 1 commit into from
Feb 29, 2024

Conversation

NvTimLiu
Copy link
Collaborator

Update spark-rapids-private and spark-rapids-jni dependencies to 24.02.1,

Because cuDF native has a new release v24.02.02 to fix buts.

Our v24.02.0 which depends on old cuDF native release have already been released to maven central.

We must update them to v24.02.1 to catch cuDF native bugs fixing in v24.02.02 release

@NvTimLiu NvTimLiu added the build Related to CI / CD or cleanly building label Feb 28, 2024
@NvTimLiu NvTimLiu self-assigned this Feb 28, 2024
@NvTimLiu NvTimLiu changed the base branch from branch-24.04 to branch-24.02 February 28, 2024 15:34
@NvTimLiu NvTimLiu marked this pull request as draft February 28, 2024 15:35
@NvTimLiu
Copy link
Collaborator Author

Draft this change until v24.02.1 both spark-rapids-private and spark-rapids-jni release jars are available to maven central

@NvTimLiu
Copy link
Collaborator Author

build

@NvTimLiu NvTimLiu marked this pull request as ready for review February 29, 2024 13:01
@NvTimLiu
Copy link
Collaborator Author

Close and reopen to trigger mvn[compile,RAT,scalastyle,docgen] check due to the missed pull-request:open action

@NvTimLiu NvTimLiu closed this Feb 29, 2024
@NvTimLiu NvTimLiu reopened this Feb 29, 2024
@NvTimLiu NvTimLiu merged commit e1c2f77 into NVIDIA:branch-24.02 Feb 29, 2024
41 of 42 checks passed
NvTimLiu added a commit that referenced this pull request Mar 2, 2024
* Update rapids jni and private dependency version to 24.02.1 (#10511)

Signed-off-by: Tim Liu <[email protected]>

* Add missed shims for scala2.13 (#10465)

* Add missed shims for scala2.13

Signed-off-by: Tim Liu <[email protected]>

* Add 351 snapshot shim for the scala2.13 version of plugin jar

Signed-off-by: Tim Liu <[email protected]>

* Remove 351 snapshot shim as spark 3.5.1 has been released

Signed-off-by: Tim Liu <[email protected]>

* Remove scala2.13 351 snapshot shim

Signed-off-by: Tim Liu <[email protected]>

* Remove 351 shim's jason string

Ran `mvn generate-sources -Dshimplify=true -Dshimplify.move=true -Dshimplify.remove.shim=351`

to remove 351 shim's jason string, and fix some unnecessary empty lines that were introduced

Signed-off-by: Tim Liu <[email protected]>

* Update Copyright 2024

Auto copyright by below scripts
```
export SPARK_RAPIDS_AUTO_COPYRIGHTER=ON

./scripts/auto-copyrighter.sh $(git diff --name-only origin/branch-24.04..HEAD)
```

Signed-off-by: Tim Liu <[email protected]>

* Revert "Update Copyright 2024"

This reverts commit 8482847.

* Revert "Remove 351 shim's jason string"

This reverts commit 78d1f00.

* skip 351 from strict checking

* Alien scala2.13/pom.xml to scala2.12 one

Run the script `bash build/make-scala-version-build-files.sh 2.13`

Signed-off-by: Tim Liu <[email protected]>

* pretend 351 is a snapshot in 24.02

Signed-off-by: Gera Shegalov <[email protected]>

* pretend 351 is a SNAPSHOT version

* Revert change of build/shimplify.py

Signed-off-by: Tim Liu <[email protected]>

---------

Signed-off-by: Tim Liu <[email protected]>
Signed-off-by: Gera Shegalov <[email protected]>
Co-authored-by: Raza Jafri <[email protected]>
Co-authored-by: Gera Shegalov <[email protected]>

* Update changelog for v24.02.0 release (#10525)

Signed-off-by: Tim Liu <[email protected]>

---------

Signed-off-by: Tim Liu <[email protected]>
Signed-off-by: Gera Shegalov <[email protected]>
Co-authored-by: Raza Jafri <[email protected]>
Co-authored-by: Gera Shegalov <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Related to CI / CD or cleanly building
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants