Skip to content

[exporter/elasticsearch] Add support for resource attributes dynamically controlling the mapping mode #38667

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

felixbarny
Copy link
Contributor

No description provided.

Copy link
Contributor

github-actions bot commented Apr 1, 2025

This PR was marked stale due to lack of activity. It will be closed in 14 days.

@felixbarny
Copy link
Contributor Author

Superseded by #39110

@github-actions github-actions bot removed the Stale label Apr 3, 2025
Copy link
Contributor

This PR was marked stale due to lack of activity. It will be closed in 14 days.

@github-actions github-actions bot added the Stale label Apr 18, 2025
andrzej-stencel pushed a commit that referenced this pull request Apr 23, 2025
#### Description

Add support for specifying the mapping mode as a scope attribute,
"elastic.mapping.mode". If specified, this overrides both
X-Elastic-Mapping-Mode from client metadata as well as the default mode
specified through collector configuration.

Simplify StartSession by removing the error result, since the only time
it can fail is if the BulkIndexerConfig is invalid, and we ensure that
cannot happen. We now also pre-create arrays of encoders, routers, and
data point hashers; this simplifies and speeds up acquisition of these
during execution.

This is based on
#38667

#### Link to tracking issue

N/A

#### Testing

Added unit tests.

#### Documentation

Updated README.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant