Skip to content
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

Reference schema from other subject during validation #3485

Open
urmichm opened this issue Dec 17, 2024 · 0 comments
Open

Reference schema from other subject during validation #3485

urmichm opened this issue Dec 17, 2024 · 0 comments

Comments

@urmichm
Copy link

urmichm commented Dec 17, 2024

Similar to issue #426
Can it combine schemas before validating it?
Given plugin 'kafka-schema-registry-maven-plugin'

 <plugin>
                <groupId>io.confluent</groupId>
                <artifactId>kafka-schema-registry-maven-plugin</artifactId>
                <version>7.8.0</version>
                <configuration>
                    <schemaRegistryUrls>
                        <param>${schema.registry.url}</param>
                    </schemaRegistryUrls>
                    <subjects>
                        <order-v1-value>
                            ${schema.path}/Order.avsc
                        </order-v1-value>
                    </subjects>
                </configuration>
                <executions>
                    <execution>
                        <phase>validate</phase>
                        <goals>
                            <goal>test-compatibility</goal>
                        </goals>
                    </execution>
                </executions>
</plugin>

Order and Product are the objects from #426
Schema registry has Order as a stand alone object, therefore Product is inline defined for it.
Could the validator combine the reference objects into inline definitions and then validate it against schema registry?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant