-
Notifications
You must be signed in to change notification settings - Fork 271
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
Can not deploy v3 using pg sql as backend when there are v2 tables in the database but different schema #5620
Comments
Thank you for reporting an issue! Pinging @jsenko to respond or triage. |
Yeah that's not great. On startup registry tries to examine the database to see if the tables already exist. It does this by checking for the existence of the As you say, we're clearly checking at the database level, not the schema level. Marked as blocker for 3.0.6. |
With that PR you can optionally set the name of your schema (only necessary if you have two schemas both with apicurio registry tables). That should result in the |
The new property is |
Merged, hopefully you can try it out when we release 3.0.6, which I will try to do asap (probably next week). |
Bonus points if you test it out using the |
Thanks for the quick fix! |
Description
Registry
Version: 3.0.4
Persistence type: postgresql
Before we use apicurio 2.x.x version. Now we want to migrate to 3.x.x
Now in our postgres database there is a database called
database1
for apicurio.And apicurio 2.x.x uses schema called
schema1
indatabase1
Now we want to apicurio 3.x.x can use a new created schema called
schema2
and still indatabase1
But when I update to 3.x.x, the apicurio will always show following error:
After I delete the old
schema1
, it will work fine.So I suspect the apicurio is scanning the whole database1 to see if there are some v2 tables instead of scanning in schema level.
Environment
kind v0.20.0 go1.21.1 darwin/arm64
This is a deploy issue not interaction
Steps to Reproduce
Expected vs Actual Behaviour
Expected behaviour is: when we Deploy apicurio 3.x.x with database1 and schema2 by update the jdbc URL to use
schema2
, it will success even there are some v2 tables in theschema1
in the same database.Logs
See the before section
The text was updated successfully, but these errors were encountered: