-
Notifications
You must be signed in to change notification settings - Fork 3
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
Documentation: Improve docs for ctk load table
#221
Comments
Hi Hernan. Thanks for your suggestion. I am sure there are anomalies, but I can't spot them, probably because of operational blindness, and your description doesn't tell me anything where to apply an improvement, and what, at least not enough to make it actionable for me. I know that Can I humbly ask you to submit a corresponding suggestion how and where to improve the documentation, either by commenting on the patch GH-216, or by submitting a separate one? Thanks a stack! |
Hi, apologies for the delay coming back to you on this. This is for the case where we may want the table on CrateDB to have a different name from the collection in MongoDB (a real world example involved the need to filter what was pulled from MongoDB which was done with a view on the MongoDB side - but the final desired state in CrateDB was to have a table with the collection's original name not the view's name), when I tested this it looked like |
Ah I see. Thanks for clarifying. Yes, in theory, the target table should be defined by |
Just a small thing that it may be worth mentioning in the docs, the schema translation part takes the name of the MongoDB collection for the
CREATE TABLE
statement but the data load part takes the table name from theCRATEDB_SQLALCHEMY_URL
so these 2 have to match forctk load table
to work.Originally posted by @hlcianfagna in #216 (review)
The text was updated successfully, but these errors were encountered: