jaegertracing/jaeger · error

indices.%s.rotation: data_stream is not yet implemented

Error message

indices.%s.rotation: data_stream is not yet implemented

What it means

The data_stream rotation strategy is a placeholder that is not implemented in the current Elasticsearch client. If indices.<type>.rotation.data_stream is set (even alone), validate rejects it so users get a clear message instead of broken runtime behavior.

Source

Thrown at internal/storage/elasticsearch/config/config_rotation.go:164

		count++
	}
	if r.ManualRollover.HasValue() {
		count++
	}
	if r.AutoRollover.HasValue() {
		count++
	}
	if r.DataStream.HasValue() {
		count++
	}
	if count > 1 {
		return fmt.Errorf(
			"indices.%s.rotation: exactly one rotation strategy must be set, found %d",
			indexType, count,
		)
	}
	if r.DataStream.HasValue() {
		return fmt.Errorf(
			"indices.%s.rotation: data_stream is not yet implemented",
			indexType,
		)
	}
	return nil
}

View on GitHub (pinned to 806f444784)

Solutions

1. Remove the data_stream entry from the rotation section
2. Use rotation.periodic instead for time-based rotation
3. Wait for/track Jaeger support for data streams before adopting

Example fix

// before
rotation:
  data_stream: {}
// after
rotation:
  periodic:
    days: 1

if r.DataStream.HasValue() {
    return errors.New("data_stream rotation is not supported in this Jaeger version; use periodic")
}

When it happens

Trigger: Setting indices.<type>.rotation.data_stream in the config and calling validate (via Validate); also reached after passing the exactly-one-strategy check.

Common situations: Following Elasticsearch data-stream documentation or a roadmap feature and assuming Jaeger already supports it.

Related errors

• cannot use both 'rotation' config and legacy flags (%s) simu
• indices.%s: cannot use both 'rotation' config and legacy 'da
• indices.%s.rotation: exactly one rotation strategy must be s
• unrecognized write_mode %q: valid values are %q and %q
• unrecognized log_level %q: valid values are debug, info, err

AI-assisted analysis of jaegertracing/jaeger@806f444784 (2026-09-01). Data as JSON: /api/errors/0e5e4f3e7767942c. Report an issue: GitHub.