Highlights
Cumulative rewards support is now available in indexer! This is complicated to calculate, and requires a non-blocking migration to implement (see upgrade notes below).
Upgrade Notes (Please Read)
Mandatory Migration
Adding cumulative rewards support requires a migration. However, this was written to run asynchronously and will not require downtime. There is minimal impact to query performance while running, but the migration is expected to take around five days to complete. The server can be restarted at any time, and the migration will pick up where it left off. You can observe if the migration has finished by checking the /health REST API endpoint. The percent progress is available in the log file or from standard out if no log file is configured.
Configuration File Name Change
If you were previously using a configuration file with indexer, you will need to rename it. If you had previously been using a file named algorand-indexer, algorand-indexer.yml, or algorand-indexer.yaml, you should rename this file to indexer, indexer.yml, or indexer.yaml. The location of the configuration file has not changed.
Changes
New Features
- Add support for cumulative rewards (#166)
- Capture create and close rounds for things that can be created and closed
Enhancements
- Switch to algod v2 client
- Degrade ReadOnly Node Service When Migration is Required
- IndexerDb should block importer until db is available
- Logging Improvements
- Naming cleanup and append to log file instead of overwriting
- remove support for e2etest.py and use e2elive.py
- Pipeline - add mule build docs
- Pipeline - parameterize STAGING in build task
- Added github templates for internal ticketing
Bug Fixes
- Config file name change
- Fix golint
- Fixing typo in README.md postgress connection string (thanks PSJoe)
- Make sure GetMaxRound returns a value if there are no rounds processed