Skip to content

Conversation

@rjernst
Copy link
Member

@rjernst rjernst commented Feb 26, 2025

No description provided.

@rjernst rjernst added >non-issue :Delivery/Build Build or test infrastructure auto-backport Automatically create backport pull requests when merged v9.0.0 v8.18.0 v8.19.0 labels Feb 26, 2025
@rjernst rjernst requested a review from a team as a code owner February 26, 2025 06:24
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-delivery (Team:Delivery)

@elasticsearchmachine elasticsearchmachine added Team:Delivery Meta label for Delivery team v9.0.1 labels Feb 26, 2025
@rjernst
Copy link
Member Author

rjernst commented Mar 1, 2025

@elasticmachine update branch

elasticmachine and others added 2 commits March 1, 2025 14:41
All CLIs in elasticsearch support command line flags for controlling the
output level. When --silent is used, the expectation is that normal
logging is omitted. Yet the log4j logger is still configured to output
error level logs. This commit sets the appropriate log level for log4j
depending on the Terminal log level.
@rjernst rjernst requested a review from a team as a code owner March 2, 2025 16:56
@ChrisHegarty
Copy link
Contributor

@rjernst For JDK 24 make sure we’re setting the org.apache.lucene.vectorization.upperJavaFeatureVersion system property. Otherwise, we’re won’t use SIMD for vector search. See
https://lucene.apache.org/core/10_1_0/changes/Changes.html#v10.1.0.improvements

Until we get a Lucene 10.2.0!!

@rjernst
Copy link
Member Author

rjernst commented Mar 4, 2025

@ChrisHegarty I pushed 4dcba68 for enabling vectorization, let me know if this matches what we discussed.

Copy link
Contributor

@ChrisHegarty ChrisHegarty left a comment

Choose a reason for hiding this comment

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

LGTM

@rjernst rjernst enabled auto-merge (squash) March 4, 2025 17:06
@rjernst rjernst merged commit 1871e17 into elastic:9.0 Mar 4, 2025
16 checks passed
@elasticsearchmachine
Copy link
Collaborator

💔 Backport failed

Status Branch Result
8.18 Commit could not be cherrypicked due to conflicts
8.x Commit could not be cherrypicked due to conflicts

You can use sqren/backport to manually backport by running backport --upstream elastic/elasticsearch --pr 123452

@rjernst rjernst deleted the build/jdk24_rc_default branch March 5, 2025 01:08
rjernst added a commit to rjernst/elasticsearch that referenced this pull request Mar 5, 2025
rjernst added a commit to rjernst/elasticsearch that referenced this pull request Mar 5, 2025
elasticsearchmachine pushed a commit that referenced this pull request Mar 5, 2025
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
elasticsearchmachine pushed a commit that referenced this pull request Mar 6, 2025
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
rjernst added a commit to rjernst/elasticsearch that referenced this pull request Mar 6, 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 backport pending :Delivery/Build Build or test infrastructure >non-issue Team:Delivery Meta label for Delivery team v8.18.1 v8.19.0 v9.0.1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants