Move cross-cluster search docs to explore and analyze #4256
Uh oh!
There was an error while loading. Please reload this page.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Contributor
Contributor
Vale Linting ResultsSummary: 6 warnings, 76 suggestions found
|
| File | Line | Rule | Message |
|---|---|---|---|
| explore-analyze/cross-cluster-search.md | 111 | Elastic.DontUse | Don't use 'Note that'. |
| explore-analyze/cross-cluster-search.md | 492 | Elastic.DontUse | Don't use 'Thus'. |
| explore-analyze/cross-cluster-search.md | 824 | Elastic.DontUse | Don't use 'and/or'. |
| explore-analyze/cross-cluster-search.md | 966 | Elastic.DontUse | Don't use 'and/or'. |
| explore-analyze/cross-cluster-search.md | 1000 | Elastic.Latinisms | Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'. |
| explore-analyze/cross-cluster-search.md | 1039 | Elastic.DontUse | Don't use 'Note that'. |
💡 Suggestions (76)
| File | Line | Rule | Message |
|---|---|---|---|
| deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md | 190 | Elastic.FutureTense | 'will remove' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md | 201 | Elastic.FutureTense | 'will remove' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/cross-cluster-search.md | 26 | Elastic.WordChoice | Consider using 'run, start' instead of 'execute', unless the term is in the UI. |
| explore-analyze/cross-cluster-search.md | 36 | Elastic.WordChoice | Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI. |
| explore-analyze/cross-cluster-search.md | 52 | Elastic.Capitalization | 'examples' should use sentence-style capitalization. |
| explore-analyze/cross-cluster-search.md | 88 | Elastic.WordChoice | Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'See', unless the term is in the UI. |
| explore-analyze/cross-cluster-search.md | 176 | Elastic.FutureTense | 'will show' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/cross-cluster-search.md | 406 | Elastic.FutureTense | 'will be' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/cross-cluster-search.md | 406 | Elastic.FutureTense | 'will be' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/cross-cluster-search.md | 410 | Elastic.FutureTense | 'will see' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/cross-cluster-search.md | 410 | Elastic.WordChoice | Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI. |
| explore-analyze/cross-cluster-search.md | 412 | Elastic.FutureTense | 'will also' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/cross-cluster-search.md | 412 | Elastic.WordChoice | Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI. |
| explore-analyze/cross-cluster-search.md | 414 | Elastic.FutureTense | 'will also' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/cross-cluster-search.md | 414 | Elastic.WordChoice | Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI. |
| explore-analyze/cross-cluster-search.md | 414 | Elastic.WordChoice | Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI. |
| explore-analyze/cross-cluster-search.md | 491 | Elastic.Wordiness | Consider using 'because' instead of 'Since'. |
| explore-analyze/cross-cluster-search.md | 491 | Elastic.FutureTense | 'will be' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/cross-cluster-search.md | 495 | Elastic.FutureTense | 'will show' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/cross-cluster-search.md | 585 | Elastic.Capitalization | 'failures' should use sentence-style capitalization. |
| explore-analyze/cross-cluster-search.md | 592 | Elastic.FutureTense | 'will be' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/cross-cluster-search.md | 594 | Elastic.FutureTense | 'will be' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/cross-cluster-search.md | 594 | Elastic.FutureTense | 'will result' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/cross-cluster-search.md | 596 | Elastic.FutureTense | 'will be' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/cross-cluster-search.md | 598 | Elastic.FutureTense | 'will have' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/cross-cluster-search.md | 712 | Elastic.Wordiness | Consider using 'because' instead of 'since'. |
| explore-analyze/cross-cluster-search.md | 720 | Elastic.Wordiness | Consider using 'because' instead of 'Since'. |
| explore-analyze/cross-cluster-search.md | 814 | Elastic.FutureTense | 'will often' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/cross-cluster-search.md | 814 | Elastic.Wordiness | Consider using 'because' instead of 'since'. |
| explore-analyze/cross-cluster-search.md | 815 | Elastic.Wordiness | Consider using 'because' instead of 'Since'. |
| explore-analyze/cross-cluster-search.md | 815 | Elastic.FutureTense | 'will not' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/cross-cluster-search.md | 817 | Elastic.Wordiness | Consider using 'because' instead of 'since'. |
| explore-analyze/cross-cluster-search.md | 826 | Elastic.FutureTense | 'will be' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/cross-cluster-search.md | 846 | Elastic.WordChoice | Consider using 'efficient' instead of 'simple', unless the term is in the UI. |
| explore-analyze/cross-cluster-search.md | 865 | Elastic.FirstPerson | Avoid first-person pronouns such as 'my'. |
| explore-analyze/cross-cluster-search.md | 875 | Elastic.FutureTense | 'will be' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/cross-cluster-search.md | 876 | Elastic.FutureTense | 'will be' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/cross-cluster-search.md | 876 | Elastic.FutureTense | 'will be' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/cross-cluster-search.md | 877 | Elastic.Wordiness | Consider using 'all' instead of 'all of '. |
| explore-analyze/cross-cluster-search.md | 877 | Elastic.Wordiness | Consider using 'because' instead of 'since'. |
| explore-analyze/cross-cluster-search.md | 893 | Elastic.WordChoice | Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI. |
| explore-analyze/cross-cluster-search.md | 967 | Elastic.WordChoice | Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI. |
| explore-analyze/cross-cluster-search.md | 983 | Elastic.FutureTense | 'will show' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/cross-cluster-search.md | 985 | Elastic.WordChoice | Consider using 'can, might' instead of 'may', unless the term is in the UI. |
| explore-analyze/cross-cluster-search.md | 1002 | Elastic.FutureTense | 'will be' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/cross-cluster-search.md | 1004 | Elastic.FutureTense | 'will be' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/cross-cluster-search.md | 1004 | Elastic.FutureTense | 'will return' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/cross-cluster-search.md | 1004 | Elastic.FutureTense | 'will be' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/cross-cluster-search.md | 1018 | Elastic.WordChoice | Consider using 'can, might' instead of 'may', unless the term is in the UI. |
| explore-analyze/cross-cluster-search.md | 1038 | Elastic.Wordiness | Consider using 'many' instead of 'a large number of'. |
| explore-analyze/cross-cluster-search.md | 1039 | Elastic.FutureTense | 'will provide' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/cross-cluster-search.md | 1068 | Elastic.Capitalization | 'Don’t minimize network roundtrips' should use sentence-style capitalization. |
| explore-analyze/cross-cluster-search.md | 1080 | Elastic.FutureTense | 'will be' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/cross-cluster-search.md | 1087 | Elastic.WordChoice | Consider using 'can, might' instead of 'may', unless the term is in the UI. |
| explore-analyze/cross-cluster-search.md | 1122 | Elastic.Wordiness | Consider using 'before' instead of 'prior to'. |
| explore-analyze/cross-cluster-search.md | 1122 | Elastic.Wordiness | Consider using 'before' instead of 'prior to'. |
| explore-analyze/cross-cluster-search.md | 1125 | Elastic.FutureTense | 'will result' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/cross-cluster-search.md | 1127 | Elastic.WordChoice | Consider using 'can, might' instead of 'may', unless the term is in the UI. |
| explore-analyze/cross-cluster-search.md | 1138 | Elastic.Capitalization | 'during an upgrade' should use sentence-style capitalization. |
| explore-analyze/cross-cluster-search.md | 1147 | Elastic.WordChoice | Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI. |
| explore-analyze/cross-cluster-search/using-resolve-cluster-endpoint-before-cross-cluster-search.md | 15 | Elastic.WordChoice | Consider using 'can, might' instead of 'may', unless the term is in the UI. |
| explore-analyze/cross-cluster-search/using-resolve-cluster-endpoint-before-cross-cluster-search.md | 17 | Elastic.FutureTense | 'will cause' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/cross-cluster-search/using-resolve-cluster-endpoint-before-cross-cluster-search.md | 18 | Elastic.FutureTense | 'will return' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/cross-cluster-search/using-resolve-cluster-endpoint-before-cross-cluster-search.md | 19 | Elastic.FutureTense | 'will be' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/cross-cluster-search/using-resolve-cluster-endpoint-before-cross-cluster-search.md | 19 | Elastic.FutureTense | 'will be' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/cross-cluster-search/using-resolve-cluster-endpoint-before-cross-cluster-search.md | 20 | Elastic.Versions | Use 'earlier version' instead of 'older version' when referring to versions. |
| explore-analyze/cross-cluster-search/using-resolve-cluster-endpoint-before-cross-cluster-search.md | 78 | Elastic.FutureTense | 'will wait' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/cross-cluster-search/using-resolve-cluster-endpoint-before-cross-cluster-search.md | 119 | Elastic.FutureTense | 'will return' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/cross-cluster-search/using-resolve-cluster-endpoint-before-cross-cluster-search.md | 120 | Elastic.WordChoice | Consider using 'can, might' instead of 'may', unless the term is in the UI. |
| explore-analyze/cross-cluster-search/using-resolve-cluster-endpoint-before-cross-cluster-search.md | 121 | Elastic.Wordiness | Consider using 'because' instead of 'Since'. |
| explore-analyze/cross-cluster-search/using-resolve-cluster-endpoint-before-cross-cluster-search.md | 123 | Elastic.WordChoice | Consider using 'can, might' instead of 'may', unless the term is in the UI. |
| explore-analyze/query-filter/languages/eql.md | 1251 | Elastic.Wordiness | Consider using 'before' instead of 'prior to'. |
| explore-analyze/query-filter/languages/eql.md | 1251 | Elastic.Wordiness | Consider using 'before' instead of 'prior to'. |
| reference/glossary/index.md | 163 | Elastic.WordChoice | Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'See', unless the term is in the UI. |
| solutions/search/vector/knn.md | 1179 | Elastic.Acronyms | 'HNSW' has no definition. |
| solutions/search/vector/knn.md | 1179 | Elastic.Acronyms | 'HNSW' has no definition. |
florent-leborgne approved these changes Dec 10, 2025
Contributor
florent-leborgne left a comment
florent-leborgne left a comment There was a problem hiding this comment.
Move and placement LGTM as previously discussed. Will you update the codeowner file too?
georgewallace approved these changes Dec 15, 2025
shainaraskas merged commit 27c8dc9 into main 7 of 8 checks passed
Uh oh!
There was an error while loading. Please reload this page.
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixeshttps://github.com/elastic/docs-content-internal/issues/481
The CCS feature is a platform primitive, not unique to the search solution. I am moving it so it is more visible to people who need to use it for non-search use cases.
Related issue https://github.com/elastic/docs-content-internal/issues/507 (not sure if this is the only thing that needs to move - it's the only thing we identified so far).
Note on placement
You can consider this to be a temporary location - we need to do some further exploration about how to get explanations about search-related platform primitives into the right spot in the docs, but this unblocks us from creating the cross-project search docs as a sibling in a non-hidden spot.
For reviewers
Most of the files that were changed here are just link updates to reflect the relocation of the file. Sorry for the many many groups being notified here.
Either @elastic/developer-docs or @elastic/admin-docs can review the core "move" (nothing really to see here)
Generative AI disclosure