embracing the Graph DSL more as a go-to.
On Wednesday, June 21, 2017 at 9:48:20 PM UTC-4, Matlik wrote:
>
> I've got an Akka Streams Flow pattern that I've wanted to implement a few
> times in the past, but haven't been successful in finding a clean and
> simple solution that works,
i suspect the issue is related to how you call 'context.system.shutdown()'.
Make sure it is called only after all your messages have been processed to
completion. As written, it appears to be called after the first message is
handled. I'm no expert with actors, but I would guess the reason it
I've got an Akka Streams Flow pattern that I've wanted to implement a few
times in the past, but haven't been successful in finding a clean and
simple solution that works, usually resulting in some kind of refactoring
for a different approach. I'm now enhancing existing code and would like to
r the emitted proofs are valid and
> > figured out they're not. This can happen when there's a mismatch between
> > the JVM algorithm that performs the verification and the compiler
> > algorithm that generates the proofs. Which one is in your case I have no
> > idea.
> >
&
rather unlikely that Akka itself is at fault here.
> You could try using the latest version of the lib etc, however I don’t
> think that’s it…
> Do other java apps work in your env (are you sure it’s not weird / broken)?
>
>
> On June 19, 2017 at 10:36:34 PM, Matlik (james@gmail
I'm encountering this issue which I've never seen before, and was wondering
if someone could point me in the right direction. I have some Akka streams
2.4.10 code (with Scala 2.11.8) that is embedded into a GlassFish 4.0
server running Oracle Java 1.8.0_131-b11. All this is wrapped into a
I think what you are looking for is a Source that defines your queries, and
a `mapAsync (3){/* perform query */}` as that executes the queries in
parallel, and returns the results in order.
If the result of the mapAsync is collections, you can flatMap to unpack
them. If the result is Streams, you
on this.
- James
On Dec 2, 2016 8:27 AM, "Martynas Mickevičius" <
martynas.mickevic...@lightbend.com> wrote:
> James, have you seen this ticket: https://github.com/
> akka/akka-http/issues/424
>
> There is an example there, which might help you.
>
> On Tue, Nov
. Am I missing something obvious?
Much thanks,
James
On Nov 26, 2016 4:14 PM, "James Matlik" <james.mat...@gmail.com> wrote:
> I am trying to create an Akka-HTTP streaming service that supports both
> JSON and protobuf.
>
> I am able to support both for
I am trying to create an Akka-HTTP streaming service that supports both
JSON and protobuf.
I am able to support both formats without streaming using
Marshaller.oneOf(...) composition. However, I cannot seem to find something
similar for EntityStreamingSupport.
Would anyone have pointers on how
It is hard to give much input without knowing the state of the code you
want to add this one time activity into. I'm inclined to think you could
use a factory function that accepts the credentials and returns a stream.
Have a special case message be processed at the start by prepending it,
thus
are
submitted?
- James
On Jul 22, 2016 5:46 AM, "Akka Team" <akka.offic...@gmail.com> wrote:
> Hi James
>
> On Thu, Jul 14, 2016 at 1:22 PM, James Matlik <james.mat...@gmail.com>
> wrote:
>
>> Using Akka streams for ETL is our primary use case. The back pr
As always, the right answer depends on your requirements. In our case, we
have taken the following approach.
Our streams process data in a strongly ordered way, but we are able to
create many runnable graphs since this ordered processing correspond to a
relatively small subset of our overall
Using Akka streams for ETL is our primary use case. The back pressure
support has been extremely useful in helping us maximize throughout while
at the same time avoid overwhelming the multiple external rest services we
query against. By maintaining dedicated, fixed sized dispatcher pools, we
can
thing
> you can do about materialization except disabling autoFusing entirely (with
> ActorMaterializerSettings), but then you will get a much slower stream as
> each stage will run in a separate actor with async boundaries inbetween.
>
> --
> Johan
>
>
> On Fri, Jul
Is there a tutorial on how to optimize materialization somewhere? I've
designed some logic that, for a given request, will aggregate multiple
sources and stream the results back.
When streaming large amounts of data, this isn't an issue, but we now have
a use case that will request small chunks
I am trying to create a pair of Flow graphs that support some conversion
between ByteString and T.
The inbound ByteString messages are chunked by a fixed size (e.g. 8K) thus
boundaries land at arbitrary points in the data being processed.
As such, the in to out message processing is not 1:1, but
Has there been any movement forward on this discussion? I like the idea of
having a single layer of cluster coordination (discovery and availability)
for all Akka and non-Akka services. If there is a clear technical
direction and code base, I'd be interested in possibly contributing.
18 matches
Mail list logo
