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

[doc] update the jvm tutorial to 1.6.1 [skip ci] #7834

Merged
merged 1 commit into from
Apr 24, 2022

Conversation

wbo4958
Copy link
Contributor

@wbo4958 wbo4958 commented Apr 22, 2022

No description provided.

@wbo4958 wbo4958 changed the title [doc] update the jvm tutorial to 1.6.1 [doc] update the jvm tutorial to 1.6.1 [skip ci] Apr 22, 2022
Copy link
Member

@trivialfis trivialfis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this is necessary.

@wbo4958
Copy link
Contributor Author

wbo4958 commented Apr 24, 2022

I don't think this is necessary.

I really don't like users to try xgboost4j-spark-gpu 1.6.0 version. please help to merge and update the page. Thx

@trivialfis trivialfis merged commit 6ece549 into dmlc:master Apr 24, 2022
@trivialfis trivialfis mentioned this pull request Apr 25, 2022
7 tasks
trivialfis pushed a commit to trivialfis/xgboost that referenced this pull request Apr 29, 2022
trivialfis added a commit that referenced this pull request Apr 29, 2022
* [jvm-packages] move the dmatrix building into rabit context (#7823)

This fixes the QuantileDeviceDMatrix in distributed environment.

* [doc] update the jvm tutorial to 1.6.1 [skip ci] (#7834)

* [Breaking][jvm-packages] Use barrier execution mode (#7836)

With the introduction of the barrier execution mode. we don't need to kill SparkContext when some xgboost tasks failed. Instead, Spark will handle the errors for us. So in this PR, `killSparkContextOnWorkerFailure` parameter is deleted.

* [doc] remove the doc about killing SparkContext [skip ci] (#7840)

* [jvm-package] remove the coalesce in barrier mode (#7846)

* [jvm-packages] Fix model compatibility (#7845)

* Ignore all Java exceptions when looking for Linux musl support (#7844)

Co-authored-by: Bobby Wang <[email protected]>
Co-authored-by: Michael Allman <[email protected]>
@@ -129,7 +129,7 @@ labels. A DataFrame like this (containing vector-represented features and numeri

.. note::

There is no need to assemble feature columns from version 1.6.0+. Instead, users can specify an array of
There is no need to assemble feature columns from version 1.6.1+. Instead, users can specify an array of
feture column names by ``setFeaturesCol(value: Array[String])`` and XGBoost4j-Spark will do it.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo: "feture" -> "feature"

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also, unrelated, but it would be helpful to comment whether is it possible to use the new categorical feature support in 1.6.X from xgboost4j.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the suggestion. It's Python only at the moment and is considered experimental. We will continue to expand it.

@wbo4958 wbo4958 deleted the 1.6.1-doc branch May 4, 2022 04:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants