Skip to content

Commit

Permalink
Update CHANGELOG.md
Browse files Browse the repository at this point in the history
Fixed `StoryOnlyForUserTransactionsAndEpochChanges`
  • Loading branch information
dhedey authored Nov 18, 2024
1 parent 66ecf82 commit a5561f1
Showing 1 changed file with 3 additions and 2 deletions.
5 changes: 3 additions & 2 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -67,10 +67,11 @@ Release built: 23.10.2024
>
### What’s new?
- New configuration options `DataAggregator__Storage__StoreTransactionReceiptEvents`, and `DataAggregator__Storage__StoreReceiptStateUpdates` for the data aggregator to configure if a transaction's receipt events and receipt state updates should be stored in the database. It is meant to be used by gateway runners who want to reduce their database size. Keep in mind that when disabled, the corresponding properties will be missing on a response from both the `/stream/transactions` and the `/transaction/committed-details` endpoints. You can save significant space by using `StoreOnlyForUserTransactionsAndEpochChanges` and only excluding round change transactions, which aren't typically read from the `/stream/transactions` endpoint.
- New configuration options `DataAggregator__Storage__StoreTransactionReceiptEvents`, and `DataAggregator__Storage__StoreReceiptStateUpdates` for the data aggregator to configure if a transaction's receipt events and receipt state updates should be stored in the database. It is meant to be used by gateway runners who want to reduce their database size. Keep in mind that when disabled, the corresponding properties will be missing on a response from both the `/stream/transactions` and the `/transaction/committed-details` endpoints. You can save significant space by using `StoryOnlyForUserTransactionsAndEpochChanges` and only excluding round change transactions, which aren't typically read from the `/stream/transactions` endpoint.
- Possible values:
- `StoreForAllTransactions` (default) - will store data for all transactions.
- `StoreOnlyForUserTransactionsAndEpochChanges` - will store data for user transactions and transactions that resulted in epoch change.
- `StoryOnlyForUserTransactionsAndEpochChanges` - will store data for user transactions and transactions that resulted in epoch change.
- NOTE: The configuration option is spelt incorrectly. Please use the prefix `Story`. In a future version, this will be fixed, and both `Story` and `Store` will be accepted, for backwards-compatibility.
- `StoreOnlyForUserTransactions` - will store data only for user transactions.
- `DoNotStore` - will not store any data.

Expand Down

0 comments on commit a5561f1

Please sign in to comment.