Package com.complexible.stardog.api

Class AbstractConnectionConfiguration<T>

java.lang.Object
com.complexible.stardog.api.AbstractConnectionConfiguration<T>
All Implemented Interfaces:
LoginConnectionConfiguration<T>
Direct Known Subclasses:
AdminConnectionConfiguration, ConnectionConfiguration
public abstract class AbstractConnectionConfiguration<T> extends Object implements LoginConnectionConfiguration<T>
Since:
2.0
Version:
3.0
Author:
Hector Perez-Urbina, Michael Grove

  • Field Details

    • mOptions

      protected final Options mOptions

    • mOptionParser

      public static final OptionParser mOptionParser

    • RUN_AS_USER

      public static final Option<String> RUN_AS_USER

    • CONNECTION_TYPE

      public static final Option<String> CONNECTION_TYPE
      This is used to identify this connection as an internal Stardog connection. Used when connecting from a cluster-node to another cluster-node. The main use case is for a replicated cluster command to be able to tell the remote node that this connection is in fact replicated and not a command coming from an end user.

    • CLUSTER_ORIGIN_NODE

      public static final Option<String> CLUSTER_ORIGIN_NODE

    • PROCESS_ID

      public static final Option<String> PROCESS_ID
      Client-supplied process ID for the in-flight request, set from the SD-Process-Id HTTP header. When present, the value is used as the external ID of the process the request creates, so the client can poll for the process status with the same ID. Null when the client did not supply one.

      The ID is an opaque string and is not enforced to be a UUID by the process layer. Transactions are the exception: their ID must parse as a UUID. Using a UUID is generally recommended especially in a clustered Stardog setup.

  • Constructor Details

    • AbstractConnectionConfiguration

      protected AbstractConnectionConfiguration()

    • AbstractConnectionConfiguration

      protected AbstractConnectionConfiguration(Options theOptions)

  • Method Details