Skip to content
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

Optimized index sorting for OTel logs #119504

Merged
merged 5 commits into from
Jan 8, 2025

Conversation

@felixbarny felixbarny added >enhancement :Data Management/Data streams Data streams and their lifecycles auto-backport Automatically create backport pull requests when merged v9.0.0 v8.18.0 labels Jan 3, 2025
@felixbarny felixbarny requested a review from kkrik-es January 3, 2025 12:34
@felixbarny felixbarny requested a review from a team as a code owner January 3, 2025 12:34
@elasticsearchmachine elasticsearchmachine added Team:Data Management Meta label for data/management team external-contributor Pull request authored by a developer outside the Elasticsearch team labels Jan 3, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-data-management (Team:Data Management)

@elasticsearchmachine
Copy link
Collaborator

Hi @felixbarny, I've created a changelog YAML for you.

…IT.testLogsAtSettingWithTimeSeriesOverride

I don't really get why you would want to set index.mode: time_series in logs@custom but these sort settings aren't compatible with tsdb
Copy link
Member

@martijnvg martijnvg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor comment LGTM otherwise.

pr: 119504
summary: Optimized index sorting for OTel logs
area: Data streams
type: enhancement
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe this is a bug?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, I didn't think of this as a bug. Is it because we're sorting the timestamp in ascending order right now? What's the consequence of that from a user's perspective?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe certain queries that filter on timestamp will now slightly perform better. But that isn't a really a bug, so let's leave this as an enhancement.

@felixbarny felixbarny merged commit afda404 into elastic:main Jan 8, 2025
16 checks passed
felixbarny added a commit to felixbarny/elasticsearch that referenced this pull request Jan 8, 2025
felixbarny added a commit to felixbarny/elasticsearch that referenced this pull request Jan 8, 2025
@felixbarny
Copy link
Member Author

💚 All backports created successfully

Status Branch Result
8.x

Questions ?

Please refer to the Backport tool documentation

elasticsearchmachine pushed a commit that referenced this pull request Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-backport Automatically create backport pull requests when merged :Data Management/Data streams Data streams and their lifecycles >enhancement external-contributor Pull request authored by a developer outside the Elasticsearch team Team:Data Management Meta label for data/management team v8.18.0 v9.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants