2019-02-21 09:46:02 UTC - Christophe Bornet: No, how to replicate a namespace
to another one of the same cluster ?
----
2019-02-21 10:12:35 UTC - bhagesharora: @bhagesharora has joined the channel
----
2019-02-21 10:14:15 UTC - bhagesharora: Hi, is it possible to create multiple
producer with one consumer in java, which shared same topic
----
2019-02-21 10:52:35 UTC - Laurent Chriqui: I installed the 2.3.0 pulsar-client
from pypy and I get the following stacktrace
----
2019-02-21 10:55:39 UTC - Marc Le Labourier: From what I understand of pulsar,
Consumers can share a topic if they have different subscription for example,
and multiple producers can send message to the same topic.
----
2019-02-21 10:55:58 UTC - Marc Le Labourier: Depends of what you are trying to
achieve.
----
2019-02-21 11:15:14 UTC - bhagesharora: I am trying to achieve is we have one
producer class which producing 100 messages to a topic name - "my-topic-string"
and we have another producer class which is also sending 100 messages to same
topic name - "my-topic-string", then we have one consumer class which is
consuming to messages from both the producer with same topic. @Marc Le Labourier
----
2019-02-21 12:11:51 UTC - Marc Le Labourier: I do not work with the Java
client, but in python, we do not manage the topics.
Topics creation and deletion are automatically handled by pulsar from what I
understood. Let me take a look at the Java doc.
----
2019-02-21 12:15:26 UTC - Marc Le Labourier: The doc says:
Once you’ve instantiated a PulsarClient object (as in the section above), you
can create a Producer FOR a specific Pulsar topic.
So this statement:
stringProducer = client.newProducer(Schema.STRING)
.topic(“my-topic-string”)
.create();
Seems to work like this:
I am asking the pulsar client to create a producer for a specific topic.
It does not create a topic called “my-topic-string”.
So, you should be able to create 2 producers with the same statement without
having different topics created.
+1 : bhagesharora
----
2019-02-21 12:16:40 UTC - Marc Le Labourier: From my understanding, topics are
created when a message is received and deleted when all messages have been
acknowledged by every consumers with a subscription.
+1 : bhagesharora
----
2019-02-21 12:17:20 UTC - Marc Le Labourier: Minus some configuration,
persistencies, TTL, storage, etc.
----
2019-02-21 13:39:39 UTC - bhagesharora: How to handle Exclusive consumer is
already connected exception in java ?
----
2019-02-21 14:15:35 UTC - Matteo Merli: @Laurent Chriqui thanks for reporting
early. Which version of macOS is that happening on?
100 : David Kjerrumgaard
----
2019-02-21 14:24:19 UTC - Laurent Chriqui: 10.14.13
----
2019-02-21 15:28:30 UTC - Matteo Merli: @bhagesharora With exclusive
subscriptions, there can only be 1 consumer connected to a particular
subscription (eg: subscription are identified by name)
If you wan to attach multiple consumers, you should use “Shared” subscription
type
+1 : bhagesharora
----
2019-02-21 15:28:51 UTC - Matteo Merli: Take a look at
<https://pulsar.apache.org/docs/en/concepts-messaging/#subscription-modes>
+1 : bhagesharora
----
2019-02-21 15:30:04 UTC - Matteo Merli: Got it. there seems to be something
changed in either brew or clang.. that now breaks the linking. I’ll post a fix
soon, before 2.3 is officially out
----
2019-02-21 15:31:04 UTC - David Kjerrumgaard: @Christophe Bornet If you had a
fixed number of static topics in the namespace, then it would be easy to use
pulsar functions to do that. Simply write an "echo function" that publishes the
messages it receives and configure its output topic as the same topic name in
the other namespace. It would be a very brittle solution, but it would get the
job done.
----
2019-02-21 15:43:26 UTC - Laurent Chriqui: ok great
----
2019-02-21 16:16:35 UTC - Christophe Bornet: Yes but as you can guess I need a
non-brittle solution :smile: . Do you think a PulsarIO Pulsar Sink would do the
job ?
----
2019-02-21 16:20:03 UTC - Grant Wu: I would double check your files regardless,
because the way Pulsar Functions work are that the pulsar core files import
your supplied code.
----
2019-02-21 16:20:36 UTC - Christophe Bornet: A generic Pulsar Sink could be
useful for a lot of other applications I guess
----
2019-02-21 16:20:39 UTC - Grant Wu: Although if you’re referring to
<https://apache-pulsar.slack.com/archives/C5Z4T36F7/p1550746355022600> yeah
that looks like something is broken in Pulsar….
----
2019-02-21 16:47:13 UTC - Laurent Chriqui: @Matteo Merli I downloaded the bin
for 2.3.0 and tested right now. I still have the issue regarding creating a
python Pulsar Function
----
2019-02-21 16:48:13 UTC - Laurent Chriqui: don’t know if it’s related to the
2.3.0 python/cpp client from before...
----
2019-02-21 16:52:08 UTC - Grant Wu: Actually, after googling this, it seems
like it’s probably Pulsar internal/related to Cython
<https://stackoverflow.com/questions/36723206/cython-compilation-error-dynamic-module-does-not-define-module-export-function>
----
2019-02-21 16:59:12 UTC - Laurent Chriqui: Yes that’s what I thought
----
2019-02-21 16:59:15 UTC - Matteo Merli: @Laurent Chriqui @Grant Wu The problem
seems to be that for some reason the boost regex that comes from brew is now
linking against `libicu` (which was not the case before).
We need to add that to the CMake scripts to make sure we link with that
+1 : Laurent Chriqui
----
2019-02-21 17:04:10 UTC - Matteo Merli: Actually, it’s not boost.. it’s the
libpython.dylib…
----
2019-02-21 18:56:34 UTC - David Kjerrumgaard: We could write one of those.
----
2019-02-21 19:07:23 UTC - Matteo Merli: @Laurent Chriqui It should be fixed
now, can you try again? It would be fetching 2.3.0.post1 package version
----
2019-02-21 19:23:40 UTC - Laurent Chriqui: @Matteo Merli I don't have my work
computer with me so I'll only be able to test it tomorrow! Thank you for the fix
----
2019-02-21 19:24:18 UTC - Matteo Merli: No worries. Tested locally on different
macs just to make sure
----
2019-02-22 00:55:31 UTC - Sijie Guo: @Sijie Guo set the channel topic: Pulsar
graduated as a Top-Level project :tada: - Pulsar release 2.3.0 -
<http://pulsar.apache.org/release-notes/#2.3.0>
beers : Matteo Merli, Ali Ahmed, David Kjerrumgaard, jia zhai, Ezequiel
Lovelle, xiaolong.ran, bossbaby, tuteng, Sébastien de Melo
fire : Guy Feldman, Grant Wu, Guangzhong Yao, jia zhai, bossbaby
party-parrot : jia zhai, bossbaby
bananadance : jia zhai, bossbaby
100 : jia zhai, bossbaby
----
2019-02-22 02:38:12 UTC - bossbaby: url download Pulsar IO Connectors 2.3.0
release not available
----
2019-02-22 02:53:39 UTC - Ali Ahmed: @bossbaby are you looking for these
<https://search.maven.org/search?q=pulsar-io>
----
2019-02-22 03:02:22 UTC - bossbaby: thanks @Ali Ahmed, i downloaded it but i
mean url download Pulsar IO Connectors 2.3.0 in Pulsar document
"<http://pulsar.apache.org/docs/en/standalone/#installing-builtin-connectors-optional>"
not available so fix it to everyone can download it easily
----
2019-02-22 03:03:44 UTC - Matteo Merli: Got it, thanks. Will fix soon. You can
download the connectors individually from the general download page
+1 : bossbaby, Ali Ahmed
----
2019-02-22 03:03:58 UTC - Matteo Merli: <https://pulsar.apache.org/en/download/>
----
2019-02-22 03:04:57 UTC - Matteo Merli: The docs were updated already, though
probably only in the master branch and not on 2.3 branch
----
2019-02-22 04:13:42 UTC - bossbaby: how to upgrade pulsar 2.3.0 if i want to
keep the data of the old version
----
2019-02-22 04:17:38 UTC - Jacob O'Farrell: Huge congratulations on the 2.3
release! So many new features/improvements that our teams have been chasing!!
----
2019-02-22 07:56:03 UTC - Mark Marijnissen: @Mark Marijnissen has joined the
channel
----
2019-02-22 08:41:43 UTC - eunice: @eunice has joined the channel
----
