Releases: near/read-rpc
Releases · near/read-rpc
v0.3.1
Supported Nearcore Version
- nearcore v2.3.0
- rust v1.81.0
What's Changed
- Improved bulk insertion of state_changes, reducing database requests from hundreds to a maximum of 7 per block.
- Configuration improvement. Create default config.toml on start application to loaded parameters from the environment variables.
- Fix to fetch state by pages (view_state_paginated).
- Change logic to get
shard_layout
for indexers. Main idea to avoid requestprotocol_config
via RPC,protocol_config
could be changed with new nearcore release and we should support old and new versions ofprotocol_config
.
0.3.0
BREAKING CHANGES
Please, see the PostgreSQL & ShardLayout Pull Request for details. This is a completely new version of the ReadRPC with a new data storage layout and a new data storage engine. The main changes are:
- Migrate from ScyllaDB to PostgreSQL for storing the data. We adopted the ShardLayout from the
nearcore
and split the data to separate PostgreSQL databases for each shard. - Changed the way we store
TransactionDetails
(JSON blobs again, but it might change soon)
All the work in this release allowed us to increase the performance of the ReadRPC and make it more reliable. We are still working on the performance improvements and will continue to work on the ReadRPC to make it even better.
Supported Nearcore Version (not changed)
- nearcore v2.2.1
- rust v1.79.0
v0.2.16
v0.2.15
v0.2.14
v0.2.12.1
v0.2.13
v0.2.12
v0.2.11
Supported Nearcore Version
- nearcore v1.40.0
- rust v1.77.0
What's Changed
- Change main data source for
transaction_details
from database to the object storage (GCS Bucket)- Add
tx-details-storage
library to handle the GCS communication - Update
rpc-server
to read from the GCS Bucket when transaction is requested - Keep the database as a backup data source for the migration period
- Add metric
legacy_database_tx_details
to track the number of requests to the database to monitor the transition progress (expected to decrease over time to zero) - Extend the number of save attempts to ensure the transaction is saved to the GCS Bucket and is deserializable correctly
- Add
- Refactor
tx-indexer
to store the transaction details in the GCS Bucket- Still storing
ExecutionOutcome
andReceipt
in the database
- Still storing