-
Notifications
You must be signed in to change notification settings - Fork 58
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
Add a new KvikIO compatibility mode "AUTO" #547
base: branch-24.12
Are you sure you want to change the base?
Add a new KvikIO compatibility mode "AUTO" #547
Conversation
69660c6
to
6557e56
Compare
4884ccf
to
db89849
Compare
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.
Looks great @kingcrimsontianyu but I am wondering if we should use the CompatMode
enum instead of a string throughout?
I'm still debating on this. My thought is that no matter what value the user specifies (via the environment variable or PS: If we decide to expose |
I have no strong opinion, but leaning towards exposing
No, I don't think that is needed. |
cpp/src/file_handle.cpp
Outdated
return; // Nothing to do in compatibility mode | ||
} else if (_compat_mode == CompatMode::AUTO) { | ||
_compat_mode = defaults::infer_compat_mode_from_runtime_sys(_compat_mode); |
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.
why not infer in _compat_mode
init?
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.
I've brought the infer to the beginning of the constructor. Is this what you would recommend?
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.
I meant the line _compat_mode{compat_mode}
, but it looks like we don't want to infer at all to ensure correct fallback.
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.
Looks great @kingcrimsontianyu! Could you also update the C++ docs and the Python docs ?
/ok to test |
1 similar comment
/ok to test |
/ok to test |
1 similar comment
/ok to test |
Contributes to rapidsai/build-planning#110 Proposes adding 2 types of validation on wheels in CI, to ensure we continue to produce wheels that are suitable for PyPI. * checks on wheel size (compressed), - *to be sure they're under PyPI limits* - *and to prompt discussion on PRs that significantly increase wheel sizes* * checks on README formatting - *to ensure they'll render properly as the PyPI project homepages* - *e.g. like how https://github.com/scikit-learn/scikit-learn/blob/main/README.rst becomes https://pypi.org/project/scikit-learn/* Authors: - James Lamb (https://github.com/jameslamb) Approvers: - Bradley Dice (https://github.com/bdice) URL: rapidsai#548
b5e07ae
to
0725d63
Compare
This PR addresses issue #529. A new compatibility mode
AUTO
(previously proposed asALLOW
) is added that explicitly asks KvikIO to determine whetherON
orOFF
is eventually used for the I/O.Closes #529