8000 Schema registry configuration option does not respect the path in the URL · Issue #20377 · risingwavelabs/risingwave · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Schema registry configuration option does not respect the path in the URL #20377

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.

Sign up for GitHub

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

Jump to bottom
Open
RacekM opened this issue Feb 4, 2025 · 1 comment · May be fixed by #21138
Open

Schema registry configuration option does not respect the path in the URL #20377

RacekM opened this issue Feb 4, 2025 · 1 comment · May be fixed by #21138
Assignees
@xiangjinwu
Labels
type/bug Type: Bug. Only for issues.
Milestone
release-2.5

Comments

@RacekM
Copy link
RacekM commented Feb 4, 2025

Describe the bug

I am creating a Kafka source that consumes messages from the Avro topic. To store data schemas, we use the Apicurio Schema registry. This registry supports Confluent Registry API, but you have to provide a specific path to the registry URL.
In this use case, it can look like http://localhost:8080/apis/ccompat/v6/.

If I create a source with this URL, it returns the following error.

Error message/log

[2025-02-04 15:44:03] [XX000] ERROR: Failed to execute the statement
[2025-02-04 15:44:03] Caused by these errors (recent errors listed first):
[2025-02-04 15:44:03] 1: connector error
[2025-02-04 15:44:03] 2: all request confluent registry all timeout, req path ["subjects", "topicName", "versions", "latest"], urls http://localhost:8080/apis/ccompat/v6/
[2025-02-04 15:44:03] 	confluent schema registry error 404: RESTEASY003210: Could not find resource for full path: http://localhost:8080/subjects/topicName/versions/latest

To Reproduce

Create Kafka Source:

CREATE SOURCE test WITH (
    connector = 'kafka',
    topic = 'topicName',
    properties.bootstrap.server = 'localhost:9092',
    scan.startup.mode = 'earliest'
)
FORMAT PLAIN ENCODE AVRO(
    schema.registry = 'http://localhost:8080/apis/ccompat/v6/'
);

Expected behavior

Application tries to access http://localhost:8080/apis/ccompat/v6/topicName/versions/latest instead of http://localhost:8080/subjects/topicName/versions/latest

How did you deploy RisingWave?

Kubernetes Operator

The version of RisingWave

PostgreSQL 13.14.0-RisingWave-2.1.2 (13d928542866eb9e1638b3a75485c98c12b0d0c5)

Additional context

No response
@RacekM RacekM added the type/bug Type: Bug. Only for issues. label Feb 4, 2025
@github-actions github-actions bot added this to the release-2.3 milestone Feb 4, 2025
@xiangjinwu xiangjinwu self-assigned this Feb 5, 2025
@xiangjinwu xiangjinwu linked a pull request Mar 27, 2025 that will close this issue
Open
8 tasks
@github-actions GitHub Actions
Copy link
Contributor
github-actions bot commented Apr 7, 2025

This issue has been open for 60 days with no activity.

If you think it is still relevant today, and needs to be done in the near future, you can comment to update the status, or just manually remove the no-issue-activity label.

You can also confidently close this issue as not planned to keep our backlog clean.
Don't worry if you think the issue is still valuable to continue in the future.
It's searchable and can be reopened when it's time. 😄

@xiangjinwu xiangjinwu modified the milestones: release-2.3, release-2.4 Apr 25, 2025
@BugenZhao BugenZhao modified the milestones: release-2.4, release-2.5 May 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@xiangjinwu xiangjinwu

Labels
type/bug Type: Bug. Only for issues.
Projects
None yet
Milestone
release-2.5
Development

Successfully merging a pull request may close this issue.

feat(connector): allow schema registry with prefix path risingwavelabs/risingwave
3 participants
@RacekM @xiangjinwu @BugenZhao
0