Fixes #4207: Integration Tests for Load Procedures with Cloud Object Storage #4226
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vga91
force-pushed
the
issue_4207
branch
3 times, most recently
from
c2d37b1
to
7aaec56
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #4207
WIP: waiting for dev fix CI
TODO - doing export as well, now that the arrow procs are in core dev, waiting for CI error resolutionapoc.load.directory*ones, which currently does not accept URLs, but only paths ()extended-it(which should contains all dockerized tests)NB: external dependencies for s3 and google cloud are still needed since they are only included in neo4j enterprise: see here
NB2: currently only S3 export procedures seem to work, Google Cloud and Azure Storage require additional handlings in
FileUtils.java(located in core). Opened a Trello Core card with id2pCEUm76with a possibile solution