supervisor endpoint not respecting frontCoded indexSpec formatVersion

[ColeAtCharter]

Affected Version

29.0.1

Description

The druid/indexer/v1/supervisor endpoint is not respecting the frontCoded indexSpec formatVersion for a kafka tuningConfig.

Affected value in kafka ingest spec: $.spec.tuningConfig.indexSpec.stringDictionaryEncoding.formatVersion

Steps to reproduce:

1. update the supervisor spec by calling druid/indexer/v1/supervisor on the router with a valid kafka index spec which has an indexSpec like the following example:

{
          "bitmap": {
            "type": "roaring"
          },
          "dimensionCompression": "lz4",
          "metricCompression": "none",
          "longEncoding": "auto",
          "stringDictionaryEncoding": {
            "type": "frontCoded",
            "formatVersion": 1,
            "bucketSize": 8
          },
          "jsonCompression": "lz4"
}

2. Validate the running supervisor spec. Use the unified console to navigate to the supervisors page, and retrieve the kafka index spec that was sent in the prior step. The expected value should have the indexSpec specified in the prior step. The actual, observed behavior is that the indexSpec may not match. For example, the stringDictionaryEncoding formatVersion may be 0 instead of 1.

References

• https://druid.apache.org/docs/latest/ingestion/ingestion-spec/#front-coding