Cloud-native search engine for observability. An open-source alternative to Datadog, Elasticsearch, Loki, and Tempo.
Full Changelog: https://github.com/quickwit-oss/quickwit/compare/v0.8.0...v0.8.1
/{index}/_stats
and /_stats
ES API (#4442)search_after
in ES scroll API (#4280).
support in DSL indentifiers (#3989)_bulk
requests (#4506)/
character in field names (#4510)start_timestamp
and end_timestamp
filter to ES _field_caps
API (#4547)_source_excludes
and _source_includes
query parameters in ES API (#4572)/indexes
endpoint (#4600)IN
instead of many OR
(#4670)_source_excludes
, _source_includes
, extra_filters
in _msearch
ES API (#4696)track_total_size
on request ES body (#4710)More details in tantivy's changelog.
_field_caps
API (#4492)source
in ES parameter, remove unsupported field fields
in response (#4590)split_size
parameter, add docs and test (#4627)gs://
(#4344)otel-logs-v0_7
(#4401)Quickwit 0.7.1 will create the new index otel-logs-v0_7 which is now used by default when ingesting data with the OTEL gRPC and HTTP API.
In the traces index otel-traces-v0_7, the service_name
field is now fast. No migration is done if otel-traces-v0_7 already exists. If you want service_name
field to be fast, you have to delete first the existing otel-traces-v0_7 index or you need to create your own index.
Beta release of Quicwkit Lambdas.
_field_caps
APIauto.offset.reset
parameter in Kafka source (#4095)coerce
and output_format
options for numeric fields (#3704)PhraseMatchQuery
and MultiMatchQuery
(#3727)TermsQuery
(#3747)source_code_default
, source_code
, multilang
(#3647, #3655, #3608)More details in tantivy's changelog.
Improve OTEL traces index config (#4311)
otel-logs-v0_7
and otel-traces-v0_7
instead of otel-logs-v0_6
and otel-traces-v0_6
Increased the gRPC payload limits from 10MiB to 20MiB (#4227)
Reject malformed Elasticsearch API requests (#4175)
Better logging when doc processing fails (#4323)
Search performance improvements
Indexing performance improvements
The format of the index and internal objects stored in the metastore of 0.7 is backward compatible with 0.6.
If you are using the OTEL indexes and ingesting data into indexes the otel-logs-v0_6
and otel-traces-v0_6
, you must stop indexing before upgrading.
Indeed, the first time you start Quickwit 0.7, it will update the doc mapping fields of Trace ID and Span ID of those two indexes by changing their input/output formats from base64 to hex. This is automatic: you don't have to perform any manual operation.
Quickwit 0.7 will create new indexes otel-logs-v0_7
and otel-traces-v0_7
, which are now used by default when ingesting data with the OTEL gRPC and HTTP API. The Jaeger gRPC and HTTP APIs will query both otel-traces-v0_6
and otel-traces-v0_7
by default.
It's possible to define the index ID you want to use for OTEL gRPC endpoints and Jaeger gRPC API by setting the request header qw-otel-logs-index
or qw-otel-traces-index
to the index ID you want to target.