Files
doc-exports/docs/css/umn/css_01_0463.html
zhengxiu 2125539080 css umn 25.1.0 version
Reviewed-by: Pruthi, Vineet <vineet.pruthi@t-systems.com>
Co-authored-by: zhengxiu <zhengxiu@huawei.com>
Co-committed-by: zhengxiu <zhengxiu@huawei.com>
2025-07-04 09:10:17 +00:00

55 lines
5.2 KiB
HTML

<a name="css_01_0463"></a><a name="css_01_0463"></a>
<h1 class="topictitle1">Search Enhancement Features for OpenSearch Clusters</h1>
<div id="body0000001992165593"><p id="css_01_0463__css_01_0400_p8060118">Compared with open-source OpenSearch, OpenSearch clusters in CSS have many enhanced features. <a href="#css_01_0463__css_01_0400_table25351046105517">Table 1</a> lists these enhanced features and the corresponding cluster versions.</p>
<div class="tablenoborder"><a name="css_01_0463__css_01_0400_table25351046105517"></a><a name="css_01_0400_table25351046105517"></a><table cellpadding="4" cellspacing="0" summary="" id="css_01_0463__css_01_0400_table25351046105517" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Search enhancement features for OpenSearch clusters</caption><thead align="left"><tr id="css_01_0463__css_01_0400_row1753644610558"><th align="left" class="cellrowborder" valign="top" width="15%" id="mcps1.3.2.2.5.1.1"><p id="css_01_0463__css_01_0400_p1853618461554">Enhanced Feature</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="50%" id="mcps1.3.2.2.5.1.2"><p id="css_01_0463__css_01_0400_p135361546165518">Description</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="20%" id="mcps1.3.2.2.5.1.3"><p id="css_01_0463__css_01_0400_p2354191071">Cluster Version</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="15%" id="mcps1.3.2.2.5.1.4"><p id="css_01_0463__css_01_0400_p153684614555">Details</p>
</th>
</tr>
</thead>
<tbody><tr id="css_01_0463__css_01_0400_row18536746175519"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.2.2.5.1.1 "><p id="css_01_0463__css_01_0400_p353674615553">Vector search</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.2.2.5.1.2 "><p id="css_01_0463__css_01_0400_en-us_topic_0000001223594448_p368234122719">Unstructured data, such as images, videos, and language corpora, is converted into vectors, which are searched based on similarity using either an exact or approximate nearest neighbors algorithm.</p>
</td>
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.2.2.5.1.3 "><p id="css_01_0463__css_01_0400_p143531918718">OpenSearch 1.3.6</p>
</td>
<td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.2.2.5.1.4 "><p id="css_01_0463__p26820405116"><a href="css_01_0465.html">About Vector Search</a></p>
</td>
</tr>
<tr id="css_01_0463__css_01_0400_row145361046115514"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.2.2.5.1.1 "><p id="css_01_0463__css_01_0400_p1353613460553">Storage-compute decoupling</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.2.2.5.1.2 "><p id="css_01_0463__css_01_0400_en-us_topic_0000001268314513_p15593195719441">CSS stores new data as hot data on SSDs to ensure optimal query performance, and historical data as cold data in OBS to cut storage costs.</p>
<p id="css_01_0463__css_01_0400_p20465101118320">Compared with cold/hot storage switchover, storage-compute decoupling is a better option for use cases that are not particularly demanding in terms of search performance, as cold data is stored in OBS, which cuts storage costs.</p>
</td>
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.2.2.5.1.3 "><p id="css_01_0463__css_01_0400_p943713580166">OpenSearch 1.3.6</p>
</td>
<td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.2.2.5.1.4 "><p id="css_01_0463__p1968211406112"><a href="css_01_0473.html">Configuring Storage-Compute Decoupling for an OpenSearch Cluster</a></p>
</td>
</tr>
<tr id="css_01_0463__css_01_0400_row1838312223614"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.2.2.5.1.1 "><p id="css_01_0463__css_01_0400_p138482211617">Switchover between hot and cold storage</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.2.2.5.1.2 "><p id="css_01_0463__css_01_0400_p913621617206">You can keep hot data on high-performance servers to ensure fast query response times (in seconds). For historical data that requires a query response time of minutes, you can keep it on large-capacity, low-specs servers as cold data. This allows you to cut storage costs and improve search efficiency.</p>
<p id="css_01_0463__css_01_0400_p1112642319398">Compared with storage-compute decoupling, cold/hot storage switchover is a better option for use cases that are demanding in terms of search performance. Cold data is stored on local cold data nodes in the cluster. The storage capacity available depends on the number of cold data nodes and their disk capacity. The storage cost is higher than that of OBS.</p>
</td>
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.2.2.5.1.3 "><p id="css_01_0463__css_01_0400_p9351219273">This feature is supported as long as the cluster has cold data nodes.</p>
</td>
<td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.2.2.5.1.4 "><p id="css_01_0463__p136781440317"><a href="css_01_0474.html">Switching Between Hot and Cold Storage for an OpenSearch Cluster</a></p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0462.html">Enhancing Search Capabilities for OpenSearch Clusters</a></div>
</div>
</div>