-
Notifications
You must be signed in to change notification settings - Fork 653
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
REFACTOR-#1928: move columnarization to backend #1914
REFACTOR-#1928: move columnarization to backend #1914
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1914 +/- ##
==========================================
+ Coverage 81.53% 81.61% +0.07%
==========================================
Files 79 79
Lines 9192 9201 +9
==========================================
+ Hits 7495 7509 +14
+ Misses 1697 1692 -5
Continue to review full report at Codecov.
|
@ienkovich , can you please create an issue for the PR? |
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.
Also, the commit message should be the following: FEAT-#your_new_created_issue: move columnarization to backend
.
""" | ||
Transposes this QueryCompiler if it has a single row but multiple columns. | ||
|
||
This method should be called for QueryCompilers representing a Series object, |
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 don't understand this phrase. You say This method should be called for QueryCompilers representing a Series object, i.e. self.is_series_like() should be True.
, but you call columnarize
without previously is_series_like
called. Maybe, worth to delete/change it and is_series_like
is not needed at 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.
Currently, columnarize
method is called in Series init function only, where we already know data has a proper shape. Before creating Series object we use is_series_like
to check the shape. Both functions are used to move index accesses to a backend and provide an alternate implementation in the OmniSci backend, which would be able to avoid index access in certain cases.
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, thanks!
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.
Left a couple more minor suggestions, which you didn't apply.
""" | ||
Transposes this QueryCompiler if it has a single row but multiple columns. | ||
|
||
This method should be called for QueryCompilers representing a Series object, |
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, thanks!
Signed-off-by: ienkovich <ilya.enkovich@intel.com>
Pushed the rest of docstrings changes. |
@ienkovich , thanks, LGTM! |
…roject#1914) Signed-off-by: ienkovich <ilya.enkovich@intel.com>
What do these changes do?
This patch helps lazy backend to avoid index accesses in Series constructor by moving columnarization part into the backend.
flake8 modin
black --check modin
git commit -s