Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Existing schema cannot be edited after upgrade to 0.7 #575

Closed
bgoerlitzHDP opened this issue Jul 24, 2019 · 0 comments · Fixed by #580
Closed

Existing schema cannot be edited after upgrade to 0.7 #575

bgoerlitzHDP opened this issue Jul 24, 2019 · 0 comments · Fixed by #580
Assignees
@raju-saravanan

Comments

@bgoerlitzHDP
Copy link

0.7 added schema metadata locking which requires an entry for each schema in the SCHEMA_LOCK table. Records for existing schema are not added to this table during migration. Edit attempts fail to acquire a lock after a time out.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@raju-saravanan raju-saravanan

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

ISSUE 575 : Add migration to enable editing of schema post upgrade to 0.7 raju-saravanan/registry
2 participants
@bgoerlitzHDP @raju-saravanan