refactor(orientdb): use rest-api instead of client library #80
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The client library seems not well maintained and contains pretty outdated dependencies. For testing purposes using the REST-API works well enough.
retry
is used to stabilise the test, since at least locally it took the container some time after start-up to accept REST-API requests sometimes. I couldn't find out a way to wait exactly for the time when the API is ready. According to the container logs the start-up is finished.Closes #38