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

Docs: some glossary terms #31390

Closed
PhaedrusTheGreek opened this issue Jun 18, 2018 · 5 comments
Closed

Docs: some glossary terms #31390

PhaedrusTheGreek opened this issue Jun 18, 2018 · 5 comments
Assignees
Labels
:Data Management/Indices APIs APIs to create and manage indices and templates >docs General docs changes

Comments

@PhaedrusTheGreek
Copy link
Contributor

Some missing terminology:

merge - This term is used to describe the merging of Lucene segments in automatic background merging, or in a force merge.

reindex - To cycle through some or all documents in one or more indices, re-writing them into the same or new index in a local or remote cluster. This is most commonly done to update mappings, or to upgrade Elasticsearch between two incompatible index versions.

shrink - To reduce the amount of shards in an index. See the Shrink Index API

split - To grow the amount of shards in an index. See the Split Index API.

@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-docs

@colings86 colings86 added >docs General docs changes :Data Management/Indices APIs APIs to create and manage indices and templates and removed :Docs labels Jun 19, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra

@Sue-Gallagher Sue-Gallagher self-assigned this Jun 19, 2018
@Sue-Gallagher
Copy link
Contributor

Questions:

  1. It's never a good idea to use a word to define itself. Can we say:
    merge - The combining of Lucene segments, either automatically in the background or initiated using force merge.
  2. You said:
    "...all documents in one or more indices, re-writing them into the same or new index..."
    We spend a lot of electrons telling our users that an index is immutable, so how does rewriting index data back into itself work?

@PhaedrusTheGreek
Copy link
Contributor Author

  1. Sounds better, yes
  2. An in-place re-index is actually an simple _update_by_query, which is a shared code base with the reindex API - although it is one of those esoteric things. We could always add another sentence: "Reindexing to the same index is known as an Update By Query"

@Sue-Gallagher
Copy link
Contributor

Fixed. See PR #66.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Data Management/Indices APIs APIs to create and manage indices and templates >docs General docs changes
Projects
None yet
Development

No branches or pull requests

4 participants