Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Clarify Std.File.Despray error messages on containerized systems

Description

In baremetal, the usual despray use form is:

Despray(<logicalfile>, <dstip>, <dstpath>)

>Despray(varstring logicalName, varstring destinationIP='', varstring destinationPath, integer4 timeOut=-1, varstring espServerIpPort=GETENV('ws_fs_server'), integer4 maxConnections=-1, boolean allowOverwrite=FALSE, varstring destinationPlane='') :=
lib_fileservices.FileServices.Despray(logicalName, destinationIP, destinationPath, timeOut, espServerIpPort, maxConnections, allowOverwrite, destinationPlane);

However, in cloud, a destination plane must be provided

> Despray(<logicalfile>, <destplane>, <dstpath>)

will hit an error that the destination plane is missing.

> Despray(<logicalfile>, DestinationPlane := <destplane>, DestinationPath := <dstpath>)

would be the correct form.
NB: it is valid to provide dstIP too, since target planes can have >1 hosts, and this allows for the selection from that list.

Conclusion

None

Activity

Show:

Jim DeFabia February 10, 2023 at 7:04 PM

there is enough info to continue.

Change needed to std lib reference and client tools manual DFUPlus section

Jacob Cobbett-Smith September 20, 2022 at 9:48 AM

is relevant/related. If they use the legacy form (destinationIP) and there is a single matching LZ with that host IP, it will now match and not error out.

Jacob Cobbett-Smith July 26, 2022 at 2:56 PM

after some reflection, although confusing, I'm not sure much more can be done as far as spotting the incorrect usage and improving the error.

The parameters to calls like this with optional params , can be misused.
It is probably always good practice to use named params, to avoid such issues.

- I suspect this is an area that might need documenting in a section relating to spraying/despraying in the cloud ?

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Components

Assignee

Reporter

Priority

Compatibility

Point

Fix versions

Pull Request URL

https://github.com/hpcc-systems/HPCC-Platform/pull/16958

Roadmap

Not applicable

Created July 26, 2022 at 1:54 PM
Updated February 20, 2023 at 9:43 AM
Resolved February 20, 2023 at 9:43 AM