v0.31.0 #1847
steven-sheehy
started this conversation in
Releases
v0.31.0
#1847
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
After scheduled transactions was made available in previewnet, we listened to user feedback and further iterated on the design to make it easier to use. This release adds support for this revised scheduled transactions design planned to be released in HAPI v0.13. There was no impact to our REST API format, only the importer needed to be updated to parse and ingest the new proto format. Our monitor API and acceptance tests will be adjusted in the next release once the SDKs add support for the new design.
This release also adds support for the newly announced account balance file format that was released in HAPI v0.12. The new protobuf based format will eventually replace the CSV format in July 2021. Until then, both formats will exist simultaneously in the bucket so users can transition at their leisure. Besides being more efficient to parse, the new files are also compressed using Gzip for reduced storage and download costs. We also took the time to improve the balance file parsing performance regardless of format. Average parse times should decrease by about 27%.
For our REST API, we now expose an
entity_idfield on our transactions related APIs. This field represents that main entity associated with that transaction type. For example, if it was a HCS transaction it would be the topic ID created, updated, or deleted.GET /api/v1/transactions/0.0.1009-1234567890-999999998{ "transactions": [{ "consensus_timestamp": "1234567890.999999999", "entity_id": "0.0.108763", "valid_start_timestamp": "1234567890.999999998", "charged_tx_fee": 0, "memo_base64": null, "result": "SUCCESS", "scheduled": false, "transaction_hash": "aGFzaA==", "name": "CRYPTOUPDATEACCOUNT", "node": "0.0.3", "transaction_id": "0.0.1009-1234567890-999999998", "valid_duration_seconds": "11", "max_fee": "33", "transfers": [] }] }We continue to make progress towards our goal of switching to TimescaleDB. We fixed the user and database initialization issues and tested a migration from PostgreSQL. We switched out the TimescaleDB Helm chart to a more stable one and explored our hosting options for production. Finally we switched to SCRAM-SHA-256 to improve the security of our database user authentication.
Breaking changes:
There were a number of breaking changes this release to be aware of. If you're using our Helm chart, we have switched the importer from a
StatefulSetto aDeploymentsince it no longer has the need for a persistent volume. We also switched the Traefik dependency from aDeploymentto aDaemonSet. Both of these will require manual intervention to delete the old workload before upgrading. Support for Helm 2 was dropped since it is no longer supported by the community after November 13, 2020. If you're directly reading from our database, a rename of thet_entitiestable and its columns may impact you as well.Enhancements
Bug Fixes
Dependency Upgrades
@hashgraph/proto from 1.0.22 to 1.0.23 in /hedera-mirror-rest/check-state-proof #1776@hashgraph/proto from 1.0.22 to 1.0.23 in /hedera-mirror-rest #1769@hashgraph/proto from 1.0.21 to 1.0.22 in /hedera-mirror-rest #1753@godaddy/terminus from 4.6.0 to 4.7.1 in /hedera-mirror-rest #1748@hashgraph/proto from 1.0.21 to 1.0.22 in /hedera-mirror-rest/check-state-proof #1735Contributors
We'd like to thank all the contributors who worked on this release!
This discussion was created from the release v0.31.0.
Beta Was this translation helpful? Give feedback.
All reactions