Deprecate sorted indexing challenge in geonames #200
Merged
Conversation
This file contains 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
The sorted indexing challenge in the `geonames` track turns out to be unstable. As we have other options that are more reliable (such as `http_logs`) we deprecate this challenge for the `geonames` track.
|
The message will be shown whenever a user attempts to run a race, e.g.: Or, for testing this PR: checkout this PR and specify |
DJRickyB
approved these changes
Oct 11, 2021
| @@ -269,6 +269,7 @@ | |||
| { | |||
| "name": "append-sorted-no-conflicts", | |||
| "description": "Indexes the whole document corpus in an index sorted by country_code field in ascending order. Document ids are unique so all index operations are append only.", | |||
| "user-info": "This challenge is deprecated and will be removed soon. Use the corresponding challenge in http_logs to benchmark sorted indices.", | |||
There was a problem hiding this comment.
TIL about user-info. Can we document it? Seems useful
There was a problem hiding this comment.
Sure: elastic/rally#1358
danielmitterdorfer
added a commit
to danielmitterdorfer/rally
that referenced
this pull request
Oct 12, 2021
With this commit we document the existing property `user-info` on the challenge object. Relates elastic/rally-tracks#200
danielmitterdorfer
added a commit
that referenced
this pull request
Oct 12, 2021
The sorted indexing challenge in the `geonames` track turns out to be unstable. As we have other options that are more reliable (such as `http_logs`) we deprecate this challenge for the `geonames` track.
danielmitterdorfer
added a commit
that referenced
this pull request
Oct 12, 2021
The sorted indexing challenge in the `geonames` track turns out to be unstable. As we have other options that are more reliable (such as `http_logs`) we deprecate this challenge for the `geonames` track.
danielmitterdorfer
added a commit
that referenced
this pull request
Oct 12, 2021
The sorted indexing challenge in the `geonames` track turns out to be unstable. As we have other options that are more reliable (such as `http_logs`) we deprecate this challenge for the `geonames` track.
danielmitterdorfer
added a commit
that referenced
this pull request
Oct 12, 2021
The sorted indexing challenge in the `geonames` track turns out to be unstable. As we have other options that are more reliable (such as `http_logs`) we deprecate this challenge for the `geonames` track.
danielmitterdorfer
added a commit
that referenced
this pull request
Oct 12, 2021
The sorted indexing challenge in the `geonames` track turns out to be unstable. As we have other options that are more reliable (such as `http_logs`) we deprecate this challenge for the `geonames` track.
danielmitterdorfer
added a commit
that referenced
this pull request
Oct 12, 2021
The sorted indexing challenge in the `geonames` track turns out to be unstable. As we have other options that are more reliable (such as `http_logs`) we deprecate this challenge for the `geonames` track.
danielmitterdorfer
added a commit
to elastic/rally
that referenced
this pull request
Oct 12, 2021
With this commit we document the existing property `user-info` on the challenge object. Relates elastic/rally-tracks#200
uparamonau-es
added a commit
to uparamonau-es/rally-tracks
that referenced
this pull request
Nov 11, 2021
In elastic#200 we agreed to deprecate sorted indexing challenge in geonames, and in elastic#202 we scheduled its removal after grace period.
uparamonau-es
added a commit
to uparamonau-es/rally-tracks
that referenced
this pull request
Nov 11, 2021
In elastic#200 we agreed to deprecate sorted indexing challenge in geonames, and in elastic#202 we scheduled its removal after grace period.
uparamonau-es
added a commit
to uparamonau-es/rally-tracks
that referenced
this pull request
Nov 11, 2021
In elastic#200 we agreed to deprecate sorted indexing challenge in geonames, and in elastic#202 we scheduled its removal after grace period.
uparamonau-es
added a commit
to uparamonau-es/rally-tracks
that referenced
this pull request
Nov 11, 2021
In elastic#200 we agreed to deprecate sorted indexing challenge in geonames, and in elastic#202 we scheduled its removal after grace period.
uparamonau-es
added a commit
to uparamonau-es/rally-tracks
that referenced
this pull request
Nov 11, 2021
In elastic#200 we agreed to deprecate sorted indexing challenge in geonames, and in elastic#202 we scheduled its removal after grace period.
uparamonau-es
added a commit
that referenced
this pull request
Nov 15, 2021
Sign up for free
to 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.
The sorted indexing challenge in the
geonamestrack turns out to beunstable. As we have other options that are more reliable (such as
http_logs) we deprecate this challenge for thegeonamestrack.