Skip to content

[DOCS] Document how reindex work in CPS#144016

Merged
szabosteve merged 15 commits intomainfrom
szabosteve/cps-reindex
Mar 26, 2026
Merged

[DOCS] Document how reindex work in CPS#144016
szabosteve merged 15 commits intomainfrom
szabosteve/cps-reindex

Conversation

@szabosteve
Copy link
Copy Markdown
Contributor

Overivew

Relates to https://github.com/elastic/docs-content-internal/issues/31
This PR documents how reindexing works in CPS.

@szabosteve szabosteve requested a review from quux00 March 11, 2026 12:56
@szabosteve szabosteve added >docs General docs changes :Docs/Dev Docs team for PDC:Search concepts (search, analytics, timeseries, ML, dev tools) and removed v9.4.0 labels Mar 11, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Mar 11, 2026

Vale Linting Results

Summary: 3 suggestions found

💡 Suggestions (3)
File Line Rule Message
docs/reference/elasticsearch/rest-apis/reindex-indices.md 790 Elastic.Wordiness Consider using 'impossible' instead of 'not possible'.
docs/reference/elasticsearch/rest-apis/reindex-indices.md 799 Elastic.Wordiness Consider using 'all' instead of 'all of '.
docs/reference/elasticsearch/rest-apis/reindex-indices.md 837 Elastic.Wordiness Consider using 'all' instead of 'all of '.

The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Mar 11, 2026

🔍 Preview links for changed docs

@github-actions
Copy link
Copy Markdown
Contributor

ℹ️ Important: Docs version tagging

👋 Thanks for updating the docs! Just a friendly reminder that our docs are now cumulative. This means all 9.x versions are documented on the same page and published off of the main branch, instead of creating separate pages for each minor version.

We use applies_to tags to mark version-specific features and changes.

Expand for a quick overview

When to use applies_to tags:

✅ At the page level to indicate which products/deployments the content applies to (mandatory)
✅ When features change state (e.g. preview, ga) in a specific version
✅ When availability differs across deployments and environments

What NOT to do:

❌ Don't remove or replace information that applies to an older version
❌ Don't add new information that applies to a specific version without an applies_to tag
❌ Don't forget that applies_to tags can be used at the page, section, and inline level

🤔 Need help?

Copy link
Copy Markdown
Contributor

@quux00 quux00 left a comment

Choose a reason for hiding this comment

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

A few suggestions for changes.

Copy link
Copy Markdown
Member

@ywangd ywangd left a comment

Choose a reason for hiding this comment

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

I left a couple comments

@szabosteve szabosteve requested review from quux00 and ywangd March 12, 2026 14:42
@szabosteve szabosteve marked this pull request as ready for review March 12, 2026 14:42
@szabosteve szabosteve requested review from a team as code owners March 12, 2026 14:42
@elasticsearchmachine
Copy link
Copy Markdown
Collaborator

Pinging @elastic/developer-docs (:Docs/Dev)

Copy link
Copy Markdown
Member

@ywangd ywangd left a comment

Choose a reason for hiding this comment

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

LGTM with one comment

@naj-h naj-h requested review from naj-h and pete-naylor March 13, 2026 15:39
Copy link
Copy Markdown
Member

@PeteGillinElastic PeteGillinElastic left a comment

Choose a reason for hiding this comment

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

Thanks for this. I left a few comments/suggestions/questions. Nothing major.

@szabosteve
Copy link
Copy Markdown
Contributor Author

Thank you for your review and suggestions, @PeteGillinElastic! I addressed them in my latest commit, except the one about the examples. You are right that they are very similar, but I'd keep both for self-contained reading. Let me know if you disagree or if I missed anything. Thank you in advance!

Copy link
Copy Markdown
Contributor

@kosabogi kosabogi left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Copy Markdown

@pete-naylor pete-naylor left a comment

Choose a reason for hiding this comment

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

Thank you!

Copy link
Copy Markdown
Contributor

@quux00 quux00 left a comment

Choose a reason for hiding this comment

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

Two change suggestions left. After those, I can approve.

@szabosteve szabosteve requested a review from quux00 March 19, 2026 08:10
Copy link
Copy Markdown
Member

@PeteGillinElastic PeteGillinElastic left a comment

Choose a reason for hiding this comment

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

Belatedly getting back to this... Thanks for your response to my last round of comments. I have one more optional nit, otherwise I'm happy when everyone else is happy.

Copy link
Copy Markdown
Contributor

@quux00 quux00 left a comment

Choose a reason for hiding this comment

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

LGTM

@szabosteve szabosteve requested a review from n1v0lg March 20, 2026 14:52
Copy link
Copy Markdown
Contributor

@shainaraskas shainaraskas left a comment

Choose a reason for hiding this comment

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

looks good to me.

should this content be surfaced in this section?

https://www.elastic.co/docs/manage-data/migrate

see this PR for the future structure

elastic/docs-content#5244

@szabosteve szabosteve merged commit 11d03ab into main Mar 26, 2026
14 checks passed
@szabosteve szabosteve deleted the szabosteve/cps-reindex branch March 26, 2026 08:41
szybia added a commit to szybia/elasticsearch that referenced this pull request Mar 26, 2026
* upstream/main: (146 commits)
  Revert "[Native] Gradle-related tweaks to improve handling of the simdvec native library (elastic#144539)"
  Fix ArrayIndexOutOfBoundsException in fetch phase with partial results (elastic#144385)
  ESQL: Correctly manage NULL data type for SUM (elastic#144942)
  [ESQL] Fixes GroupedTopNBenchmark not executing (elastic#144944)
  Fix reader context leak when query response serialization fails (elastic#144708)
  Validate individual offset values in BULK_OFFSETS bounds checks (elastic#144643)
  Merge main21 source set into main in simdvec (elastic#144921)
  [TEST] Unmute TsidExtractingIdFieldMapperTests (elastic#144848)
  [Native] Gradle-related tweaks to improve handling of the simdvec native library (elastic#144539)
  Fix `ThreadedActionListenerTests#testRejectionHandling` (elastic#144795)
  Add new DLM Frozen Tier Transition execution plugin and service (elastic#144595)
  Prometheus: execute query_range via parsed EsqlStatement plan (elastic#144416)
  Investigate `testBulkIndexingRequestSplitting` failure (elastic#144766)
  Add test utility for wrapping directories in FilterDirectory layer (elastic#143563)
  Fix ES|QL decay tests with negative scale (elastic#144657)
  Fix circuit breaker leak in percolator query construction (elastic#144827)
  Use XPerFieldDocValuesFormat in AbstractTSDBSyntheticIdCodec (elastic#144744)
  [DOCS] Document how reindex work in CPS (elastic#144016)
  Fix Int4 vector library tests failing on Java 21 (elastic#144830)
  [DiskBBQ] Fix index sorting on flush (elastic#144938)
  ...
seanzatzdev pushed a commit to seanzatzdev/elasticsearch that referenced this pull request Mar 26, 2026
* [CPS] Document how reindex work in CPS.

* Add CPS subs.

* More edits.

* Addresses feedback.

* Address feedback.

* Refine content.

* Address feedback.

* More edits.

* Address feedback.

* Clarify authentication.
seanzatzdev pushed a commit to seanzatzdev/elasticsearch that referenced this pull request Mar 27, 2026
* [CPS] Document how reindex work in CPS.

* Add CPS subs.

* More edits.

* Addresses feedback.

* Address feedback.

* Refine content.

* Address feedback.

* More edits.

* Address feedback.

* Clarify authentication.
mamazzol pushed a commit to mamazzol/elasticsearch that referenced this pull request Mar 30, 2026
* [CPS] Document how reindex work in CPS.

* Add CPS subs.

* More edits.

* Addresses feedback.

* Address feedback.

* Refine content.

* Address feedback.

* More edits.

* Address feedback.

* Clarify authentication.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

:Docs/Dev Docs team for PDC:Search concepts (search, analytics, timeseries, ML, dev tools) >docs General docs changes v9.4.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.