[BUG] Invalid JSON API schema after update #11251
Assignees
Labels
component/json-api
HTTP JSON API
needs-backport
Candidate fix for backporting to the latest release branch
team/ledger-clients
Related to the Ledger Clients team's components.
Milestone
Comments
stefanobaghino-da
added
component/json-api
stefanobaghino-da
added a commit
that referenced
this issue
Oct 14, 2021
Closes #11251 Schema changed as part of #11102 Also backported to 1.17.1 in #11143 changelog_begin [JSON API] Solving a bug that could cause the JSON API to return correct result if a contract with the same key is observed twice required a schema change. The JSON API data needs to be dropped and the query store needs to reset. If you are migrating from a previous version, either reset your database manually or start the HTTP JSON API with one of the options that regenerate the schema (`create-only`, `create-if-needed-and-start`, `create-and-start`). changelog_end
7 tasks
stefanobaghino-da
added a commit
that referenced
this issue
Oct 15, 2021
Closes #11251 Schema changed as part of #11102 Also backported to 1.17.1 in #11143 changelog_begin [JSON API] Solving a bug that could cause the JSON API to return correct result if a contract with the same key is observed twice required a schema change. The JSON API data needs to be dropped and the query store needs to reset. If you are migrating from a previous version, either reset your database manually or start the HTTP JSON API with one of the options that regenerate the schema (`create-only`, `create-if-needed-and-start`, `create-and-start`). changelog_end
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I confirm that, if this is a bug that has security implications, I already contacted [email protected] and followed the responsible disclosure policy.
I confirm that this is not a question or a request for technical support by the community, for which the Daml forum is available.
Affected Daml version(s)
1.17.1 and 1.18 snapshot
Bug description
The schema is not correctly validated after a change as part of the transition from 1.17.x to 1.18.x
To reproduce
Start from a fresh database on 1.17.0, shut down, restart without creating the schema on 1.18 snapshot. The issue originally fixed by #11102 will still occur.
Expected behavior
Enter here a clear and concise description of what you expected to happen.
Workaround
The JSON API query store can be safely dropped and we can restart.
Additional context
Original fix: #11102
Backport to 1.17.1: #11143
The text was updated successfully, but these errors were encountered: