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

Gateway: Store cluster meta data in JSON (and not binary) #36

Closed
kimchy opened this issue Feb 22, 2010 · 1 comment
Closed

Gateway: Store cluster meta data in JSON (and not binary) #36

kimchy opened this issue Feb 22, 2010 · 1 comment

Comments

@kimchy
Copy link
Member

kimchy commented Feb 22, 2010

Makes things much easier to debug, tinker with, and support for backward compatibility. Sadly, this will break backward compatibility.

@kimchy
Copy link
Member Author

kimchy commented Feb 22, 2010

Gateway: Store cluster meta data in JSON (and not binary), closed by 67d86de.

dadoonet added a commit that referenced this issue Jun 5, 2015
Closes #36.

(cherry picked from commit f2c83df)
johtani added a commit that referenced this issue Jun 5, 2015
rmuir pushed a commit to rmuir/elasticsearch that referenced this issue Nov 8, 2015
ywelsch added a commit to ywelsch/elasticsearch that referenced this issue May 24, 2018
Adds node leaving based on a simplified MasterService abstraction
ClaudioMFreitas pushed a commit to ClaudioMFreitas/elasticsearch-1 that referenced this issue Nov 12, 2019
For  elastic#36 - Add support for creating optional elasticsearch user and group
henningandersen pushed a commit to henningandersen/elasticsearch that referenced this issue Jun 4, 2020
With this commit we remove the custom runner `createindex` which creates
index templates, matching indices and also aliases and replace it with
runners that are available out of the box with Rally. Furthermore, we
cleanup some duplication and have removed the challenge
`append-no-conflicts` which acted as a dummy default challenge but does
not serve any other purpose.

Relates elastic#36
henningandersen pushed a commit to henningandersen/elasticsearch that referenced this issue Jun 4, 2020
With this commit we use the correct property `index` in the
`bulk-update` challenge instead of the outdated property name
`index_name`. This is a leftover from elastic#36

Relates elastic#44
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant