iotaledger / iota / 26549227281

67%

Build Type

push

github

Committed by web-flow

Commit Message

refactor(iota-indexer): support filtered queries on transactions with a fallback to the archival store (#11656)

# Description of change

This PR adds support for pruned transactions to be retrieved form the
fallback archival store in the `IndexerApi::query_transaction_blocks`.

Included the `signal` feature flag to `tokio` dependency needed for the
graceful shutdown.


## Links to any relevant issues

fixes #9498 

## How the change has been tested

- [x] Basic tests (linting, compilation, formatting, unit/integration
tests)
- [ ] Patch-specific tests (correctness, functionality coverage)

The fix was verified by manually simulating a pruned state and
confirming the API successfully fetches missing data from the fallback
store.

1. Started a local network using the `iota-localnet` cli tool
```shell
cargo r -- -p iota-localnet -- start --force-regenesis --with-grpc
```
2. Start the kv-store ingestion task to write checkpoints into BigTable
(see the README in the `iota-kvstore` crate for details):
```shell
cargo r -p iota-data-ingestion --bin iota-data-ingestion -- bigtable.yaml
```
3. Start the kv-store REST API
```shell
cargo -p iota-rest-kv r -- --config bigtable.yaml
```
4. Start the indexer writer:
```shell
cargo r -p iota-indexer -- --database-url=postgres://postgres:postgrespw@localhost:5432/iota_indexer indexer --remote-store-url=http://localhost:50051 --reset-db
```
5. Start the indexer reader with the fallback KV URL configured:
```shell
 cargo r -p iota-indexer -- --database-url=postgres://postgres:postgrespw@localhost:5432/iota_indexer --metrics-address=0.0.0.0:9185 json-rpc-service --rpc-client-url=http://localhost:50051 --fallback-kv-url=http://localhost:3555 --rpc-address=0.0.0.0:9001
```

Once the database had ingested some transactions, we picked a starting
point for the test queries. We listed checkpoints:

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "iota_getCheckpoints",
  "params": [
    "10",
    4,
    false
  ]
}
```
an... (continued)

Coverage Stats

0 of 60 new or added lines in 1 file covered. (0.0%)

871 existing lines in 45 files now uncovered.

152186 of 227566 relevant lines covered (66.88%)

464328.89 hits per line