Salvatore Campagna

LogsDB - Indexing overhead performance testing of `ignore_malformed`

2

### Description LogsDB uses stored fields under the hood to deal with malformed field values and as a fallback mechanism in situations where doc values are not available. This behaviour...

LogsDB - Third-party Integration Testing

1

### Description As part of the effort to test integration of LogsDB we would like to run third-party integration testing. When it comes to integrations, customers are allowed to override...

Store original source for keywords using a normalizer

2

Using a normalizer for a keyword field might result in not being able to reconstruct the original source when using synthetic source. Here, if synthetic source is enabled and a...

LogsDB - Ignore dimension fields

1

### Description Multiple field types support the `dimension` boolean parameter after the introduction of TSDB (dimensions used for routing purposes). There are integrations sharing component and composable templates and creating...

Re-arrange document id bytes to take advantage of shared prefixes

12

Here we change the auto generated document id structure so to favour compression of the Lucene terms dictionary used to store document ids. The idea is to generate the document...

Default LogsDB value for `ignore_dynamic_beyond_limit`

4

This is a backport of #115265

Default LogsDB value for `ignore_dynamic_beyond_limit`

19

When ingesting logs, it's important to ensure that documents are not dropped due to mapping issues, also when dealing with dynamically mapped fields. Elasticsearch provides two key settings that help...

Change `cluster.logsdb.enabled` default value to `true`

1

### Description After releasing LogsDB we need to make the default value of `cluster.logsdb.enabled` to be `true` for non-stateful deployments by means of an override.