-
Notifications
You must be signed in to change notification settings - Fork 499
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
Karthik/5438/deprecate horizon fields for protocol 22 #5478
Karthik/5438/deprecate horizon fields for protocol 22 #5478
Conversation
As a part of this cleanup/deprecation task, I think the fields in Db structure
|
Yes, you're correct. You will need to add a new migration which removes the |
.../horizon/internal/db2/schema/migrations/68_remove_deprecated_fields_from_exp_asset_stats.sql
Show resolved
Hide resolved
@tamirms |
Remove deprecated fields from horizon in protocol 22 release as a part of issue 5438 (https://github.com//issues/5438)
PR Structure
otherwise).
services/friendbot
, orall
ordoc
if the changes are broad or impact manypackages.
Thoroughness
.md
files, etc... affected by this change). Take a look in the
docs
folder for a given service,like this one.
Release planning
CHANGELOG.md
within the component folder structure. For example, if I changed horizon, then I updated (services/horizon/CHANGELOG.md. I add a new line item describing the change and reference to this PR. If I don't update a CHANGELOG, I acknowledge this PR's change may not be mentioned in future release notes.semver, or if it's mainly a patch change. The PR is targeted at the next
release branch if it's not a patch change.
What
They are
numAccounts
,amount
,validBefore
,validAfter
from theAssetStat
structure in services/horizon/protocols/main.gonum_accounts
andamount
columns are also dropped from theexp_asset_stat
tables and the DB bindings and code are removedThe PR that updates/removes the references for these deprecated fields from the stellar-docs is: stellar/stellar-docs#1014