I'm have some schema topics in in my Schema-Registry that I would like to remove.
I have not been able to figure out how to do this.
Can someone post an example of how to this?
Thanks
BR
Peter
I second this. I understand the rationale for not making first-class "delete" functionality, but I can't help but notice that a "delete" does exist on the KafkaStore class and is used by this project's unit tests. Well, guess what? Any sophisticated user of this project is going to want to test the ability to process schema updates in production without hiccups, but such a test can't be done without adding a dummy enhancement to the schema that we'll want to remove after the test.
Even simple instructions for blowing away the store manually would be helpful. Confluent isn't the only entity that needs to be able to test!
+1 on this request, being able to clean up old schemas looks like a pretty reasonable idea
+1
On Tue, Jan 5, 2016 at 7:50 AM Fred Cons [email protected] wrote:
+1 on this request, being able to clean up old schemas looks like a pretty
reasonable idea—
Reply to this email directly or view it on GitHub
https://github.com/confluentinc/schema-registry/issues/227#issuecomment-169040980
.
+1.. bummed this doesn't exist
+1; already built something like this ourselves for testing.
+1
+1
+1
+1
+1
+1
+1
+1
+1
+1 Can we put this back in? seems a feature used to exist. https://github.com/confluentinc/schema-registry/pull/38
+1
+1
+1
+1
+1 A year plus later and no love for this valid feature request... 😟
+1
+1
Hey, we are thinking of implementing a slightly modified version of this - allowing to delete schemas when the matching topic is deleted. What do you guys think of that?
Why not an option to be able to delete versions of a schema or completely remove schemas by id's?
@astubbs That would be a great first step. Anything that doesn't involve this kind of hacking would be great: https://groups.google.com/forum/#!topic/confluent-platform/UpJM4fEABXQ
+1 any news on this?
Another github open issue with tons of +1s!
+1
+1
+1
+1
+1
+100
+1
+1
Hey folks, no need to upvote this. The code for deleting a single version of a subject and an entire subject are already merged: https://github.com/confluentinc/schema-registry/pull/532 Documentation is on its way. This will be released in Confluent Platform 3.3.
I've added PR #584 to document the basic delete cases. Hopefully, whether or not it's merged, that's useful to people looking at this issue like I was, before Confluent get round to doing a more major documentation upgrade.
@oliverlockwood Thanks for the contribution. We do also have this info in the docs (e.g. see https://github.com/confluentinc/schema-registry/blob/master/docs/schema-deletion-guidelines.rst) and those will be published once we've released a version with this feature.
Most helpful comment
Hey folks, no need to upvote this. The code for deleting a single version of a subject and an entire subject are already merged: https://github.com/confluentinc/schema-registry/pull/532 Documentation is on its way. This will be released in Confluent Platform 3.3.