Got some time to experiment: with this definition
val fetchLikesAndUpdateProfile = Flow[(OptProfile,
LikesAndCount)].flatMapConcat
{
case (Some(profile), (likesExpected, stream)) ⇒ GraphDSL.create() {
implicit builder ⇒
import GraphDSL.Implicits._
val in =
Also, it looks like that avoiding the use of a connection pool doesn't
trigger the issue. The following code works fine, without any error
class StreamOmplusEvents {
implicit val system = ActorSystem()
implicit val materializer = ActorMaterializer()
implicit val timeout =
*Simplest code to reproduce:*
class StreamOmplusEvents {
implicit val system = ActorSystem()
implicit val materializer = ActorMaterializer()
implicit val timeout = Timeout(10.seconds)
import system.dispatcher
val request = HttpRequest(
uri = "https://httpstatuses.com/200;
)
Perfect then Patrick, we will not need to inform about down and join
updates then :)
On Tuesday, November 8, 2016 at 11:26:08 AM UTC+1, Patrik Nordwall wrote:
>
> If you restart a node and join it with same hostname and port it will
> automatically Down previous incarnation of that member.
>
>
For future reference the docs page on akka.io referred to (and the rest of
the akka.io site) is in the akka.github.com repo, here:
https://github.com/akka/akka.github.com/blob/master/_includes/download.html
The actual doc contents are in the akka and akka-http repos here:
If you restart a node and join it with same hostname and port it will
automatically Down previous incarnation of that member.
On Tue, Nov 8, 2016 at 10:56 AM, Javier Ferrer González <
javier.mailse...@gmail.com> wrote:
> Hi Patrik, thanks for your response :)
>
> Do I need to send the down and
Hi there,
i am having trouble with making akka recognize an UnMarshaller, for
improved formatting i have post my question in
stackoverflow
http://stackoverflow.com/questions/40469370/missing-fromrequestunmarshallerentity-on-akka-post-route
in summary i am getting the error
could not find
Hi Patrik, thanks for your response :)
Do I need to send the down and join notifications even if the node to be
deployed will have the very same IP and port after the deploy?
I've take a look to the HTTP API and it looks awesome :D
Quite interesting to see how you test all this orchestration
Depending on the data store I think that can be rather difficult to
implement. A persistence query plugin may implement any queries and I think
this is an excellent plugin specific extension for those plugins that can
implement it without trouble.
Regards,
Patrik
On Mon, Oct 31, 2016 at 8:39 PM,
