-
Notifications
You must be signed in to change notification settings - Fork 13
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
Plan to add bulk import / export? #6
Comments
Submitted an initial PR #7 (Definitely not complete). Wanted to see what is on your mind to make this complete. |
@johansja Are you still working on implementing this feature? We have forked the project and are supporting it on best efforts basis. Being a 2 members developer team we cannot devote the required time to build all the features. However, some mission-critical features have been corrected. Can you please contribute in the project referenced below and help it grow? Thus, allowing you to get involved with the Elixir community. By Mar 2019, we hope to have all the essential features available and documented. You can help by doing the following: |
@chintan-mishra I'm not actively using ArangoDB at the moment. I'll definitely checkout that repo. Do you mind listing out the enhancements that you have done? How do you plan to publish that to hex.pm? |
@johansja Fixed most of the failing tests. Transaction, and AQLValidation failed tests are remaining. These will be fixed come August end. The library now supports Elixir 1.7 and higher. But can also work with Elixir 1.6 with changes in |
We created this issue on GitLab the day we forked the library. If you have any insights on how to do this then please share it in the issue above. If all else fails I will try and contact support of hex.pm. |
Any plan to add Bulk Import / Export? I have around 300,000 documents to insert into a collection. And according to the
:timer.tc
output, each individual document create now takes around 25ms. So currently figuring out on how can I speed up the loading of the documents and that endpoint seems like something interesting.The text was updated successfully, but these errors were encountered: