Collector complains about "Could not dynamically add mapping for field [http.connection.id]"

[mviitane]

Bug Report

Which version of the demo you are using?

Using main latest:
$ git log
commit e3548c6 (HEAD -> main, upstream/main)
Date: Sun Dec 22 08:49:02 2024 -0500

Symptom

Collector batchprocessor and opensearch exporter complains about
Could not dynamically add mapping for field [http.connection.id]
Existing mapping for [attributes.http] must be of type object but found [text]

otel-collector  | 2024-12-23T12:40:13.035Z	warn	[email protected]/batch_processor.go:263	Sender failed	{"kind": "processor", "name": "batch", "pipeline": "logs", "error": "not retryable error: Permanent error: {\"type\":\"mapper_parsing_exception\",\"reason\":\"Could not dynamically add mapping for field [http.connection.id]. Existing mapping for [attributes.http] must be of type object but found [text].\",\"caused_by\":
...
otel-collector  | 2024-12-23T12:40:13.449Z	error	internal/base_exporter.go:139	Exporting failed. Rejecting data.	{"kind": "exporter", "data_type": "logs", "name": "opensearch", "error": "not retryable error: Permanent error: {\"type\":\"mapper_parsing_exception\",\"reason\":\"Could not dynamically add mapping for field [http.connection.id]. Existing mapping for [attributes.http] must be of type object but found [text].\",\"caused_by\":
...

What is the expected behavior?

No complains.

Reproduce

Could you provide the minimum required steps to resolve the issue you're seeing?

docker compose build
docker compose run
docker compose logs otel-collector

Workaround

Disable logs pipeline in the Collector.

Additional context

Related to #1833

However, this occurs with standard demo components without enabling any vendor backends.

[mviitane]

This seems to be related to the envoy access logs and #1768