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

[8.15] [DOCS] Adds pre-cleaning recommendation to ELSER docs (backport #2796) #2799

Merged
merged 2 commits into from
Sep 19, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Sep 19, 2024

Overview

This PR adds a new section to the ELSER conceptual page that recommends cleaning the input text before generating embeddings to achieve the best results.

Preview

ELSER - Pre-cleaning input text


This is an automatic backport of pull request #2796 done by Mergify.

(cherry picked from commit 34a6c7b)

# Conflicts:
#	docs/en/stack/ml/nlp/ml-nlp-elser.asciidoc
@mergify mergify bot requested a review from a team as a code owner September 19, 2024 08:45
Copy link
Contributor Author

mergify bot commented Sep 19, 2024

Cherry-pick of 34a6c7b has failed:

On branch mergify/bp/8.15/pr-2796
Your branch is up to date with 'origin/8.15'.

You are currently cherry-picking commit 34a6c7b5.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   docs/en/stack/ml/nlp/ml-nlp-elser.asciidoc

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

Copy link

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

@szabosteve szabosteve merged commit 2f9aeb7 into 8.15 Sep 19, 2024
3 checks passed
@szabosteve szabosteve deleted the mergify/bp/8.15/pr-2796 branch September 19, 2024 11:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant