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

[Pulsar-sql]Using pulsar SQL query messages will appear NoSuchLedger when zk root directory changed #5001

Merged
merged 2 commits into from
Nov 27, 2019

Conversation

zymap
Copy link
Member

@zymap zymap commented Aug 21, 2019

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.

@sijie sijie added the area/sql Pulsar SQL related features label Aug 21, 2019
@sijie sijie added this to the 2.5.0 milestone Aug 21, 2019
Copy link
Member

@sijie sijie left a 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.

@zymap
Copy link
Member Author

zymap commented Aug 22, 2019

@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?

@sijie
Copy link
Member

sijie commented Aug 22, 2019

@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.

@jiazhai
Copy link
Member

jiazhai commented Aug 23, 2019

@zymap As Sijie suggested we could add tests for ManagedLedger firstly, this would cover most of the code changes.

@zymap
Copy link
Member Author

zymap commented Aug 23, 2019

@sijie @jiazhai thanks. I will add it.

…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
@sijie
Copy link
Member

sijie commented Nov 25, 2019

@zymap this pull request has been outstanding for a few months. Can you address the comments?

@zymap
Copy link
Member Author

zymap commented Nov 26, 2019

@sijie Ok

@zymap
Copy link
Member Author

zymap commented Nov 26, 2019

@sijie @jiazhai PTAL.

@sijie sijie merged commit e00ad11 into apache:master Nov 27, 2019
codelipenghui pushed a commit that referenced this pull request Jun 4, 2020
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`.
huangdx0726 pushed a commit to huangdx0726/pulsar that referenced this pull request Aug 24, 2020
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`.
sijie pushed a commit to apache/pulsar-presto that referenced this pull request Nov 11, 2020
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`.
sijie pushed a commit to apache/pulsar-presto that referenced this pull request Nov 11, 2020
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`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/sql Pulsar SQL related features
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[pulsar-sql] BKNoSuchLedgerExistsException when using custom ZooKeeper path for pulsar
3 participants