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

Fix issue #467 - Move imports to rbc.heavydb #470

Merged

Conversation

guilhermeleobas
Copy link
Contributor

@guilhermeleobas guilhermeleobas commented Mar 29, 2022

As title.

  • Moves all imports from rbc.heavai.* to rbc.heavydb.*
  • Rename the test folder rbc/tests/heavyai to rbc/tests/heavydb
  • Includes a test file rbc/tests/heavydb/test_imports.py that ensures imports for Array, ArrayPointer, Bytes, Column are working as expected. Some of those imports are used in UD[T]Fs to create objects at runtime, others are used internally in jitted functions.

@guilhermeleobas guilhermeleobas added the code quality Code quality label Mar 29, 2022
@guilhermeleobas guilhermeleobas self-assigned this Mar 29, 2022
@guilhermeleobas guilhermeleobas linked an issue Mar 29, 2022 that may be closed by this pull request
@guilhermeleobas guilhermeleobas force-pushed the guilhermeleobas/issue467 branch from 202c45f to d884525 Compare March 29, 2022 16:25
@guilhermeleobas guilhermeleobas requested review from pearu and tupui March 29, 2022 17:19
Copy link
Contributor

@tupui tupui left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice! I went over all the files, LGTM. Just 2 remarks.

Ultimately, why don't we just move heavydb into heavydb_backend?

@guilhermeleobas guilhermeleobas force-pushed the guilhermeleobas/issue467 branch from c9da34e to 5335a1f Compare March 29, 2022 18:42
@guilhermeleobas guilhermeleobas force-pushed the guilhermeleobas/issue467 branch from 5335a1f to 8056911 Compare March 29, 2022 19:06
Copy link
Contributor

@tupui tupui left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM now. Although I see you adding files again. Are you missing more?

Copy link
Contributor

@pearu pearu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Re @tupui comment: Ultimately, why don't we just move heavydb into heavydb_backend?

Yes, I think it makes sense but as a follow-up PR:

  • move heavydb.py to heavydb_backend/remote_heavydb.py (or suggest a better name)
  • rename heavydb_backend/ to heavydb/
  • expose the UI of heavydb.py via heavydb/__init__.py

@guilhermeleobas
Copy link
Contributor Author

LGTM now. Although I see you adding files again. Are you missing more?

I've messed up during rebase 😆

@guilhermeleobas guilhermeleobas merged commit 377e0ce into heavyai:master Mar 29, 2022
@guilhermeleobas guilhermeleobas deleted the guilhermeleobas/issue467 branch March 29, 2022 20:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code quality Code quality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Rename heavyai to heavydb
3 participants