GitHub user xinyuiscool opened a pull request:
https://github.com/apache/samza/pull/135
SAMZA-1222: Clean up LocalApplicationRunner
Clean up the LocalApplicationRunner based on the further feedback in
https://github.com/apache/samza/pull/117.
You can merge this pull request into a
GitHub user prateekm opened a pull request:
https://github.com/apache/samza/pull/134
SAMZA-1229: Disk space monitor should only count data in use by the
container
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/prateekm/samza di
It might be worth taking a look at how Beam does test streams. The API is
more powerful than just passing in a queue, e.g.:
TestStream source = TestStream.create(StringUtf8Coder.of())
.addElements(TimestampedValue.of("this", start))
.addElements(TimestampedValue.of("that", start))
.add
Thanks for the SEP!
+1 on introducing these new components
-1 on the current definition of their roles (see Design feedback below)
*Design*
- If LocalJobRunner and RemoteJobRunner handle the different methods of
launching a Job, what additional value do the different types of
Applicatio
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43244/#review172454
---
Ship it!
Ship It!
- Yi Pan (Data Infrastructure)
On Feb. 5,
GitHub user nickpan47 opened a pull request:
https://github.com/apache/samza/pull/133
SAMZA-1226: relax type parameters in MessageStream functions
relax the type parameter in user supplied functions in fluent API
You can merge this pull request into a Git repository by running:
