Re: Proposal to create a new `pulsar-translation` repo under ASF

2019-07-16 Thread Jinfeng Huang
Hi Masakazu, Thank you very much for your feedback. For the 2nd one, I've made a brief schedule, including "Topic, translator, reviewer, status (translated/approved)". See the attachment for the general workflow, and I'll write a detailed one so all contributors and reviewers can follow. With the

Re: Proposal to create a new `pulsar-translation` repo under ASF

2019-07-16 Thread Masakazu Kitajo
Hi Jennifer, Could you share projects that do similar translation task management if you know some? Ideas 1) and 3) sound good me too, but I couldn't imagine how 2) will be like. It says contributors can submit pull requests, but what files will be stored in the GitHub repo? I assume the master t

[GitHub] [pulsar-client-node] freeart opened a new pull request #37: added serialize/deserialize methods to set custom startMessageId in createReader

2019-07-16 Thread GitBox
freeart opened a new pull request #37: added serialize/deserialize methods to set custom startMessageId in createReader URL: https://github.com/apache/pulsar-client-node/pull/37 To restore Reader from the custom message needs to provide startMessageId ```js const msg = await reader.r

Slack digest for #dev - 2019-07-16

2019-07-16 Thread Apache Pulsar Slack
2019-07-16 01:24:49 UTC - Sijie Guo: @Jerry Peng : any idea why did you switch the type of publish_time from TIMESTAMP to TIMESTAMP_WITH_TIME_ZONE ? 2019-07-16 01:24:58 UTC - Sijie Guo: but not for