2019-02-20 09:35:21 UTC - Laurent Chriqui: @Matteo Merli I tested with your PR
and it compiles well. Thanks.
----
2019-02-20 10:18:21 UTC - Laurent Chriqui: When I try to create functions on a
standalone pulsar server with the Master Code compiled, the cpp-client compiled
and the python-client installed, I get the following stacktrace
----
2019-02-20 10:18:31 UTC - Laurent Chriqui:
----
2019-02-20 12:45:32 UTC - Christophe Bornet: > Does it have to be at the
namespace level or can it be per-topic to start?
We could probably start with topics but namespace would be quickly needed. Can
you hint on how to do it ? Pulsar Function ? Pulsar IO ? Geo-replication ?
Other ?
----
2019-02-20 13:58:42 UTC - Ryan Samo: Hey guys, I might be blind as a bat so
forgive me but can you please point me to somewhere in the docs where it shows
how to set the rack policies for your bookies? I want to make sure we have
separate racks for them in case of failures. Thanks!
----
2019-02-20 14:31:48 UTC - Samuel Sun: Hi folks, I met this issue when I built
on new version code, anyone met this before ?
----
2019-02-20 14:31:55 UTC - Samuel Sun: ```
[ERROR] Failed to execute goal
net.alchim31.maven:scala-maven-plugin:3.4.4:compile (default) on project flink:
wrap: org.apache.commons.exec.ExecuteException: Process exited with an error:
240 (Exit value: 240) -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
net.alchim31.maven:scala-maven-plugin:3.4.4:compile (default) on project flink:
wrap: org.apache.commons.exec.ExecuteException: Process exited with an error:
240 (Exit value: 240)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:215)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
```
----
2019-02-20 14:32:27 UTC - Samuel Sun: ```
Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3;
2018-10-25T02:41:47+08:00)
Maven home: /usr/local/Cellar/maven/3.6.0/libexec
Java version: 11.0.1, vendor: Oracle Corporation, runtime:
/Library/Java/JavaVirtualMachines/openjdk-11.0.1.jdk/Contents/Home
Default locale: en_SG, platform encoding: UTF-8
OS name: "mac os x", version: "10.14.3", arch: "x86_64", family: "mac"
```
----
2019-02-20 14:32:55 UTC - Samuel Sun: I tried to "mvn clean" , looks not work
----
2019-02-20 14:36:14 UTC - Facundo Rodriguez: Yes! When I suscribe from a
ReactJS app
----
2019-02-20 14:56:38 UTC - Samuel Sun: sorry for any trouble, I revert my java
version from 11 to 1.8, it works right now, thanks
----
2019-02-20 14:57:26 UTC - Samuel Sun: it could hint this issue
<https://github.com/vavr-io/vavr/issues/2321>
----
2019-02-20 15:13:09 UTC - Joe Francis: Ah, doc is poor on this side? Take a
look at this <https://github.com/apache/pulsar/issues/151>
----
2019-02-20 15:20:55 UTC - Matteo Merli: @Samuel Sun Can you open an issue for
that? Ideally everything should compile and run on Java11. We haven’t enabled
Jenkins test on Java11 yet for some test failures with powermock that are yet
to be fixed.. though we should get to that soon.
----
2019-02-20 15:37:08 UTC - Facundo Rodriguez: `failed: Error during WebSocket
handshake: Unexpected response code: 500`
----
2019-02-20 16:15:59 UTC - Yadi Yang: @Matteo Merli Let me try it, thanks!
----
2019-02-20 18:29:29 UTC - Ryan Samo: Thanks, I’ll give it a read!
----
2019-02-20 19:27:14 UTC - Laurent Chriqui: Do we have an ETA for the 2.3.0
release ?
----
2019-02-20 19:36:44 UTC - Matteo Merli: Release is already cut, finishing up
website links before official announce
----
2019-02-20 20:35:56 UTC - Facundo Rodriguez: My bad! the URI is wrong...missins
*persistent*
----
2019-02-20 20:36:09 UTC - David Kjerrumgaard: According to the error message,
it looks like Pulsar is expecting the function to have an "init" method
defined, but is does not. Can you share the python code structure?
----
2019-02-20 20:40:01 UTC - David Kjerrumgaard: @Christophe Bornet How to do
what? Implement the Calvin algorithm?
----
2019-02-20 21:09:46 UTC - Laurent Chriqui: Ok thanks. Any ideas about the bug
running a python pulsar function that I posted earlier?
----
2019-02-20 21:14:04 UTC - Grant Wu: Did you see
<https://apache-pulsar.slack.com/archives/C5Z4T36F7/p1550694969009100?thread_ts=1550657911.222100&cid=C5Z4T36F7>
?
----
2019-02-20 21:20:29 UTC - Grant Wu: @Laurent Chriqui
----
2019-02-21 01:03:31 UTC - Sijie Guo: Glad that you figured it out already
:slightly_smiling_face:
----
2019-02-21 01:35:54 UTC - bossbaby: How to delete the data in the global-topic
in the bookie?
----
2019-02-21 02:31:56 UTC - David Kjerrumgaard: @bossbaby Bookies store data in
terms of Ledgers, while Pulsar topics are collections of these ledgers. So
unless you know ALL of the ledger ids for the topic, it will be impossible to
use BK for this. If your goal is to delete all the data in the topic only,
then why not just delete the topic itself and re-create it?
----
2019-02-21 02:33:00 UTC - David Kjerrumgaard: If your goal is to prevent
consumers from reading the current data, you can expire the messages, which
will cause the consumers to skip the current messages and only consume new
messages.
----
2019-02-21 02:33:33 UTC - David Kjerrumgaard:
<http://pulsar.apache.org/docs/en/pulsar-admin/#delete-6>
----
2019-02-21 02:33:51 UTC - David Kjerrumgaard:
<http://pulsar.apache.org/docs/en/pulsar-admin/#expire-messages-all-subscriptions>
----
2019-02-21 02:41:40 UTC - bossbaby: @David Kjerrumgaard the data in the topic
when deleted will not need to be reused, if you keep it in bookie, it will be a
waste of resources so I want to delete
----
2019-02-21 02:45:07 UTC - bossbaby: An example is that the test data will need
to be deleted when done, otherwise the bookie will hold it without deleting it,
which will reduce the server's available disk.
----
2019-02-21 02:50:35 UTC - David Kjerrumgaard: Pulsar will handle deleting
expired and consumed messages for you automatically based on the retention and
TTL policies you have defined.
----
2019-02-21 02:50:48 UTC - David Kjerrumgaard:
<http://pulsar.apache.org/docs/en/cookbooks-retention-expiry/#docsNav>
----
2019-02-21 02:51:47 UTC - David Kjerrumgaard: "expiring" a message has the same
effect as marking it consumed by all subscriptions. Then they become eligible
for deletion based on your TTL policy
----
2019-02-21 03:02:35 UTC - bossbaby: Before that I also set tts = 1M for
namespaces but the result is still the same as if the topic was deleted but the
disk space still does not decrease
----
2019-02-21 04:55:14 UTC - Samuel Sun: @Matteo Merli I filed an issue for that ,
<https://github.com/apache/pulsar/issues/3640>
100 : Sijie Guo
+1 : Matteo Merli
----
2019-02-21 08:34:07 UTC - Laurent Chriqui: The files referenced in the
Stacktrace are not mine, they are pulsar core files...I believe the issue comes
from a compilation problem but I couldn’t pinpoint exactly what to correct.
----
