-
Notifications
You must be signed in to change notification settings - Fork 594
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
feat(pulsar source): support lz4 decompression #14787
Comments
Could you connect to prometheus (port 9500) and query for |
Prometheus need to be installed separately? I am currently using Docker for installation |
I thought it was started with docker compose, which includes a prometheus container. If that is not the case, we can also get the info without prometheus. Depending on your deployment mode:
run |
now i started with docker compose, but not found the metrics user_source_reader_error in Prometheus and use http://host:port/metrics |
Alternatively, if you are still experimenting, you can also try docker image tagged with |
okey, Thanks, I will test it later |
rw-streaming pulsar::consumer::engine: rx terminated |
i used pulsar connection , pulsar used lz4 compressed message |
Thanks for your info. Then either RisingWave will need to support decompressing lz4 message from pulsar, or you can proceed by disabling lz4 compression on the producer side before the feature is available. |
disable lz4 compression it's okey, Thanks |
Describe the bug
my pulsar source table:
pulsar topic message:
Error message/log
To Reproduce
No response
Expected behavior
No response
How did you deploy RisingWave?
No response
The version of RisingWave
docker
PostgreSQL 9.5-RisingWave-1.6.0
Additional context
No response
The text was updated successfully, but these errors were encountered: