Skip to content

Conversation

rjernst
Copy link
Member

@rjernst rjernst commented Sep 10, 2025

In serverless new transport versions are based on the greater of the largest serverless transport version, or the largest in server. This commit adds configuration to the generate task which allows specifying the upper bound file from server to consult when generating a new transport version.

In serverless new transport versions are based on the greater of the
largest serverless transport version, or the largest in server. This
commit adds configuration to the generate task which allows specifying
the upper bound file from server to consule when generating a new
transport version.
@rjernst rjernst requested a review from a team as a code owner September 10, 2025 03:19
@rjernst rjernst added :Core/Infra/Core Core issues without another label auto-backport Automatically create backport pull requests when merged v8.19.5 v9.1.5 v8.18.8 v9.0.8 labels Sep 10, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra (Team:Core/Infra)

@elasticsearchmachine elasticsearchmachine added Team:Core/Infra Meta label for core/infra team v9.2.0 labels Sep 10, 2025
@rjernst rjernst requested a review from mark-vieira September 10, 2025 03:31
@elasticsearchmachine elasticsearchmachine added the serverless-linked Added by automation, don't add manually label Sep 10, 2025
Copy link
Contributor

@mark-vieira mark-vieira left a comment

Choose a reason for hiding this comment

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

one small nit, otherwise LGTM.

if (getAlternateUpperBoundFile().isPresent()) {
Path altUpperBoundPath = getAlternateUpperBoundFile().get().getAsFile().toPath();
String contents = Files.readString(altUpperBoundPath, StandardCharsets.UTF_8);
var altUpperBound = TransportVersionUpperBound.fromString(altUpperBoundPath, contents);
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: can we agree on when we do and don't use var. I just find it really odd to mix explicit type declarations and var on literally consecutive lines of code.

Copy link
Member Author

Choose a reason for hiding this comment

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

My rule of thumb is I only use it in these cases:

  • if the type is obvious, eg the rhs has new or is an obvious factory method like here
  • if the line is incredibly long because of generic types

@rjernst rjernst merged commit 280bae5 into elastic:main Sep 11, 2025
35 checks passed
@rjernst rjernst deleted the transport/alternate_upper_bound branch September 11, 2025 14:13
rjernst added a commit to rjernst/elasticsearch that referenced this pull request Sep 11, 2025
In serverless new transport versions are based on the greater of the
largest serverless transport version, or the largest in server. This
commit adds configuration to the generate task which allows specifying
the upper bound file from server to consule when generating a new
transport version.
rjernst added a commit to rjernst/elasticsearch that referenced this pull request Sep 11, 2025
In serverless new transport versions are based on the greater of the
largest serverless transport version, or the largest in server. This
commit adds configuration to the generate task which allows specifying
the upper bound file from server to consule when generating a new
transport version.
@elasticsearchmachine
Copy link
Collaborator

💔 Backport failed

Status Branch Result
8.19
9.1 Commit could not be cherrypicked due to conflicts
8.18
9.0

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

rjernst added a commit to rjernst/elasticsearch that referenced this pull request Sep 11, 2025
In serverless new transport versions are based on the greater of the
largest serverless transport version, or the largest in server. This
commit adds configuration to the generate task which allows specifying
the upper bound file from server to consule when generating a new
transport version.
elasticsearchmachine pushed a commit that referenced this pull request Sep 11, 2025
)

In serverless new transport versions are based on the greater of the
largest serverless transport version, or the largest in server. This
commit adds configuration to the generate task which allows specifying
the upper bound file from server to consule when generating a new
transport version.
elasticsearchmachine pushed a commit that referenced this pull request Sep 11, 2025
)

In serverless new transport versions are based on the greater of the
largest serverless transport version, or the largest in server. This
commit adds configuration to the generate task which allows specifying
the upper bound file from server to consule when generating a new
transport version.
elasticsearchmachine pushed a commit that referenced this pull request Sep 11, 2025
)

In serverless new transport versions are based on the greater of the
largest serverless transport version, or the largest in server. This
commit adds configuration to the generate task which allows specifying
the upper bound file from server to consule when generating a new
transport version.
sarog pushed a commit to portsbuild/elasticsearch that referenced this pull request Sep 11, 2025
elastic#134548)

In serverless new transport versions are based on the greater of the
largest serverless transport version, or the largest in server. This
commit adds configuration to the generate task which allows specifying
the upper bound file from server to consule when generating a new
transport version.
rjernst added a commit to rjernst/elasticsearch that referenced this pull request Sep 12, 2025
In serverless new transport versions are based on the greater of the
largest serverless transport version, or the largest in server. This
commit adds configuration to the generate task which allows specifying
the upper bound file from server to consule when generating a new
transport version.
elasticsearchmachine pushed a commit that referenced this pull request Sep 12, 2025
)

In serverless new transport versions are based on the greater of the
largest serverless transport version, or the largest in server. This
commit adds configuration to the generate task which allows specifying
the upper bound file from server to consule when generating a new
transport version.
sarog pushed a commit to portsbuild/elasticsearch that referenced this pull request Sep 19, 2025
elastic#134548)

In serverless new transport versions are based on the greater of the
largest serverless transport version, or the largest in server. This
commit adds configuration to the generate task which allows specifying
the upper bound file from server to consule when generating a new
transport version.
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 :Core/Infra/Core Core issues without another label >non-issue serverless-linked Added by automation, don't add manually Team:Core/Infra Meta label for core/infra team v8.18.8 v8.19.5 v9.0.8 v9.1.5 v9.2.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants