-
Notifications
You must be signed in to change notification settings - Fork 654
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-#2957: Restructure project files #3210
REFACTOR-#2957: Restructure project files #3210
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3210 +/- ##
===========================================
- Coverage 85.66% 60.70% -24.97%
===========================================
Files 150 178 +28
Lines 15969 15450 -519
===========================================
- Hits 13680 9379 -4301
- Misses 2289 6071 +3782
Continue to review full report at Codecov.
|
this doesn't move files or anything, why would we want a |
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.
@vnlitvinov , I guess @devin-petersohn wanted to move the structure discussion from the issue to a PR to simplify the structure correction not commenting it each time.
@vnlitvinov to help see the overall structure before we move anything. github diff is not super great at showing large restructure like this |
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 discussed these changes in a call today, I think this structure looks good
project_structure.txt
Outdated
.test/ | ||
.rest files | ||
.core/ | ||
.storage_formats/ |
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.
Doing the refactor one thought came in my mind. I see three options:
- Leave as it is now
- Put
storage_formats
along withexecution
indataframe
. - Move
execution
to the higher level to reside it along withstorage_formats
incore
.
I am more inclined towards the third option. What do you think would be the best choice?
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.
3rd option is currently applied.
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.
Yes, the 3rd option makes the most sense to me
Track current stage of the project structure in |
242e89e
to
325f168
Compare
@modin-project/modin-core , @modin-project/modin-omnisci , reminder to review. |
@YarShev does Teamcity need to be updated? |
@devin-petersohn , TeamCity failed (upon timeout) because conda takes a huge time to create an environment. We should merge #3409 first to be unblocked to run tests there. |
5eeb2f9
to
193a873
Compare
@YarShev @devin-petersohn where are we with this? I don't think we need to polish the namings much longer, we can always re-do them partially later when desired (as we haven't hit the I have scanned over the |
@vnlitvinov , current stage of the project structure is about what we wanted to reach. It might be required to introduce some local changes based on potential reviews. I created two issues to polish the code and the docs (#3412 and #3413, respectively) that should be resolved in 0.11.
+1 to default2pandas |
bea2682
to
193a873
Compare
Signed-off-by: Devin Petersohn <[email protected]>
Signed-off-by: Igoshev, Yaroslav <[email protected]>
Signed-off-by: Igoshev, Yaroslav <[email protected]>
Signed-off-by: Igoshev, Yaroslav <[email protected]>
Signed-off-by: Igoshev, Yaroslav <[email protected]>
Signed-off-by: Igoshev, Yaroslav <[email protected]>
193a873
to
193e872
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.
Mostly fine, but I got a couple of comments...
# ANY KIND, either express or implied. See the License for the specific language | ||
# governing permissions and limitations under the License. | ||
|
||
"""Modin's functionality related to dispatching to specific execution.""" |
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 would like this to be a little more elaborate
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 would like to hear an example :) but this should go in a separate issue/PR regarding cosmetic changes.
@devin-petersohn can I fix conflicts myself? UPD: since I did not find commits in your branch that would fix conflicts, added them myself. |
Signed-off-by: Devin Petersohn <[email protected]>
Signed-off-by: Devin Petersohn <[email protected]>
Signed-off-by: Devin Petersohn <[email protected]>
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.
Mostly fine to me. There are two comments/questions from my side.
- We should probably move
modin/core/execution/ray/implementations/pandas_on_ray/modin_aqp.py
to
modin/core/execution/ray/generic/modin_aqp.py
or
modin/core/execution/ray/common/modin_aqp.py
- We should probably move the following files:
modin/experimental/core/execution/native/implementations/omnisci_on_native/dataframe/calcite_algebra.py
modin/experimental/core/execution/native/implementations/omnisci_on_native/dataframe/calcite_builder.py
modin/experimental/core/execution/native/implementations/omnisci_on_native/dataframe/calcite_serializer.py
modin/experimental/core/execution/native/implementations/omnisci_on_native/dataframe/df_algebra.py
modin/experimental/core/execution/native/implementations/omnisci_on_native/dataframe/expr.py
modin/experimental/core/execution/native/implementations/omnisci_on_native/dataframe/omnisci_worker.py
to a higher lever or somewhere else. Any options?
...xperimental/core/execution/native/implementations/omnisci_on_native/partitioning/__init__.py
Outdated
Show resolved
Hide resolved
.../experimental/core/execution/native/implementations/omnisci_on_native/dataframe/partition.py
Outdated
Show resolved
Hide resolved
Moved |
0cc0980
to
1fe61d8
Compare
1fe61d8
to
7596c88
Compare
e7d45e0
to
dfe2d8f
Compare
@devin-petersohn , @vnlitvinov , reminder to review |
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.
LGTM, thanks @YarShev
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.
LGTM! 🎉
Signed-off-by: Devin Petersohn [email protected]
What do these changes do?
flake8 modin
black --check modin
git commit -s
docs/developer/architecture.rst
is up-to-date