GitHub user navina opened a pull request:
https://github.com/apache/samza/pull/230
SAMZA-1340 - StreamProcessor does not propagate container failures from
StreamTask
Storing the exception seen from the container in the
`SamzaContainerListener#onFailure(Throwable)` in the StreamProc
Hey Navina,
I appreciate all the comments you have provided! I have updated the wiki to
remove the task expansion from Rejected Alternative section and put it only
in the Future Work section.
Thanks much!
Dong
On Wed, Jun 21, 2017 at 5:11 PM, Navina Ramesh (Apache)
wrote:
> > But IMO it is the
> But IMO it is the best available solution towards the support of
partition expansion in comparison to alternative, no?
At this time, relative to the other alternatives you have listed, this is a
path of least effort to solving this problem. I agree to that. :)
> I can merge those two sections o
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/229
Session fail reregister
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza SessionFailReregister
Alternatively you can review and apply
Thanks much for the reply Navina. Please see my reply inline.
On Wed, Jun 21, 2017 at 2:57 PM, Navina Ramesh (Apache)
wrote:
> Thanks to Jake, Dong and Kartik for keeping the discussion going.
>
> > Here are the pros and cons of the extra re-partitioning stage in
> comparison
> to SEP-5.
>
> I t
Thanks to Jake, Dong and Kartik for keeping the discussion going.
> Here are the pros and cons of the extra re-partitioning stage in
comparison
to SEP-5.
I think that is good summarization of pros/cons for the repartitioning
stage based solution. Can you please include it in your SEP? It seems li
Now that I look at the whole list again, I see we could adequately
address #2 by first addressing #3. If instead of building aggregation
directly into the window operator we had aggregation operators like
sum then the lambas would be more intuitive. It would probably even be
nicer if the first lamb
