From 6870679c9caf6ed33b9e35f16bcd1f4ccd5fa6b3 Mon Sep 17 00:00:00 2001 From: Nate B <96254688+nateynateynate@users.noreply.github.com> Date: Tue, 2 Apr 2024 14:52:49 -0700 Subject: [PATCH] Adjusting named anchor. Signed-off-by: Nate B <96254688+nateynateynate@users.noreply.github.com> --- _posts/2024-04-02-2.13-is-ready-for-download.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2024-04-02-2.13-is-ready-for-download.md b/_posts/2024-04-02-2.13-is-ready-for-download.md index 8c24d02f3e..2501ad1140 100644 --- a/_posts/2024-04-02-2.13-is-ready-for-download.md +++ b/_posts/2024-04-02-2.13-is-ready-for-download.md @@ -27,7 +27,7 @@ The [OpenSearch Assistant Toolkit](https://opensearch.org/docs/latest/ml-commons OpenSearch provides the ability to integrate with LLMs to power generative AI use cases. LLMs can potentially generate harmful content, so for this release, the OpenSearch [agent framework](https://opensearch.org/docs/latest/ml-commons-plugin/agents-tools/index/) adds support for [user-defined regex rules](https://opensearch.org/docs/latest/ml-commons-plugin/remote-models/guardrails/) or word lists to filter inappropriate text generation that could be produced by integrated LLMs. ### Apply aggregations to hybrid search results -[Hybrid search](https://opensearch.org/docs/latest/search-plugins/hybrid-search/) combines results from lexical and neural search, providing more relevant results than either one separately. OpenSearch now offers the ability to [post-filter](https://opensearch.org/docs/latest/search-plugins/hybrid-search/#combining-hybrid-search-and-aggregations/) the combined results and to apply aggregations to them to support use cases such as faceting. +[Hybrid search](https://opensearch.org/docs/latest/search-plugins/hybrid-search/) combines results from lexical and neural search, providing more relevant results than either one separately. OpenSearch now offers the ability to [post-filter](https://opensearch.org/docs/latest/search-plugins/hybrid-search/#combining-hybrid-search-and-aggregations) the combined results and to apply aggregations to them to support use cases such as faceting. ### Query and manage external data sources more efficiently OpenSearch community members looking to optimize costs can find themselves storing infrequently queried data outside of OpenSearch in object stores. In the 2.9 release, we introduced data sources, which allow you to create a new Apache Spark data source type to directly query object stores. For those who wanted to [increase query performance](https://opensearch.org/docs/latest/dashboards/management/accelerate-external-data/), we released skipping indexes (in the 2.9 release) to speed up direct queries as well as materialized views and covering indexes (both in the 2.11 release) to ingest data directly into OpenSearch indexes. In the 2.13 release, we’ve added a new skipping index type, [Bloom filter](https://opensearch.org/docs/latest/install-and-configure/configuring-opensearch/index-settings/), which is more efficient for data types like IP addresses and hostnames that have many different values that can be stored. In addition, we’ve made improvements to the [data sources experience](https://opensearch.org/docs/latest/dashboards/management/multi-data-sources/), where community members can now manage tables and accelerations visually instead of using SQL statements in [Query Workbench](https://opensearch.org/docs/latest/dashboards/query-workbench/). In upcoming releases, we will improve the querying experience as we merge observability logs functionality into [Discover](https://opensearch.org/docs/latest/dashboards/discover/index-discover/).