Remote Data access via Get() or Transport #3740
Merged
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.
This is a replacement for the prior WIP Remote PR (which I will delete when this is merged). This has been reformatted with the new clang-format parameters and contains a tiny bit of Norbert's campaign tweaks (the RemoteDataPath parameter). However, it can still be activated with the
DoRemote
environment variable (activates Get()-level remote data access) and theDoFileRemote
environment variable (activates transport-level remote data access). If only DoRemote is activated, the metadata is read locally and Get() operations sent to the remote server. If only DoFileRemote is activated, all file access is sent to the remote server, including metadata reads. (This is a temporary measure to test the mechanism, not a final solution.). If both are activated, metadata access happens via the remote data mechanism and data access (via Get()) is done via the remote Get() mechanism.