Hi team We have upgraded datahub to 0.10.5 but dat...
# all-things-deployment
c
Hi team We have upgraded datahub to 0.10.5 but datahub upgrade image is throwing error at datahub start step. We have pulled the docker image of 0.10.5 and doing testing
this 1
plus1 5
b
you are getting this error as well? https://github.com/acryldata/datahub-helm/issues/347
c
The same error I am getting while running upgrade Job
b
okay yeah experienced it yesterday but found no solution until now for this 😞
c
Same here I think it’s an open issue whosoever upgraded to 0.10.5
d
Hi, thanks for the report! we’ll get back to you shortly.
c
How you guys will fix this one whether you will going to drop new tag or update the older one ?
o
This error should only happen if you have configured Internal Schema Registry, if this is not intended then you can reconfigure the schema registry implementation to be Confluent Kafka: https://github.com/acryldata/datahub-helm/blob/master/charts/datahub/values.yaml#L491
It seems there are still issues with configuring Internal Schema Registry if you are intending to use it and the recommendation at this time is to still use Confluent Schema Registry if it is possible for your team until we can get this fixed
b
Thanks @orange-night-91387 for coming back with a workaround. Yes we intend to not use the CP schema registry but I guess we can wait until it is fixed to use the internal registry
c
But with 0.10.4 we have also configured internal schema and with that version we are not getting any error In 0.10.5 what basically causing this error?
r
Yup facing same issue. Is that resolved @dazzling-yak-93039 else plz notify on resolution
b
its not yet resolve (see github issue). Recommendation is to either switch to CP Schema Registry if you need the update or wait 🙂
r
I want to use Internal only. I have to wait then 🫠
c
One concern I have we switched to internal schema with 0.10.4 and it was working But in 0.10.5 what break this ?
r
What would be the timeline for this fix. Sp I can park it to team. Should free version of confluent can be used for KAFKA instead of INTERNAL
d
@creamy-van-28626 there is a feature in 0.10.5 that does not work with internal schema registry, sorry about that! For now, you can either stay on 0.10.4 or switch to confluent schema registry with 0.10.5 until we can get this fixed.
@red-florist-94889 sorry I don't have a timeline for you, as the team is stretched pretty thin this week. We will update the Github issue when we do have one though!
r
Have anyone used confluent schema registery? Does the community edition supported by datahub?
b
@red-florist-94889 yes the community edition works well. Its also just a configuration option in the helm chart. If you just switch the configs there all will be fine
r
Thanks @bland-orange-95847 will try it out then
How to get urn for s3. I'm trying to add s3 dataset urn to airflow inlets and outlets but no luck. @numerous-address-22061