Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Components
Assignee
Greg PanagiotatosGreg PanagiotatosReporter
Jacob Cobbett-SmithJacob Cobbett-SmithPriority
MinorCompatibility
PointFix versions
Pull Request URL
Roadmap
2022q1
Details
Details
Components
Assignee
Greg Panagiotatos
Greg PanagiotatosReporter
Jacob Cobbett-Smith
Jacob Cobbett-SmithPriority
Compatibility
Point
Fix versions
Pull Request URL
Roadmap
2022q1
Created January 17, 2022 at 7:08 PM
Updated May 24, 2023 at 3:59 PM
Resolved May 24, 2023 at 3:59 PM
HPCC-26958 introduces the ability to access logical files from other remote environments in a cloud configuration.
This is acheived by configuring the storage section of hpcc helm chart with a "remote" section.
The storage.remote section is a list of named remote environments that define the remote service url and a section that maps remote plane names to local plane names.
The local planes referenced are special planes with category 'remote'. They are read-only and only exposed to the engines which can read from them.
Example:
This defines a remote target called "hpcc2" whose DFS service url is http://20.102.22.31:8010 and whose local plane is "hpcc2data".
The local plane must be defined such that it shares the same storage as the remote environment. This is expected to be done via a PVC that has been pre-configured to use the same storage.
A logical file will be access in ECL in the following form, e.g.: