-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add configurable cl audits table #94
Conversation
Good call. I agree that this should be configurable since it's quite storage intensive. We'll merge our endpoint, too. It's experimental at the moment but if it's controlled via config I think it makes sense to include as an optional endpoint. |
515ff53
to
642c98c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM but left a question.
@@ -75,6 +90,12 @@ where | |||
txn.execute(query) | |||
.await | |||
.map_err(|db_err| IngesterError::StorageWriteError(db_err.to_string()))?; | |||
|
|||
|
|||
// Insert the audit item after the insert into cl_items have been completed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wouldn't you want insert to the audit table before inserting to cl_items
, so that if the insert to cl_items
fails, it remains in the audit table and is audited and fixed later?
This adds the cl_audits table which contains all the transactions for a specific compressed asset. This has some quite heavy increased data usage, so I have added a configuration param for this.
I think helius-labs have used this same table for a new rpc call they added so getting this merged in would help upstream those changes too later.