Elasticsearch indexer for osu_scores*_high #1
Conversation
notbakaneko
force-pushed the
notbakaneko:feature/elastic-index
branch
from
9df5b28
to
e829e5a
notbakaneko
force-pushed the
notbakaneko:feature/elastic-index
branch
from
0436509
to
312c4d9
Issue when no prefix is used.
I thought I removed that?
notbakaneko
force-pushed the
notbakaneko:feature/elastic-index
branch
from
186dc17
to
e508cb3
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.
Indexes the contents of the
osu_scores*_hightables into elasticsearch.It turns out it's significantly faster and less resource intensive to have a separate program in C# perform the index population instead of running it though osu-web.
The main use for this, initially, is for osu-web to be able to run aggregation queries for the user's high score data though elasticsearch. Eventually, we should probably look at moving all the index population over?
There's still a bunch of stuff to do like