graphprotocol / graphprotocol/indexer
Perf: Add index to database to help calculating unaggregated fees in tap-agent
Open
Nobody has claimed this yet.
p1
perf
TAP
- Dominant language
- TypeScript
- Stars
- 262
- Forks
- 148
- PR merge metrics
- No merged PRs in 30d
Description
CREATE INDEX idx_scalar_tap_receipts_allocation_signer_timestamp_cast
ON scalar_tap_receipts ((allocation_id::text), (signer_address::text), timestamp_ns);
CREATE INDEX idx_scalar_tap_invalid_receipts_allocation_signer_cast
ON scalar_tap_invalid_receipts ((allocation_id::text), (signer_address::text));
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the database migration or schema entry points for scalar_tap_receipts and scalar_tap_invalid_receipts, then inspect how existing indexes are defined. Add the two specified indexes and verify that the resulting schema contains them for the unaggregated-fee query path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100