I'm not sure if anyone from Lightbend still monitors this list? There's a
pretty active community at gitter.im/akka/akka
Brian Maso
On Sat, May 16, 2020 at 5:42 AM Joseph Mansigian <
joseph.c.mansig...@gmail.com> wrote:
> This is a good question for Lightbend staff. Remoting wi
Ah, good factoid! Thanks!
Brian Maso
On Mon, Apr 13, 2020, 03:29 Alexey Shuksto wrote:
> > To be honest I'm not sure of how messages are handled when there are no
> active Source[T] instances consuming messages sent to Broadcast.sink[T]...
> > My impression is that they would
] instances consuming messages sent to Broadcast.sink[T]...
My impression is that they would be thrown away, and the bufferSize
parameter to BroadcastHub.sink[T] only comes into play when there are one
or more active graphs from (3) consuming messages. Experimentation is
probably necessary to confi
See Source.mapAsyncOrdered and Source.mapAsyncUnordered. That should be
enough of a pointer to get you there, but if not write again for more hints.
Also, consider joining gitter.im/akka/akka -- much more active
Brian Maso
On Thu, Nov 21, 2019, 09:31 Dennis Haupt wrote:
> i want to d
Have you seen Source.queue? Does that not get you what you are describing?
Brian Maso
On Thu, Nov 7, 2019 at 1:55 AM Bishnu Shankar Pandey <
bishnu.pan...@flutura.com> wrote:
> I saw the Example. I tried implementing it with queue but the issue that I
> am facing is that if the q
).
Anyway, sounds like some engineering work needs to be done to design a
system with sufficient throughput and error tolerances. Akka Streams isn't
the issue, there's more global architectural issues at play here.
Brian Maso
On Thu, Aug 8, 2019 at 2:02 AM Aditya pavan Kumar <
adityapavankumar
I suggest looking up "dead letters" (and maybe also "unhandled messages").
What you are describing is a dead letter message, and there is a specific
mechanism for routing and handling them in Akka.
Best regards,
Brian Maso
On Tue, Mar 26, 2019 at 3:46 AM Bishnu Shankar
The problem is that a Sink has no outlets for data. They are on-way
consumers of elements, and emit none. You probably are looking for a Flow.
Brian Maso
On Fri, Feb 1, 2019 at 12:38 PM Zohar Etzioni
wrote:
> Hello,
>
> I'm trying to get a *new* source from an *existing* sink so
and cluster sharding) to implement "eventually processed at
least once" behavior, but you'll need to employ more than just akka-streams
to do it. You'll need to add message persistence features in yourself.
Brian Maso
On Thu, Jan 17, 2019 at 10:08 PM adgang wrote:
> This is a post(set
See https://doc.akka.io/docs/akka/current/testing.html
Brian Maso
On Fri, Dec 28, 2018 at 7:06 AM wrote:
> Hi All,
> In my project we are getting message in actor and we are converting (some
> changes ) and sending into another actor. I need to write UT for this
> scenario. i am
t; pattern,
and using Flow.mapAsync with a finite "parallelism" value to integrate it
into your flow.
Brian Maso
On Tue, Nov 13, 2018 at 3:08 AM <4915374...@gmail.com> wrote:
> object stream2iter extends Iterator[(LogSequenceNumber, String)] {
> override def next: (LogSeque
a profiler to
determine what's going on.
Brian MAso
On Thu, Nov 8, 2018 at 1:37 AM <4915374...@gmail.com> wrote:
> Hello,Every Hacker:
> I am a junior software engineer. I tried to rewrite Stream as a sink and
> found that when I read a large update of the database, I thr
n use the approach from https://gist.github.com/viktorklang/9414163
> which works well. There is also a small library [1] for retry which you can
> look into.
>
> Chetan Mehrotra
> [1] https://github.com/softwaremill/retry
>
>
> On Mon, Nov 5, 2018 at 9:29 PM Brian Maso wro
... Sounds like trying to employ side-effects
where good old functional composition describes the solution much better.
Brian Maso
On Mon, Nov 5, 2018 at 1:40 AM mandeep gandhi
wrote:
> Hi all,
>
> My use case is that I want to make external calls from an actor( on
> receiving a typ
it.
Brian Maso
On Sat, Sep 29, 2018 at 8:14 PM Beno wrote:
> Hello,
>
> I have seen threads on this forum where Akka team recommends trying to
> avoid stream loops ("they are tricky"). I have a use case where steams with
> loops could be a solution to otherwise difficult
I would consider Akka Persistence or using Akka Streams with the
Flow.mapAsync function. Either one provides a way to handle your situation
without unlimited threads. Using raw Actors only it will be just a lot of
work and cleverness and wheel re-invention.
Brian Maso
On Thu, Jan 4, 2018 at 2:30
cess using Akka Streams in
several different projects -- speeding up development, simplifying testing,
and getting reliable implementations as a result.
I'd be happy to help with pointers, advice, and hints.
Brian Maso
On Wed, Dec 27, 2017 at 2:02 PM, Feyyaz <feyyazertug...@gmail.com> wrote
ld be much of a burden.
Brian Maso
On Thu, Dec 21, 2017 at 1:15 AM, <dvdgr...@gmail.com> wrote:
> Hi all,
> I have the following problem, I need to parse CSV files where the heade
> lines are not a fixed number, i.e. a file could have an header with three
> lines and another
You might also want to take a look at mapAsync() instead of map() on the
first stage of your flow. I find anything with network I/O in it makes more
sense to run through a mapAsync().
Brian Maso
On Tue, Nov 21, 2017 at 9:27 AM, Julian Howarth <10.howa...@gmail.com>
wrote:
> Ta
19 matches
Mail list logo
