## Description:
- Apache Samza is a distributed stream processing engine that are highly
configurable to process events from various data sources, including
real-time messaging system (e.g. Kafka) and distributed file systems (e.g.
HDFS).
## Issues:
- there are no issues requiring board attentio
GitHub user nickpan47 opened a pull request:
https://github.com/apache/samza/pull/242
SAMZA-1358: fix the bug in validating task.class empty string when apâ¦
â¦p.class is configured
Another bug due to scala/java differences.
You can merge this pull request into a Git repo
Github user asfgit closed the pull request at:
https://github.com/apache/samza/pull/242
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
To write to two different output streams, you can call collector.send()
twice.
>> For what I understand now, MessageCollector.send can only be
called once in process, because it relates to Acks, checkpoint and
processing loop.
These should be pretty orthogonal. If the docs are misleading,
Hi Jagadish,
When write one message to two different output streams, Samza will wait
acks from two different streams and then process checkpointing. Do I understand
right?
Thanks for your help!
QiShu
> 在 2017年7月12日，03:48，Jagadish Venkatraman 写道：
>
> To write to two
Yes, before the completion of a checkpoint/commit, all pending messages
(across all streams) are guaranteed to be flushed.
On Tue, Jul 11, 2017 at 7:33 PM 舒琦 wrote:
> Hi Jagadish,
>
> When write one message to two different output streams, Samza will
> wait acks from two different stream
Hi Jagadish,
Thank you very much!
QiShu
> 在 2017年7月12日，10:45，Jagadish Venkatraman 写道：
>
> Yes, before the completion of a checkpoint/commit, all pending messages
> (across all streams) are guaranteed to be flushed.
>
> On Tue, Jul 11, 2017 at 7:33 PM 舒琦 wrote:
>
>> Hi Jagad
