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

[Serverless]: Clarify Serverless and Stateful clients compatibility with Serverless and non-Serverless environments #80

Closed
ppf2 opened this issue Oct 18, 2024 · 2 comments · Fixed by #198
Assignees
Labels
Serverless bug bash 🐛 Issues discovered during the Serverless UX bug bash

Comments

@ppf2
Copy link
Member

ppf2 commented Oct 18, 2024

Serverless Docs

Elasticsearch

Description

Let's clarify Serverless clients vs. non-Serverless clients: https://www.elastic.co/docs/current/serverless/elasticsearch/clients

We have seen confusion by multiple customers while reviewing Serverless cases where they are attempting to use Serverless clients against non-Serverless deployments and vice versa.

In short, our current stance is:

  • Serverless client will only work on Serverless
  • Non-Serverless (Stateful) clients may work on Serverless but there will be a lag in the release to support Serverless features. Also some feature gap like autocomplete are not supported when used with Serverless. @technige can provide additional details.

It will be helpful to put up banners for each language client's documentation page on both Serverless and Stateful clients documentation so that regardless of whether the customer lands in Serverless clients documentation or Stateful clients documentation, they will see a disclaimer about these clients' compatibility with Serverless and non-Serverless environments.

Resources and additional context

https://www.elastic.co/docs/current/serverless/elasticsearch/clients
https://www.elastic.co/guide/en/elasticsearch/client/index.html

@KOTungseth KOTungseth added the Serverless bug bash 🐛 Issues discovered during the Serverless UX bug bash label Oct 29, 2024
@marciw
Copy link
Contributor

marciw commented Nov 14, 2024

@marciw
Copy link
Contributor

marciw commented Dec 13, 2024

I temporarily reopened this because I thought I needed to track the Part 2 work in this issue, but we'll do that in the other issue. Closing again.

@marciw marciw closed this as completed Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Serverless bug bash 🐛 Issues discovered during the Serverless UX bug bash
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants