Hey everybody,
I can create a sink that broadcasts incoming messages to a given list of
sinks. How can I make that sink materialize a future that completes when
the downstream sinks have completed?
For example,
final Source in = Source.from(Arrays.asList(1,
2, 3, 4, 5));
final
splitWhen/splitAfter can only have one substream open at any given time and
grouped does not create substreams but collections.
Regards,
Roland
Sent from my iPhone
> On 22 Dec 2015, at 23:47, matheuslima...@gmail.com wrote:
>
> * Why splitAfter/splitWhen/grouped don't have maxSubstreams para
* Why splitAfter/splitWhen/grouped don't have maxSubstreams parameter by
the same reason (bound resource consumption)?
On Tuesday, December 22, 2015 at 8:44:14 PM UTC-2, matheus...@gmail.com
wrote:
>
> Why splitAfter/splitWhen/grouped also haven't maxSubstreams parameter by
> the same reason (b
Why splitAfter/splitWhen/grouped also haven't maxSubstreams parameter by
the same reason (bound resource consumption)?
On Tuesday, December 22, 2015 at 7:18:25 PM UTC-2, rkuhn wrote:
>
> We will make it fusable in the same fashion as
> splitWhen/splitAfter/prefixAndTail are fusable. One minor co
We will make it fusable in the same fashion as
splitWhen/splitAfter/prefixAndTail are fusable. One minor correction: the
number of substreams is no longer unbounded, the API demands that you specify a
limit beyond which the groupBy logic will fail the stream. This is necessary in
order to place
This topic clarified almost all questions I had on fusion. The only one
question remains is how groupBy stage will properly fused. If we are
modelling a stream of stream processing (for example, process telemetry
events for multiple IoT devices continuously is a stream of stream), maybe
makes n
Hi Adam,
> 22 dec 2015 kl. 20:37 skrev Adam Warski :
>
>
>> Now, with auto-fusing that changes. By default, if there's a split, the
>> branches won't be executed in parallel. I think that's quite a big
>> semantical change.
>
> This is a bit of an overstatement: the semantics of the stream pr
>
>
> Now, with auto-fusing that changes. By default, if there's a split, the
> branches won't be executed in parallel. I think that's quite a big
> semantical change.
>
>
> This is a bit of an overstatement: the semantics of the stream processing
> do not change, the same rules apply to how el
Hi,
we are currently in phase of evaluating akka as our microservice
architecture implementation.
According to basic Microservice architecture rules, microservices should
communicate with each other using language agnostics API like REST.
My question is:
1. are we missing something by using
Hi Adam,
thanks for trying out the new release (and for the blog update!) and also for
your feedback; comments inline.
> 22 dec 2015 kl. 16:41 skrev Adam Warski :
>
> Hello,
>
> I think that the new fusing support in akka-streams may have more
> consequences than I initially suspected. It qui
On Tuesday, December 22, 2015 at 5:17:09 PM UTC+1, Konrad Malawski wrote:
>
>
> I'll leave the semantics questions to Roland or Endre to tackle (in
> general it should not change semantics), but a few quick ones:
>
>
> 2. how to insert async boundaries in linear pipelines? E.g.:
>
> Source(List(
I'll leave the semantics questions to Roland or Endre to tackle (in general it
should not change semantics), but a few quick ones:
2. how to insert async boundaries in linear pipelines? E.g.:
Source(List(1, 2, 3))
.map(_ + 1)
.addAttributes(Attributes.asyncBoundary)
.map
Hello,
I think that the new fusing support in akka-streams may have more
consequences than I initially suspected. It quite drastically changes how
concurrency is handled in akka-streams.
So far the model was quite clear: every stage gets materialised into an
actor. If there's a split/broadcast
no, that is harmless and the merged result looks correct
On Tue, Dec 22, 2015 at 1:56 PM, Anders Båtstrand
wrote:
> I tried this again, and looked in the logs. The nodes are downed as
> expected, but the following was interesting. Could it be related?
>
> 2015-12-22 13:34:39,983 DEBUG akka.clust
I tried this again, and looked in the logs. The nodes are downed as
expected, but the following was interesting. Could it be related?
2015-12-22 13:34:39,983 DEBUG akka.cluster.ClusterCoreDaemon
my-system-akka.actor.default-dispatcher-15 - Couldn't establish a causal
relationship between "remote"
15 matches
Mail list logo
