OCI Search with OpenSearch

ociSearch indexoci-opensearch

Managed OpenSearch cluster with private endpoints, scheduled backups and Oracle-run upgrades.

Provider
oci
Category
Data
Properties · 3 set by this component
propertytypevaluesrequiredkind defaultthis component
dataNodes · component propertyinteger—no—inherited
geoScheme · advancedenumnone | s2 | h3 | geohash | quadtreenononeinherited
indexingenumsync | async | batchnoasyncinherited
leaderNodes · component propertyinteger—no—inherited
managedboolean—nofalse▸ true
nodeProfile · component propertyenumdevelopment | application-search | log-analyticsno—inherited
privateEndpointOnly · component propertyboolean—notrueinherited
rebuildCadenceHours · advancedinteger—no—inherited
replicasinteger—no—inherited
searchableSnapshots · component propertyboolean—nofalseinherited
shardingStrategy · advancedenumnone | hash | geo | time | prefix-rangenonone▸ hash
structureenuminverted | trie | vector | geo-cellnoinverted▸ inverted
Rules that apply · 1

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

derived-store-without-cdc-or-rebuild

A search index is derived data and needs an asynchronous feed from a stream, change data capture or an indexing worker. Without one it is written inline on the request path, and it can never be rebuilt after it drifts.

  • — this does not hold:
  • — the node has at least one asynchronous incoming edge from a stream, change-data-capture or worker
Use it in a design
nodes:
  - { id: "opensearch", component: "oci-opensearch" }
Other Search index products · 31
Source
# yaml-language-server: $schema=../../schema/component.schema.json
# OCI Search with OpenSearch cluster: managed OpenSearch that Oracle patches, upgrades, resizes and backs up
# on a schedule ("About Search with OpenSearch"). The cluster is reached only through private endpoints in
# its own VCN. "Creating a Search with OpenSearch Cluster" allows 1-10 data nodes, 1-3 leader nodes and
# 1-3 OpenSearch Dashboards nodes, with sizing defaults taken from the selected node optimization profile.
schemaVersion: "1"
type: "component"
id: "oci-opensearch"
kind: "search-index"
provider: "oci"
docs: "https://docs.oracle.com/en-us/iaas/Content/search-opensearch/Concepts/ociopensearch.htm"
defaults:
  managed: true
  structure: "inverted"
  shardingStrategy: "hash"
properties:
  dataNodes:
    type: "integer"
  leaderNodes:
    type: "integer"
  nodeProfile:
    type: "enum"
    values: ["development", "application-search", "log-analytics"]
  privateEndpointOnly:
    type: "boolean"
    default: true
  searchableSnapshots:
    type: "boolean"
    default: false

The same page as markdown, for an agent: /catalogue/components/oci-opensearch.md