-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
[Pulsar-sql]Using pulsar SQL query messages will appear NoSuchLedger
when zk root directory changed
#5001
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@zymap the change looks good. but can you please add tests to verify your change work.
@sijie I think the integration tests is more suit for testing this scene. But I need to change the test framework to make zookeeper URI configurable and then move to the specified path, for example, 127.0.0.1:2181/pulsar, to test it is working well. Do you have any suggestions? |
@zymap managed ledger has a lot of tests there. why not add one test there? also the point here is to have tests for any code you add or modify in Pulsar. |
@zymap As Sijie suggested we could add tests for ManagedLedger firstly, this would cover most of the code changes. |
…ot directory changed --- Fixes apache#4715 *Motivation* When zookeeper ledgers root path is changed, using pulsar-sql to query messages will cause `BKNoSuchLedgerExistsException`. *Modifications* Make bookie using `setMetadataServiceUri` to set zookeeper uri
@zymap this pull request has been outstanding for a few months. Can you address the comments? |
@sijie Ok |
d681d87
to
cf8a50e
Compare
cf8a50e
to
981a4dd
Compare
Fixes #6852 ### Motivation Currently, if the config `pulsar.zookeeper-uri` use multi zk address like this `127.0.0.1:2181,127.0.0.2:2181,127.0.0.3:2181` in $PULAR_HOME/conf/presto/catalog/pulsar.properties, the Pulsar SQL query will be failed. Break PR #5001. ### Modifications Change the multi zk address delimiter from `,` to `;` for the config `metadataServiceUri` of the `ClientConfiguration`.
Fixes apache#6852 ### Motivation Currently, if the config `pulsar.zookeeper-uri` use multi zk address like this `127.0.0.1:2181,127.0.0.2:2181,127.0.0.3:2181` in $PULAR_HOME/conf/presto/catalog/pulsar.properties, the Pulsar SQL query will be failed. Break PR apache#5001. ### Modifications Change the multi zk address delimiter from `,` to `;` for the config `metadataServiceUri` of the `ClientConfiguration`.
Fixes #6852 ### Motivation Currently, if the config `pulsar.zookeeper-uri` use multi zk address like this `127.0.0.1:2181,127.0.0.2:2181,127.0.0.3:2181` in $PULAR_HOME/conf/presto/catalog/pulsar.properties, the Pulsar SQL query will be failed. Break PR apache/pulsar#5001. ### Modifications Change the multi zk address delimiter from `,` to `;` for the config `metadataServiceUri` of the `ClientConfiguration`.
Fixes #6852 ### Motivation Currently, if the config `pulsar.zookeeper-uri` use multi zk address like this `127.0.0.1:2181,127.0.0.2:2181,127.0.0.3:2181` in $PULAR_HOME/conf/presto/catalog/pulsar.properties, the Pulsar SQL query will be failed. Break PR apache/pulsar#5001. ### Modifications Change the multi zk address delimiter from `,` to `;` for the config `metadataServiceUri` of the `ClientConfiguration`.
Fixes #4715
Motivation
When zookeeper ledgers root path is changed, using pulsar-sql to query messages will cause
BKNoSuchLedgerExistsException
.Modifications
Make bookie using
setMetadataServiceUri
to set zookeeper uri.