Skip to content

AGG.IND :: Pools Historical Data Latest record management refactoring #75

@mckrava

Description

@mckrava

In table processor_status there are following properties:

  • aavepool_hist_data_latest_block
  • omnipool_hist_data_latest_block
  • stableswap_hist_data_latest_block
    These markers are used for queries related with TVL metrics. But this approach must be refactored and implemented by the same way as in Xykpools TVL query - based on latest value table.

Problem:
Approach with single value of latest processed block in processor_status works well when indexer doesn't dedupe historical data and indexer aggregates hist date for all pools/assets each block. But if dedupe logic is involved, historical data table contains only data which are changed. So at latest indexer block DB won't contain hist data for all pools/assets, but only for that which are changed at this block.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions