Skip to content

Conversation

@prwhelan
Copy link
Member

"elser" is an alias for "elasticsearch", and "sagemaker" is an alias for "amazon_sagemaker".

Users can continue to create and use providers by their alias. Elasticsearch will continue to support the alias when it reads the configuration from the internal index.

"elser" is an alias for "elasticsearch", and "sagemaker" is an alias for
"amazon_sagemaker".

Users can continue to create and use providers by their alias.
Elasticsearch will continue to support the alias when it reads the
configuration from the internal index.
@prwhelan prwhelan added >enhancement :ml Machine learning Team:ML Meta label for the ML team auto-backport Automatically create backport pull requests when merged v8.19.0 v9.1.0 labels May 28, 2025
@elasticsearchmachine
Copy link
Collaborator

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

@prwhelan prwhelan marked this pull request as ready for review May 28, 2025 18:38
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/ml-core (Team:ML)

Copy link
Contributor

@jonathan-buttner jonathan-buttner left a comment

Choose a reason for hiding this comment

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

Looks great 🙌 I think there are a few places where we still use the name(). From what you've seen do you think it'll create confusion if a user did a PUT with amazon_bedrock but see amazonbedrock instead?

testSupportedStream("streaming_completion_test_service_alias");
}

public void testSupportedStream(String serviceName) throws Exception {
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 make this private and potentially static?

@prwhelan
Copy link
Member Author

prwhelan commented May 28, 2025

Looks great 🙌 I think there are a few places where we still use the name(). From what you've seen do you think it'll create confusion if a user did a PUT with amazon_bedrock but see amazonbedrock instead?

I don't think so, or at least I don't think I'd be confused by that. GET will return amazon_sagemaker if the user did a PUT with amazonsagemaker or sagemaker, but I'm kinda fine with that? And that's what we've been doing with "elser" -> "elasticsearch"

@prwhelan prwhelan enabled auto-merge (squash) May 28, 2025 19:27
@prwhelan prwhelan merged commit 86cef7f into elastic:main May 28, 2025
16 of 18 checks passed
prwhelan added a commit to prwhelan/elasticsearch that referenced this pull request May 28, 2025
"elser" is an alias for "elasticsearch", and "sagemaker" is an alias for
"amazon_sagemaker".

Users can continue to create and use providers by their alias.
Elasticsearch will continue to support the alias when it reads the
configuration from the internal index.
@elasticsearchmachine
Copy link
Collaborator

💚 Backport successful

Status Branch Result
8.19

elasticsearchmachine pushed a commit that referenced this pull request May 28, 2025
"elser" is an alias for "elasticsearch", and "sagemaker" is an alias for
"amazon_sagemaker".

Users can continue to create and use providers by their alias.
Elasticsearch will continue to support the alias when it reads the
configuration from the internal index.
Samiul-TheSoccerFan pushed a commit to Samiul-TheSoccerFan/elasticsearch that referenced this pull request Jun 5, 2025
"elser" is an alias for "elasticsearch", and "sagemaker" is an alias for
"amazon_sagemaker".

Users can continue to create and use providers by their alias.
Elasticsearch will continue to support the alias when it reads the
configuration from the internal index.
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 >enhancement :ml Machine learning Team:ML Meta label for the ML team v8.19.0 v9.1.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants