Apicurio/apicurio-registry

Summary The Confluent Schema Registry v7 compatibility endpoint GET /subjects/{subject} currently returns null because getSubjectMetadata is unimplemented. This is a compatibility gap for clients that query subject metadata. Location app/src/main/java/io/apicurio/registry/ccompat/rest/v7/impl/SubjectsResourceImpl.java (lines 476-479) Current behavior @Override public Schema getSubjectMetadata(String subject, String key, String value, String format, Boolean deleted, String xRegistryGroupId) { //TODO not implemented return null; }

Summary DataExporter.exportData logs per-entity ZIP write errors and increments an errorCounter, but the endpoint still returns HTTP 200 with a potentially corrupt/incomplete ZIP archive. Location app/src/main/java/io/apicurio/registry/rest/v3/impl/shared/DataExporter.java (lines 47-58) Current behavior storage.exportData(...) invokes writer.writeEntity(entity) for each exported entity. If writer.writeEntity throws, the exception is logged and errorCounter is incremented, but the export continues. After the loop, the code does // TODO if the errorCounter > 0, then what? and returns the ZIP with 200 OK. Expected behavior A failed entity write should cause the export to fail in a way the client can detect, either: By aborting the stream and returning an HTTP 5xx / 4xx response, or By including a manifest of failed entities so the client knows the ZIP is partial. Acceptance criteria Determine the desired failure mode for v3 export. Implement the chosen behavior. Add unit/integrati

Description Registry Version: snapshot (build from main, 3.3.1-SNAPSHOT) Persistence type: N/A - this is a compile-time warning, independent of the storage backend AbstractCompatibilityChecker has a private helper that takes a generic varargs argument: private Set<D> unionOf(Set<D>... from) { Because Set<D> isn't reifiable, the compiler has to create a generic array for the varargs, and that produces an unchecked warning every time the method is called. It's not annotated with @SafeVarargs or @SuppressWarnings, so the warning shows up on a normal build. The two callers are the FULL and FULL_TRANSITIVE branches of testCompatibility, and both of them only ever pass exactly two sets, so the varargs isn't really buying anything here. File: schema-util/common/src/main/java/io/apicurio/registry/rules/compatibility/AbstractCompatibilityChecker.java (the unionOf method, plus its call sites in the FULL / FULL_TRANSITIVE cases). Nothing is functionally broken, the union result is correct. It's a

Description Registry Version: main / 3.3.1-SNAPSHOT (fresh clone from https://github.com/Apicurio/apicurio-registry) Persistence type: N/A - documentation / developer setup issue (UI module) The README Getting started (UI) section instructs developers to run: cd ui npm install cd ui-app ./init-dev.sh npm run dev On Windows with PowerShell, ./init-dev.sh is not a native command. There is no .ps1, .bat, or Windows-specific instructions in the root README getting-started flow. The script only copies two config files (configs/version.js → version.js and configs/config-local.js → config.js). The workaround is simple, but not documented for Windows users in the main README. This affects Windows contributors who want to run the UI in dev mode alongside the Registry API. Environment OS: Windows 10/11 (10.0.26200) Shell: PowerShell (default Windows shell) Node: v20.x Registry backend: Docker (apicurio/apicurio-registry:latest-snapshot on port 8080) Module: ui/ui-app Interaction: Local UI d

Tab Documentation is empty. I have content Openapi in my version and when I enter in Documentation tab this is empty This is under version 3.3.0