Draft: (Reptracker integration) Integrate reputation_tracker with hivemind
Requires: reputation_tracker!11 (merged) (added option to change if app is forking and attached on setup)
Changes:
- Added reputation_tracker as a submodule and integrated with hivemind sync,
- Removed reputation and is_implicit columns from hive_accounts, hive_reputation_data table removed,
- Adjusted hive_accounts_view to supplement data from reputation_tracker:
- join on context.accounts_view (convert_haf_id is not enough in certain scenarios like in CI - mock data moves some accounts in hive_accounts and there is a slightly bigger slip between hive.accounts and hive_accounts)
- context is specified in this view, I think it can stay that way untill the python server gets completly replaced by postgrest and this issue with hivemind not supporting custom schema will be resolved,
- Adjust test (condenser, bridge, tags api):
- blocktrades pattern changed to
"author_reputation": 69.12
(from"author_reputation": 68.63
) - previous value was incorrect (tested and compared with reputation from reputation_api.get_account_reputations) - additional
"reblogs": 0
in response (I think it should be there?) - order changed to
"reblogs": 0,"replies": []
(from"replies": [],"reblogs": 0
) (I think it doesn't matter) - in condenser api most tests return list of accounts with their reputations so there is much more changes
- the same in tags_api - only reputation changes
-
join_collapse_limit
from 1 to 6 - improves performance of joining reptracker's tables
Edited by Michal Zander