Plug Database Advanced icon

Plug Database Advanced

Run Plug Database commands over REST or Socket.

Actions26

SQL → Validate Context

AI-generated

Summary

Validate the execution context for SQL commands on the Plug Database Advanced node using either REST or socket communication, optionally specifying agent and client token overrides, with configurable timeout and socket buffering options.

Inputs

  • Channel (required) — Select 'REST' to run the validation via REST API or 'Socket' to use the Plug consumer socket connection.
  • Agent ID — Optionally override the target Plug agent ID; defaults to the credential's default agent ID if empty.
  • Client Token — Optionally override the Plug client token; defaults to the credential's default client token if empty.
  • Include Plug Metadata — Choose whether to include the '__plug' metadata object with channel, agent, request, and socket details in the operation output.
  • Additional Options - Timeout (ms) — Optional timeout in milliseconds for the validation request, defaulting to 15000 ms.
  • Socket Options (shown if Channel is 'Socket') - Max Buffered Rows — Maximum number of rows buffered locally while collecting socket stream output; default is 50000.
  • Socket Options - Max Buffered Bytes — Approximate maximum JSON bytes buffered locally during socket stream output collection; default is 8388608 bytes.
  • Socket Options - Max Buffered Chunks — Maximum socket stream chunks buffered before the node fails clearly; default is 512 chunks.
  • Socket Options - Stream Pull Window Size — Number of socket stream chunks requested per pull window from Plug, between 1 and 1000; defaults to 32.

Output shape

a single JSON object representing the validation result, optionally enriched with Plug metadata.

The operation returns the validation response from the Plug service as a JSON object. If 'Include Plug Metadata' is enabled, the output includes a '__plug' object with metadata about the communication channel, agent information, request, and socket state. When using the socket channel, output is subject to configured local buffering limits. The node handles timeouts and errors according to specified options.

Links

Discussion