[GitHub] samza pull request #188: SAMZA-1288: Add null check for sink OutputStream

2017-05-11 Thread xinyuiscool
GitHub user xinyuiscool opened a pull request: https://github.com/apache/samza/pull/188 SAMZA-1288: Add null check for sink OutputStream The logic to generate json for Sink operator does not check whether the output stream is null. This causes null pointer exception. You can merge

[GitHub] samza pull request #187: SAMZA-1287: Updated instructions for running integr...

2017-05-11 Thread prateekm
GitHub user prateekm opened a pull request: https://github.com/apache/samza/pull/187 SAMZA-1287: Updated instructions for running integration and stability tests. You can merge this pull request into a Git repository by running: $ git pull https://github.com/prateekm/samza in

[GitHub] samza pull request #186: Increase the plan graph size

2017-05-11 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/samza/pull/186 --- 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

[GitHub] samza pull request #132: Profiling State Performance

2017-05-11 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/samza/pull/132 --- 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

[GitHub] samza pull request #186: Increase the plan graph size

2017-05-11 Thread xinyuiscool
GitHub user xinyuiscool opened a pull request: https://github.com/apache/samza/pull/186 Increase the plan graph size Increase the canvas size to a standard 24 inch resolution and also the scaling factor. You can merge this pull request into a Git repository by running: $ git p

[GitHub] samza pull request #185: SAMZA-1286: Close zk connection in ZkController.sto...

2017-05-11 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/samza/pull/185 --- 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

[GitHub] samza pull request #185: SAMZA-1286: Close zk connection in ZkController.sto...

2017-05-11 Thread sborya
GitHub user sborya opened a pull request: https://github.com/apache/samza/pull/185 SAMZA-1286: Close zk connection in ZkController.stop() You can merge this pull request into a Git repository by running: $ git pull https://github.com/navina/samza ZkControllerClose Alternative

Re: A question about checkpointing

2017-05-11 Thread 舒琦
Hi Jagadish, I may not express my questions clearly. Here is what I want to know. When MessageCollector.send is called in process method, if sending fail and fail again, under this situation is it possible to cause data loss ( continue to fetch and process messages, but can’t s

Re: A question about checkpointing

2017-05-11 Thread Jagadish Venkatraman
Hi Qi, >> If one record can’t be sent out all the time, then the consumer will still fetch messages or not, and what about the offset checkpointing? Polling / fetching messages from the consumer (in case of Kafka) happens in a separate thread. Samza offers an at-least once processing gua

A question about checkpointing

2017-05-11 Thread 舒琦
Hi, Below is the description about checkpointing. 『Checkpointing is guaranteed to only cover events that are fully processed. It happens only when there are no pending process()/processAsync() or WindowableTask.window() invocations. All preceding invocations happen-before check