Releases: appbaseio/reactivesearch-api
Releases · appbaseio/reactivesearch-api
1.0.23
Changes in this release:
- Adds support for suprressing all pipeline unmarshal errors with
marklogicQuery
so that it doesn't add noise to the logs output. - Adds a fix regarding pipeline rollover making the entire app crash
1.0.22
Changes in this release:
- Includes changes for rollover configurations for
.logs
,.analytics
index. - Includes support for rollover index for
.pipeline_logs
. - Other fixes
1.0.21
Changes in this release:
- Includes all changes from
dev
in SLS - Includes support for caching with Redis
- Fixes some issues with concurrent map writes
- Other bug fixes and enhancements
8.20.0
Enhancements
- Add support for configuring an external Redis compatible cache, API endpoint ref
Minor Fixes
- Moves extra logs from
info
category todebug
- Use stricter check for rs routes by adding a / prefix
- Wait for indexing completion after adding FAQ
8.20.0 Alpha
Enhancements
- Add support for configuring an external Redis compatible cache, API endpoint ref
Minor Fixes
- Moves extra logs from
info
category todebug
- Use stricter check for rs routes by adding a / prefix
- Wait for indexing completion after adding FAQ
8.19.0
Enhancements
- Build architecture change: Binary and Docker size is ~8x smaller, shifts base image to Go 1.21.3 which includes an important security fix related to net/http
- Supports
filter_path
query string for filtering of responses from Elasticsearch and OpenSearch for search calls. This can enable reducing the returned response's size outside of source filtering, which is supported withincludeFields
(andexcludeFields
) - New API endpoint to filter FAQs by a
searchboxId
Fixes
- Fixes an edge-case with syncing of popular suggestions in a multi-node setup
- Fixes an edge-case with suggestions API call when either of endpoint or index suggestions are enabled
- Fixes filtering of pipeline logs by category
- Fixes time taken reporting in pipeline analytics
- Fixes caching behavior with pipelines to return valid JSON
- Include URL params as part of the cache key
8.19.0.rc
Enhancements
- Build architecture change: Binary and Docker size is ~8x smaller, shifts base image to Go 1.21.3 which includes an important security fix related to net/http
- Supports
filter_path
query string for filtering of responses from Elasticsearch and OpenSearch for search calls. This can enable reducing the returned response's size outside of source filtering, which is supported withincludeFields
(andexcludeFields
)
Fixes
- Fixes an edge-case with syncing of popular suggestions in a multi-node setup
- Fixes an edge-case with suggestions API call when either of endpoint or index suggestions are enabled
- Fixes filtering of pipeline logs by category
- Fixes time taken reporting in pipeline analytics
- Fixes caching behavior with pipelines to return valid JSON
- Include URL params as part of the cache key
1.0.20
- Add support for injecting the
searchNetworkTook
in settings.
1.0.19
Changes in this release:
- Adds a fix to decrease the startup time of SLS
- Adds a fix for concurrent writes to a map
- Other bug fixes
8.18.0
Enhancements
This release adds several enhancements to ReactiveSearch pipelines.
- Key/value store support for pipelines, when caching is enabled, you can use key/value store to read/write to the cache.
This allows for new use-cases where data can be stored and retrieved across stages or even across pipeline executions
- Increases stage execution limit to
30s
and pipeline execution limit to1m
to support ML inference use-cases
Previous limits were
10s
for the pipeline execution, you can run 6x more complex / computation heavy processes now
- Support for
async
type stages that aren't needed by other stages to be run in the background after the pipeline has exited
For indexing pipelines, this allows for data enrichment to happen asynchronously and for search pipelines, this allows for doing post-processing or side-effect registrations without affecting the main-runtime latency
Fixes
- Fixes usage of document suggestions query when
settings.userId
isn't specified