The reference doc shows custom Sources and Flows but not Sinks. I wrote a
custom Sink with an InHandler that overrides onPush but it is never called.
I assumed that calling runWith would cause the SinkShape to pull by
default. An upstream custom Flow doesn't receive either onPush or onPull.
Thought I'd start a new thread for my latest stumbling block, while I
explore some options that don't feel great.
Short version:
flatMapMerge has a "breadth" parameter which limits the number of
substreams in flight. groupBy() does not. If maxSubstreams is exceeded the
stream will fail. I am
This was a very helpful response, thanks Endre. By using flatMapMerge and a
few buffers, I think I have got the queries to postgres under control.
I have a similar problem now on the sink side of the stream - I am opening
too many files at once. The file write takes a source of ByteStrings and
Hi All,
I'm experimenting with the PubSubMediator and Akka Cluster. So far so good,
but I have one use case which I cannot cover yet.
Is it possible to either:
a. Use a custom comparer on a Publish operation, to match a Publish
request against multiple topics using wildcards? E.g. similar
Hi Michael,
> 19 feb 2016 kl. 17:33 skrev Michi :
>
> I documented it here: https://github.com/mthaler/akka-http-test/
>
> I can open a ticket later. What is a PR?
>
> I think it would be useful for test-code to keep the option to disable
> certificate /
The issue with security is always that if you make something convenient,
even for testing, then somehow it ends up in production :(
-Endre
On Fri, Feb 19, 2016 at 5:33 PM, Michi wrote:
> I documented it here: https://github.com/mthaler/akka-http-test/
>
>
I documented it here: https://github.com/mthaler/akka-http-test/
I can open a ticket later. What is a PR?
I think it would be useful for test-code to keep the option to disable
certificate / hostname validation. For tests that only run on localhost
security is not an issue at all. Running
Thank you for the detailed response, Endre! This clears up some of my
questions. I'll look into the stream IO API some more.
-Ryan
On Fri, Feb 19, 2016 at 9:37 AM, Endre Varga
wrote:
> Hi Ryan,
>
>
>
> On Thu, Feb 18, 2016 at 11:14 PM, Ryan Phillips
Hi Konrad,
thanks for the quick reply, that works! Out of curiosity: is there a way to
do this on a per connection basis?
Best regards,
Michael
On Friday, February 19, 2016 at 4:55:56 PM UTC+1, Konrad Malawski wrote:
>
> Hi,
> Have you tried setting akka.ssl-config.hostnameVerifierClass to
Yeah, I guess you're right that we should document that instead.
We talked with Will that in ssl-config we'll want to remove all the "loose"
settings (including disabling this check), so documenting with that in mind
probably makes more thanks.
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @
Currently there isn't a way to do this per connection.
In general we'd prefer to not make disabling these kinds of checks actually,
but I know that's not a very popular statement.
Could you open a ticket or submit a PR that documents how to do this using the
current scheme?
Thanks a lot in
Hi,
I have written a small HTTPS test server and client and now I try to
disable hostname verification. Here is the code:
object HttpsServer extends App {
implicit val system = ActorSystem("system")
implicit val mat = ActorMaterializer()
implicit val ec = system.dispatcher
val
Hi Ryan,
On Thu, Feb 18, 2016 at 11:14 PM, Ryan Phillips wrote:
> Greetings,
>
> I've been sitting on this email for a little bit but after Владимир
> message I figured it was appropriate. My question revolves around what
> may be considered (or going to be considered) the
Thnx Endre,
Got it working :)
On Friday, February 19, 2016 at 12:06:49 PM UTC+1, drewhk wrote:
>
> Hi Jeroen,
>
> See the scaladocs on Flow. It takes the timeout as a parameter and fails
> the stream if no elements pass during that time window.
>
> -Endre
>
> On Fri, Feb 19, 2016 at 12:01 PM,
Hi Jeroen,
See the scaladocs on Flow. It takes the timeout as a parameter and fails
the stream if no elements pass during that time window.
-Endre
On Fri, Feb 19, 2016 at 12:01 PM, Jeroen Rosenberg <
jeroen.rosenb...@gmail.com> wrote:
> Thnx Endre for that swift reply.
>
> I've managed to
Thnx Endre for that swift reply.
I've managed to upgrade to Akka 2.4.2 without any issues like you expected.
Could you please give me a small code sample of how to use this idleTimeout
combinator?
Thnx a lot!
On Friday, February 19, 2016 at 11:47:40 AM UTC+1, drewhk wrote:
>
> First of all,
First of all, please use 2.0.3 since that is the latest of that version.
Actually 2.4.2 is the latest streams version but then you need Akka 2.4
(which is binary compatible so that should not be an issue).
Otherwise, you can use the .idleTimeout combinator on streams.
-Endre
On Fri, Feb 19,
I'm using Akka Http and Akka streams 2.0.1 to process data from a streaming
HTTP API. For my usecase I need to make sure I shutdown (and restart) my
app in the following scenarios:
1. Client disconnect (connection is closed by something on my end)
2. I receive a zero byte chunk, which
Thanks for the explanation, endre.
On a different note, I'm trying to understand what happens using async
boundaries.
In this example on the documentation:
1. Source(List(1, 2, 3))
2. .map(_ + 1).async
3. .map(_ * 2)
4. .to(Sink.ignore)
you create two different "islands" in the
Hi Hbf,
(which is a bit funny because I always read «Hauptbahnhof» :-) )
there are no guarantees, we only promise at-most-once messaging. That said,
local message sends are hard to drop without killing the JVM in the process.
But interrupting threads may result in undefined behavior (in
20 matches
Mail list logo