-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
[data][doc] Add DatasetConfig -> DataConfig migration guide #37278
[data][doc] Add DatasetConfig -> DataConfig migration guide #37278
Conversation
Signed-off-by: Hao Chen <chenh1024@gmail.com>
# __legacy_api_end__ | ||
|
||
# __new_api__ | ||
from ray.train.data_config import DataConfig |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should be clear here that ray.train.data_config
is not a public API. All the configs should be included via ray.train
directly going forward. Also see the PR description of #36706 and the REP ray-project/enhancements#36 :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ericl maybe we should rename data_config
to _data_config
so there are not two ways to do this and people get confused?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should put it in a _internal folder then probably, to follow convention of other libraries.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, let's replace ray.train.data_config
with ray.train
everywhere in this PR before merging, and then we can do the _internal
refactor later as time permits (doesn't need to be part of 2.6).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So I assume nothing is needed in this PR, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is -- you need to replace ray.train.data_config.DataConfig
with ray.train.DataConfig
everywhere :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh, I didn't know it's already in ray.train
. I think there may be other places using ray.train.data_config
as well. Will update all.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, that's awesome :)
Signed-off-by: Hao Chen <chenh1024@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, feel free to merge if the CI passes :)
@pcmoritz also moved |
Thanks, that's great! Yes, it needs to be cherry-picked :) |
…ect#37278) - Add DatasetConfig -> DataConfig migration guide - Move ray.train.data_config to ray.train._internal.data_config --------- Signed-off-by: Hao Chen <chenh1024@gmail.com>
…ide (#37383) * [data][doc] Add DatasetConfig -> DataConfig migration guide (#37278) - Add DatasetConfig -> DataConfig migration guide - Move ray.train.data_config to ray.train._internal.data_config --------- Signed-off-by: Hao Chen <chenh1024@gmail.com> * fix Signed-off-by: Hao Chen <chenh1024@gmail.com> --------- Signed-off-by: Hao Chen <chenh1024@gmail.com>
##37278 moved `ray.train.data_config` to `ray.train._internal.data_config`. But missed this place.
…ect#37278) - Add DatasetConfig -> DataConfig migration guide - Move ray.train.data_config to ray.train._internal.data_config --------- Signed-off-by: Hao Chen <chenh1024@gmail.com>
…ect#37278) - Add DatasetConfig -> DataConfig migration guide - Move ray.train.data_config to ray.train._internal.data_config --------- Signed-off-by: Hao Chen <chenh1024@gmail.com> Signed-off-by: NripeshN <nn2012@hw.ac.uk>
#ray-project#37278 moved `ray.train.data_config` to `ray.train._internal.data_config`. But missed this place. Signed-off-by: NripeshN <nn2012@hw.ac.uk>
…ect#37278) - Add DatasetConfig -> DataConfig migration guide - Move ray.train.data_config to ray.train._internal.data_config --------- Signed-off-by: Hao Chen <chenh1024@gmail.com> Signed-off-by: e428265 <arvind.chandramouli@lmco.com>
#ray-project#37278 moved `ray.train.data_config` to `ray.train._internal.data_config`. But missed this place. Signed-off-by: e428265 <arvind.chandramouli@lmco.com>
…ect#37278) - Add DatasetConfig -> DataConfig migration guide - Move ray.train.data_config to ray.train._internal.data_config --------- Signed-off-by: Hao Chen <chenh1024@gmail.com> Signed-off-by: Victor <vctr.y.m@example.com>
#ray-project#37278 moved `ray.train.data_config` to `ray.train._internal.data_config`. But missed this place. Signed-off-by: Victor <vctr.y.m@example.com>
Why are these changes needed?
ray.train.data_config
toray.train._internal.data_config
Related issue number
closes #35958
Checks
git commit -s
) in this PR.scripts/format.sh
to lint the changes in this PR.method in Tune, I've added it in
doc/source/tune/api/
under thecorresponding
.rst
file.