Re: [DISCUSS] SEP-2: ApplicationRunner Design

btw, I will get to SAMZA-1246 as soon as possible. Thanks, Xinyu On Thu, Apr 27, 2017 at 9:11 PM, xinyu liu wrote: > Let me try to capture the updated requirements: > > 1. Set up input streams outside StreamGraph, and treat graph building as a > library (*Fluent, Beam*).

Re: [DISCUSS] SEP-2: ApplicationRunner Design

Let me try to capture the updated requirements: 1. Set up input streams outside StreamGraph, and treat graph building as a library (*Fluent, Beam*). 2. Improve ease of use for ApplicationRunner to avoid complex configurations such as zkCoordinator, zkCoordinationService. (*Standalone*). Provide

[GitHub] samza pull request #142: SAMZA-1219 Add metrics for operator message receive...

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

[GitHub] samza pull request #147: Access log

Github user jayasi closed the pull request at: https://github.com/apache/samza/pull/147 --- 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

[GitHub] samza pull request #147: Access log

GitHub user jayasi opened a pull request: https://github.com/apache/samza/pull/147 Access log You can merge this pull request into a Git repository by running: $ git pull https://github.com/s-noghabi/samza access-log Alternatively you can review and apply these changes as

[GitHub] samza pull request #141: Samza 1214: Allow users to set a default replicatio...

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

[GitHub] samza pull request #122: SAMZA-1210: Fixing merge issue and container id gen...

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

[GitHub] samza pull request #146: SAMZA-1224 : Revert job coordinator factory config ...

GitHub user navina opened a pull request: https://github.com/apache/samza/pull/146 SAMZA-1224 : Revert job coordinator factory config to the old format We didn't release since adding this config. So, it is ok to change the format now. You can merge this pull request into a Git

[GitHub] samza pull request #145: SAMZA-1245: Make stream samza.physical.name config ...

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

[GitHub] samza pull request #145: SAMZA-1245: Make stream samza.physical.name config ...

GitHub user xinyuiscool opened a pull request: https://github.com/apache/samza/pull/145 SAMZA-1245: Make stream samza.physical.name config name string public For certain system such as hdfs, the physical stream name might need to be finalized during the config generation. In order

Re: [DISCUSS] SEP-2: ApplicationRunner Design

That should have been: For #1, Beam doesn't have a hard requirement... On Thu, Apr 27, 2017 at 9:07 AM, Chris Pettitt wrote: > For #1, I doesn't have a hard requirement for any change from Samza. A > very nice to have would be to allow the input systems to be set up at

Re: [DISCUSS] SEP-2: ApplicationRunner Design

For #1, I doesn't have a hard requirement for any change from Samza. A very nice to have would be to allow the input systems to be set up at the same time as the rest of the StreamGraph. An even nicer to have would be to do away with the callback based approach and treat graph building as a