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

Backport concatenation fix of cudf.RangeIndex #8984

Merged
merged 1 commit into from
Aug 6, 2021

Conversation

galipremsagar
Copy link
Contributor

This is a backport of #8970 to 21.08

Fixes: rapidsai#6872 

In cudf, we have been concatenating a collection of `RangeIndex`'s by materializing each one of them, but instead we should rather be introspecting each RangeIndex to decide whether to materialize of not. This PR fixes it.

<!--

Thank you for contributing to cuDF :)

Here are some guidelines to help the review process go smoothly.

1. Please write a description in this text box of the changes that are being
   made.

2. Please ensure that you have written units tests for the changes made/features
   added.

3. There are CI checks in place to enforce that committed code follows our style
   and syntax standards. Please see our contribution guide in `CONTRIBUTING.MD`
   in the project root for more information about the checks we perform and how
   you can run them locally.

4. If you are closing an issue please use one of the automatic closing words as
   noted here: https://help.github.com/articles/closing-issues-using-keywords/

5. If your pull request is not ready for review but you want to make use of the
   continuous integration testing facilities please mark your pull request as Draft.
   https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request#converting-a-pull-request-to-a-draft

6. If your pull request is ready to be reviewed without requiring additional
   work on top of it, then remove it from "Draft" and make it "Ready for Review".
   https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request#marking-a-pull-request-as-ready-for-review

   If assistance is required to complete the functionality, for example when the
   C/C++ code of a feature is complete but Python bindings are still required,
   then add the label `help wanted` so that others can triage and assist.
   The additional changes then can be implemented on top of the same PR.
   If the assistance is done by members of the rapidsAI team, then no
   additional actions are required by the creator of the original PR for this,
   otherwise the original author of the PR needs to give permission to the
   person(s) assisting to commit to their personal fork of the project. If that
   doesn't happen then a new PR based on the code of the original PR can be
   opened by the person assisting, which then will be the PR that will be
   merged.

7. Once all work has been done and review has taken place please do not add
   features or make changes out of the scope of those requested by the reviewer
   (doing this just add delays as already reviewed code ends up having to be
   re-reviewed/it is hard to tell what is new etc!). Further, please do not
   rebase your branch on the target branch, force push, or rewrite history.
   Doing any of these causes the context of any comments made by reviewers to be lost.
   If conflicts occur against the target branch they should be resolved by
   merging the target branch into the branch used for making the pull request.

Many thanks in advance for your cooperation!

-->

Authors:
  - GALI PREM SAGAR (https://github.com/galipremsagar)

Approvers:
  - Benjamin Zaitlen (https://github.com/quasiben)
  - Vyas Ramasubramani (https://github.com/vyasr)

URL: rapidsai#8970
@galipremsagar galipremsagar requested review from a team as code owners August 6, 2021 03:03
@galipremsagar galipremsagar requested review from brandon-b-miller and marlenezw and removed request for a team August 6, 2021 03:03
@galipremsagar galipremsagar self-assigned this Aug 6, 2021
@github-actions github-actions bot added the Python Affects Python cuDF API. label Aug 6, 2021
@galipremsagar galipremsagar added 3 - Ready for Review Ready for review by team 4 - Needs cuDF (Python) Reviewer Python Affects Python cuDF API. and removed Python Affects Python cuDF API. labels Aug 6, 2021
@galipremsagar galipremsagar added bug Something isn't working non-breaking Non-breaking change labels Aug 6, 2021
@codecov
Copy link

codecov bot commented Aug 6, 2021

Codecov Report

Merging #8984 (1a67aba) into branch-21.08 (6193093) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

❗ Current head 1a67aba differs from pull request most recent head a2840c6. Consider uploading reports for the commit a2840c6 to get more accurate results
Impacted file tree graph

@@               Coverage Diff                @@
##           branch-21.08    #8984      +/-   ##
================================================
- Coverage         10.58%   10.56%   -0.02%     
================================================
  Files               116      116              
  Lines             18650    18677      +27     
================================================
  Hits               1974     1974              
- Misses            16676    16703      +27     
Impacted Files Coverage Δ
python/cudf/cudf/core/index.py 0.00% <0.00%> (ø)
python/cudf/cudf/utils/gpu_utils.py 0.00% <0.00%> (ø)
python/cudf/cudf/utils/ioutils.py 0.00% <ø> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7de5c52...a2840c6. Read the comment docs.

@quasiben
Copy link
Member

quasiben commented Aug 6, 2021

cc @rjzamora for awareness

@raydouglass raydouglass merged commit 7c1251a into rapidsai:branch-21.08 Aug 6, 2021
@vyasr vyasr added 4 - Needs Review Waiting for reviewer to review or respond and removed 4 - Needs cuDF (Python) Reviewer labels Feb 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3 - Ready for Review Ready for review by team 4 - Needs Review Waiting for reviewer to review or respond bug Something isn't working non-breaking Non-breaking change Python Affects Python cuDF API.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants