Skip to main content
Use the @bijection/connectors/opensearch entrypoint to declare OpenSearch resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Index

scan: scan

The following example matches configuration standard.

Configuration: standard

Case: opensearch/index/scan/standard. Connection and resource configuration are declared by this exact case. Credential kind: opensearch. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

These recipes declare sources read by the native store transport: Azure Cosmos DB, Apache Cassandra, Elasticsearch, OpenSearch, Apache HBase (REST server), Neo4j (HTTP Query API), Redis keys, OPC UA servers and the AVEVA PI System through PI Web API. A document store record is { key, document }; a historian sample is { key, stream, time, value, status }; a discovery listing entry is { key, name, document }. The declaration names only what changes what a publication proves: which change history is followed, and deletions: { everyHours }, which looks every published key up by key at that interval and withdraws the keys the store answers absent for. A sweep is refused where the change history already carries deletions (Cosmos DB all versions and deletes, Neo4j change data capture), for OPC UA, and for PI points and values; a PI AF pass takes one. Endpoints, databases, containers, keyspaces, tables, indexes, labels, key properties, key patterns, nodes and points are binding setup; credentials are private connection configuration. PI values read installed points (names on dataServer) and attributes (full AF attribute paths). A pi.values.channel connection is never continuous with the previous one: each first reads recorded values from the retained position, then follows the channel until its window ends or the channel closes, fails or stays silent past its heartbeat bound. PI recorded and channel sources may declare writes: { commands: { <name>: "create" } } (no marker): a create adds { value } at its key’s time (<WebId>|<time>|0) with updateOption=NoReplace and bufferOption=DoNotBuffer, and a lost answer is settled by reading the value back. OPC UA uses security policy None, so it reaches only loopback endpoints or a co-located gateway; signed and encrypted policies are not built. These registrations establish no provider check or hosted qualification; see the platform’s provider pages for what each reader proves and its limits.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.