-
Notifications
You must be signed in to change notification settings - Fork 263
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Developer guide for new structure data source integration #966
Developer guide for new structure data source integration #966
Conversation
@jiashenC Please review the documentation. Shall we ask for test cases when adding a new data source integration? If so, how do we do that given many of them needs to setup a backend server. Thanks! |
Yeah, for open sourced engine, we can probably setup server in CI as Postgres. For other commercial ones, we need to think of other solutions. |
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.
Overall it looks good.
- We probably need to explain where to add
requirements.txt
for installing native database-related libraries and how it is handled by us. - Just check the consistency of lower case / upper case for MyDB example.
…e-for-new-data-source-intergration
source. Make MyDB lower case.
|
||
.. note:: | ||
|
||
EvaDB will only install a data source's specific dependency libraries when a connection to the data source is created by the user via, e.g., `CREATE DATABASE mydb_source WITH ENGINE = "mydb";`. |
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.
@jiashenC This is what I have for requirements.txt. Could you help elaborate on that? 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.
Oh, i see. I missed that part.
Remove the unit test case requirements. We will add back when we have one. |
No description provided.