On Wed, Jan 10, 2018 at 7:31 PM, Joe F wrote:
> While we are at it, can we also think of "persistent://"? PIP-11 covers
> this only for limited use cases.
>
> Maybe shorten it to p://? That will be 9MB for a million topics, in ZK
> strings (more with utf8).
You could even get rid of the //. http
> While we are at it, can we also think of "persistent://"? PIP-11 covers
> this only for limited use cases.
PIP-11 is just covering the "external" representation of topic, by allowing
apps to use the short form while internally using the complete name.
> In general the topic names are a sap on
While we are at it, can we also think of "persistent://"? PIP-11 covers
this only for limited use cases.
Maybe shorten it to p://? That will be 9MB for a million topics, in ZK
strings (more with utf8).
In general the topic names are a sap on space. With a 200 byte name, its
about 10M of strings
That's correct:
* Old topics with an arbitrary number of `/` will continue to work
* New topic without cluster name will not be able to use `/` in them
(without some kind of escaping)
I don't see an easy way around it, only that it doesn't affect the backward
compatibility. We just need to prope
Glad to see this proposal coming out to hide the cluster information!
I have a few questions regarding how to keep BC here (correct me if I am
wrong):
If I understand pulsar correct, you can use "/" in the topic name. so what
is the plan to distinguish following names:
persistent:namespace/
https://github.com/apache/incubator-pulsar/wiki/PIP-10:-Remove-cluster-for-namespace-and-topic-names
[Copying the wiki text here for easier quoting]
* **Status**: Proposal
* **Author**: Matteo Merli
* **Pull Request**: [ ]
* **Mailing List discussion**:
## Motivation
