-
Notifications
You must be signed in to change notification settings - Fork 915
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
Deprecate decimal_cols_as_float
in ORC reader (C++ layer)
#10152
Conversation
Codecov Report
@@ Coverage Diff @@
## branch-22.04 #10152 +/- ##
================================================
+ Coverage 10.37% 10.43% +0.05%
================================================
Files 119 119
Lines 20149 20594 +445
================================================
+ Hits 2091 2148 +57
- Misses 18058 18446 +388
Continue to review full report at Codecov.
|
@@ -220,7 +220,9 @@ class orc_reader_options { | |||
* | |||
* @param val Vector of fully qualified column names. | |||
*/ | |||
void set_decimal_cols_as_float(std::vector<std::string> val) | |||
[[deprecated( |
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.
Does this add a compiler warning when building libcudf?
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 should issue warnings only when the function is used.
https://en.cppreference.com/w/cpp/language/attributes/deprecated
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 see. I read that page earlier but thought it was showing compiler output and not runtime output. Thanks for the correction.
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.
Should we also update the documentation to indicate that the method is deprecated? I don't think we have any real policies around this in libcudf, and I doubt many people actually read our doxygen, but it might still be nice to add a message. Otherwise LGTM.
I haven't done so when previously deprecating APIs, but I'm not opposed to it. Do you know of an example where we included this info in the docs? |
I do not. It would be nice for us to have some policy around how deprecations should be handled in libcudf (we have a rough one in cuDF Python) but no need to hold up this PR for that if we don't already have a standard. It might be something we could define and document in the dev guide for future use, though. |
@gpucibot merge |
Issue #10129