I think I figured out what it was. We backed out a change and it was fungible with an earlier version of the schema. Therefore it appears that it didn't create a new version of the schema. When I made a more meaningful change, it created a new 4th version.
Thanks, Mike On Wed, Jan 16, 2019 at 10:39 AM Bryan Bende <[email protected]> wrote: > Mike, > > Do you have anymore details about why the Hortonworks schema registry > stopped working? > > I have used it before and didn’t have any issues. > > Thanks > > Bryan > > On Tue, Jan 15, 2019 at 8:38 PM dan young <[email protected]> wrote: > >> We used the AvroSchemaRegistry >> >> Dano >> >> On Tue, Jan 15, 2019, 12:51 PM Mike Thomsen <[email protected] >> wrote: >> >>> What schema registry are others using in production use cases? We tried >>> out the HortonWorks registry, but it seemed to stop accepting updates once >>> we hit "v3" of our schema (we didn't name it v3, that's the version it >>> showed in the UI). So I'd like to know what others are doing for their >>> registry use since we're looking at either Confluent or going back to the >>> AvroSchemaRegistry. >>> >>> Thanks, >>> >>> Mike >>> >> -- > Sent from Gmail Mobile >
