Module aws_sdk_neptunedata::types

Data structures used by operation inputs/outputs.

Modules

• builders
  Builders
• error
  Error types that Amazon NeptuneData can respond with.

Structs

• CustomModelTrainingParameters

  Contains custom model training parameters. See Custom models in Neptune ML.

• CustomModelTransformParameters

  Contains custom model transform parameters. See Use a trained model to generate new model artifacts.

• DeleteStatisticsValueMap

  The payload for DeleteStatistics.

• EdgeStructure

  An edge structure.

• FastResetToken

  A structure containing the fast reset token used to initiate a fast reset.

• GremlinQueryStatus

  Captures the status of a Gremlin query (see the Gremlin query status API page).

• GremlinQueryStatusAttributes

  Contains status components of a Gremlin query.

• LoaderIdResult

  Contains a list of load IDs.

• MlConfigDefinition

  Contains a Neptune ML configuration.

• MlResourceDefinition

  Defines a Neptune ML resource.

• NodeStructure

  A node structure.

• PropertygraphData

  A Gremlin or openCypher change record.

• PropertygraphRecord

  Structure of a property graph record.

• PropertygraphSummary

  The graph summary API returns a read-only list of node and edge labels and property keys, along with counts of nodes, edges, and properties. See Graph summary response for a property graph (PG).

• PropertygraphSummaryValueMap

  Payload for the property graph summary response.

• QueryEvalStats

  Structure to capture query statistics such as how many queries are running, accepted or waiting and their details.

• QueryLanguageVersion

  Structure for expressing the query language version.

• RdfGraphSummary

  The RDF graph summary API returns a read-only list of classes and predicate keys, along with counts of quads, subjects, and predicates.

• RdfGraphSummaryValueMap

  Payload for an RDF graph summary response.

• RefreshStatisticsIdMap

  Statistics for REFRESH mode.

• SparqlData

  Neptune logs are converted to SPARQL quads in the graph using the Resource Description Framework (RDF) N-QUADS language defined in the W3C RDF 1.1 N-Quads specification

• SparqlRecord

  A serialized SPARQL stream record capturing a change-log entry for the RDF graph.

• Statistics

  Contains statistics information. The DFE engine uses information about the data in your Neptune graph to make effective trade-offs when planning query execution. This information takes the form of statistics that include so-called characteristic sets and predicate statistics that can guide query planning. See Managing statistics for the Neptune DFE to use.

• StatisticsSummary

  Information about the characteristic sets generated in the statistics.

• SubjectStructure

  A subject structure.

Enums

• Action
  When writing a match expression against Action, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• Encoding
  When writing a match expression against Encoding, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• Format
  When writing a match expression against Format, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• GraphSummaryType
  When writing a match expression against GraphSummaryType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• IteratorType
  When writing a match expression against IteratorType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• Mode
  When writing a match expression against Mode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• OpenCypherExplainMode
  When writing a match expression against OpenCypherExplainMode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• Parallelism
  When writing a match expression against Parallelism, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• S3BucketRegion
  When writing a match expression against S3BucketRegion, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• StatisticsAutoGenerationMode
  When writing a match expression against StatisticsAutoGenerationMode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.