-
Notifications
You must be signed in to change notification settings - Fork 315
Added starting items to /matches endpoint #2254
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
Conversation
processors/processLogParse.js
Outdated
| function processReduce(entries, meta) { | ||
| const result = entries.filter((e) => { | ||
| if (e.type === 'DOTA_COMBATLOG_PURCHASE' | ||
| if (e.type === 'DOTA_COMBATLOG_PURCHASE' || e.type === 'STARTING_ITEM' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can leave this out, we don't need this in the pro game logs.
|
This looks generally fine, but we might want to optimize how we store this data, as we'd be storing this x10 players for each match and storage is already the most expensive part of running the service. |
|
This will need a rebase if it still should be merged, and the processor code is now in odota/parser. If possible I'd also like to see an example of how this looks/changes the parser blob output so we can estimate the storage impact |
|
I'm not sure this is necessary anymore. It is currently possible to get a players starting items by checking the players purchase_log and the purchase time <= 0. |
odota/parser#42