Hi John,
good observation, however this has not shown up in our initial benchmarking
as a bottle-neck so far AFAIR.
We're taking a systematic aproach and first improving the perf of the
biggest bang for the buck elements of Akka Http.
Currently this means we're focusing on fusing and need to
Hello and welcome to the list,
Have you read http://doc.akka.io/docs/akka/current/java/logging.html#SLF4J ?
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 17 August 2015 at 10:06:17, Pinaki C (cpinaki.m...@gmail.com) wrote:
Newbie in akka.I want to customize akka logger to use my
Somehow Google points to the M2 release which only has FlowGraph {implicit b
=} which of course doesn’t work.
The 1.0 documentation is really good (if you find it..)
Ah I see, yes that's something we should work on with our SEO optimisation I
think...
I also thought of putting up a warning
I'd write to a primary journal and use the (Akka) query side to populate
the other journal. Yes they may be a bit behind, but depending on needs
that could be optimised (query side could be pushed to).
Have you looked into Akka Persistence Query yet? We implemented something
for leveldb this week
processing stages:
doc.akka.io/docs/akka-stream-and-http-experimental/1.0/scala/stream-customize.html
--
Cheers,
Konrad Malawski
Akka @ Typesafe
On 20 August 2015 at 17:12:55, Alexey Shuksto (seig...@gmail.com) wrote:
Hello there,
I could not find answer to this particular question neither in docs
Hi Eax,
I think that re-using an implementation (Kamon for example) for the collection
of data is a good first step,
you'll want to avoid re-inventing the wheel there (and the horrible pains of
weaving instrumentation into the codebase manually ;-)).
Perhaps it's possible to re-use Kamon's
If I remember it correctly the Aggregator pattern has done it's job once
it has aggregated the values,
thus it stops itself. You could use these in the actor-per-request model,
but it's of course possible to have more aggregators inside as well.
On Wed, Jun 24, 2015 at 2:21 PM, Matheus Lima
We have ideas that might help to improve from the current recovery style,
but nothing directly planned.
It's related to this ticket: https://github.com/akka/akka/issues/17837 but
still quite researchy.
Currently you'll need to clean the persistent data before restarting
sharding.
On Thu, Jun 25,
appropriate given we are talking split
brain, though ^_^ ). How should I fix it?
Anyways: thanks for the reply. As I mentioned there, is there any risk
of race condition in performing this operation?
Thanks,
D.
On Tuesday, 23 June 2015 14:52:22 UTC+1, Konrad Malawski wrote:
Hi Diego,
I
Http has not been performance tuned yet, but we plan to do so after 1.0
(which is around 2 weeks away or so).
I'd suggest starting out with Spray currently, and then doing the move to
Akka Http should not be painful at all, since the routing DSLs are very
similar and most of the directives are
Hi Chris,
I think the feature you're after is described in the ticket:
https://github.com/akka/akka/issues/17732
https://github.com/akka/akka/issues/17346
Also see here for an in depth response about this issue:
https://github.com/akka/akka/issues/17816
On Thu, Jun 4, 2015 at 2:47 PM, Chris
Have you looked into the examples inside the Spec Martynas linked to?
It's as easy as using the FutureDirectives as seen here:
https://github.com/akka/akka/blob/4b603ad018b1b909bb331b26ab7ec5464d86cd50/akka-http-tests/src/test/scala/akka/http/server/directives/FutureDirectivesSpec.scala#L26
On
Seems you're mixing up dependencies.
Please don't use 2.3.9, use 2.3.12 (see your akka-actor dependency).
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 29 July 2015 at 22:52:05, sfosb...@twilio.com (sfosb...@twilio.com) wrote:
The subject pretty much says it all. I have the following
Hi there,
that's simple to do with just using vars inside the Actor.
I see you might want to keep the become with data style though... This
needs to get some time spent on looking into it.
If you'd have some time to investigate how to best expose this in the API
and maybe prep a PR that'd be
at 4:03:38 PM UTC+1, Konrad Malawski wrote:
Hi there,
that's simple to do with just using vars inside the Actor.
I see you might want to keep the become with data style though... This needs
to get some time spent on looking into it.
If you'd have some time to investigate how to best expose
Hi Kamil!
That looks like a pretty fun game / project actually!
Yes I think Akka would match the problem here pretty well, since you can
model the entities (and their respective websockets) as Actors.
While pretty old, you might enjoy Piotr Kukiełka's sample app where he does
something a bit
Hi there,
sorry I missed this thread previously.
This change has some background story to it, but perhaps we missed something
when Criteria is used for the delete...
I'll open a bug and have a look at it. The reason was to abandon the
deleteSnapshot(seqNr, timestamp) API, as the timestamp is
By looking at the patch it seems it's a bug indeed - would you submit the patch
as a PR Stephen?
I opened up an issue, so you could open a PR referencing the issue nr:
https://github.com/akka/akka/issues/18112
Thanks a lot for finding this and the patch!
--
Cheers,
Konrad 'ktoso’ Malawski
Hi there,
you could do it like you mention (pseudocode):
Broadcast ~ Flow[].filter(even) ~
Broadcast ~ Flow[].filter(odd) ~
However we have a built-in that serves those kinds of route things depending
on something situations well: FlexiRoute
Here are the docs for it:
But, my question was about to use Apache CXF together with Akka in an
asynchronous way (see example code) and if this ok from a technical perspective?
Should just work I guess :-)
Not the optimal setup but should just work, yeap.
-- Konrad
--
Read the docs: http://akka.io/docs/
Happy hakking! :-)
On Fri, Aug 7, 2015 at 3:46 PM, akka...@gmail.com wrote:
Thanks for your help.
Cheers
Rob
Am Freitag, 7. August 2015 15:29:40 UTC+2 schrieb Konrad Malawski:
But, my question was about to use Apache CXF *together* with Akka in an
asynchronous way (see example code
That's because *Persistent*FSMActor lives in akka-*persistence* :-)
See here:
http://doc.akka.io/docs/akka/current/scala/persistence.html#Dependencies
Notice that it's graduating from experimental mode in a few weeks (into Akka
2.4).
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 27
For Akka HTTP the experimental means that we reserve the right to change
APIs slightly,
but it's not going away it that's what worries you.
We're planning to focus on its performance these weeks (it's not very fast
yet).
On Thu, Aug 6, 2015 at 9:05 AM, akka...@gmail.com wrote:
Thank you André,
Hi there,
in general the answer is somewhat along the lines of:
Because Akka is built from the ground up around asynchronous processing, it's a
better match for building such systems.
If other tools add some async stuff, yet it is not really the core of what
they do you'll find some mismatches
Uff, indeed :-)
Gotta watch out and only keep as many ActorSystems as you really intent to have.
Glad you found the solution, happy hakking!
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 10 August 2015 at 10:31:31, n...@rubell.com (n...@rubell.com) wrote:
Hi,
I am trying to use
Hi Yaroslav!
What do you mean?
It is applied - we flush a write when the accumulated events reach lenght of
that configured setting:
eventBatch.reverse.foreach { p ⇒
addToBatch(p)
if (!writeInProgress || maxBatchSizeReached) flushJournalBatch()
If you mean the persistAll(Seq()) than that's
: immutable.Seq[A])(handler: A ⇒
Unit): Unit` in Akka 2.3
Looks like this has been fixed in Akka 2.4, thanks Konrad.
On Monday, July 27, 2015 at 11:48:04 AM UTC+3, Konrad Malawski wrote:
Hi Yaroslav!
What do you mean?
It is applied - we flush a write when the accumulated events reach lenght
The question seems double posted, let's continue in this thread
please: https://groups.google.com/forum/#!topic/akka-user/O4UmqHbP7e4
-- konrad
W dniu czwartek, 23 lipca 2015 10:14:40 UTC+2 użytkownik Leon napisał:
My sbt can find all dependencies listed on http://akka.io/docs/
except
Hi Leon,
drop the `scala`, the artifact name is: akka-http-testkit-experimental
See here:
http://search.maven.org/#artifactdetails%7Ccom.typesafe.akka%7Cakka-http-testkit-experimental_2.11%7C1.0%7Cjar
I don't see the wrong artifact name being mentioned on http://akka.io/docs/
where
did you
Hi Leon,
drop the `scala`, the artifact name is: akka-http-testkit-experimental
See here:
http://search.maven.org/#artifactdetails%7Ccom.typesafe.akka%7Cakka-http-testkit-experimental_2.11%7C1.0%7Cjar
I don't see the wrong artifact name being mentioned on http://akka.io/docs/
where did you find
Hi Leon,
drop the `scala`, the artifact name is: akka-http-testkit-experimental
See here:
http://search.maven.org/#artifactdetails%7Ccom.typesafe.akka%7Cakka-http-testkit-experimental_2.11%7C1.0%7Cjar
I don't see the wrong artifact name being mentioned on http://akka.io/docs/
where
did you
This is being discussed as issue: https://github.com/akka/akka/issues/16591
And some initial proof-of-concept repos are already appearing:
- https://github.com/kodemaniak/akka-http-restdoc
- https://github.com/devsprint/akka-http-swagger
I don’t think they’re “done” yet, but as you can
Hi Rahul,
Typesafe Console has been end-of-lifed quite some time ago.
Instead you should look into Takipi or Kamon.io while we're working to provide
something new and exciting in partnership with 3rd parties :-)
EOL annoucement:
Typesafe announces the End-Of-Life cycle for commercial support
Hi Hosam,
why do you want to run Akka using 2 threads?
Where do you configure the calling thread dispatcher?
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 14 July 2015 at 17:02:16, Hosam Aly (hosama...@gmail.com) wrote:
Hi,
I am trying to use the `CallingThreadDispatcherConfigurator`,
The nice thing with Akka streams and a Source[ByteString, _] is that you can
easily swap it for a different source without changing the rest of your impl :-)
The current impl uses nio.FileChannel with ByteBuffers which proved to give
very good performance - and I've benchmarked a number of impls
!
commits added removed
262342 335 Johannes Rudolph
11 10112 97 Endre Sándor Varga
9 757 173 Martynas Mickevičius
82821 487 Konrad Malawski
3 28 49 2beaucoup
3 701 636 Viktor Klang
2 43 7 Rafał Krzewski
2 801
On Wed, Jul 15, 2015 at 10:08 PM, Sam Halliday sam.halli...@gmail.com
wrote:
Great! We already have a branch in ENSIME to expose our JSON protocol
(JERKY) over akka-http REST and WebSockets:
Awesome, thanks for tracking the release so eagerly and for your feedback
along the way!
On Wed, Jul
I'll try to answer all questions posted here; It may take more than 1
email, please bear with me :-)
First of all congratulations on the release of akka-streams and akka-http !
Thanks!
What's a good approach to design such a service ?
All depends on the exact what should it be doing I
This sounds rather weird – can you provide a bit more details how you are
joining the nodes?
Is is seed nodes? Can you share some logs from the process? Please enable
debug logging and akka.remote.log-remote-akkalifecycle-event
Thanks!
On Mon, Jul 13, 2015 at 9:37 AM, Moiz Raja
Hi guys,
A few things to add to the discussion here :-)
Multiple journals are supported in Akka Persistence since 2.4-M1.
https://github.com/akka/akka/issues/15587
In general 2.4 will include all the things that were missing in persistence
in its experimental phase.
*Push model:*Akka
and then switching to the new impl when it's stable
would be a good idea?
On Friday, 17 July 2015 10:52:28 UTC+2, Konrad Malawski wrote:
Hi guys,
A few things to add to the discussion here :-)
Multiple journals are supported in Akka Persistence since 2.4-M1.
https://github.com/akka/akka/issues
The tweets example you mention here:
http://doc.akka.io/docs/akka-stream-and-http-experimental/1.0/scala/stream-integrations.html#Integrating_with_External_Services
Relates to the quickstart – reactive tweets:
Yep, that's how it works! :-)
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 17 July 2015 at 21:11:19, ahjohannessen (ahjohannes...@gmail.com) wrote:
If that defer works as explained, then I can reduce my code to this:
...
val durables = events map { e ⇒
DurableEvent(e,
Of course, I'd like to help. Are these docs stored in the akka/akka github repo?
Awesome, thanks in advance!
The sources are on the release-2.3-dev branch (for all akka streams things):
https://github.com/akka/akka/blob/release-2.3-dev/akka-docs-dev/rst/scala/stream-quickstart.rst
Thanks for reporting Tim!
On Jul 19, 2015 01:46, Tim Harper timchar...@gmail.com wrote:
Done. https://github.com/akka/akka/issues/18037
On Friday, July 17, 2015 at 2:32:36 PM UTC-6, √ wrote:
Interesting. Please open an Issue.
On Fri, Jul 17, 2015 at 8:31 PM, Tim Harper timch...@gmail.com
UTC+8上午5:48:26,Konrad Malawski写道:
1. what is the different between Module and Shape?
Modules are internal things.
Shapes are ports, you have FlowShape, SinkShape, SourceShape,
MyVeryOwnCustomShape etc.
Shapes describe what you can connect to things; modules are the boxes
that contain
I think you might want to use a FlexiRoute
http://doc.akka.io/docs/akka-stream-and-http-experimental/1.0/scala/stream-customize.html#Using_FlexiRoute
And in it you'd decide which way the element should go.
You'd have 2 outputs from it, one being the async path, and the other one
the other path.
Awesome, thanks for sharing and your continued enthusiasm the project! :-)
On Thu, Jul 9, 2015 at 6:04 PM, Anton Kulaga antonkul...@gmail.com wrote:
Hi all,
I updated my akka-http-extensions (
https://github.com/denigma/akka-http-extensions ) to 0.5-RC4 So, now it
also contains allow
Hi Sam,
thanks for pointing out that frustration point - we'll include this commit
adding more info about how it works
https://github.com/spray/akka/commit/b8cc008fa2288612e0d2059b3741afd8a63aa5df
in the docs (please note it's still WIP, not all docs are there yet).
On Sun, Jul 12, 2015 at 6:49
Breakpoints should just work; remember that they're line-by-line based; you may
need to split stuff into lines.
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 20 July 2015 at 22:59:01, Maatary Okouya (maatarioko...@gmail.com) wrote:
The code i am trying to debug look as such:
def
+1
for
mapAsync + ask
:-)
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 21 July 2015 at 11:59:41, Viktor Klang (viktor.kl...@gmail.com) wrote:
mapAsync + ask?
On Tue, Jul 21, 2015 at 11:53 AM, john.vie...@gmail.com wrote:
In the code example
Hi Radek,
Thanks for the feedback!
There is recover() https://github.com/akka/akka/pull/17991 but that's not
really the same; What you effectively ask for is recoverWith()
https://github.com/akka/akka/issues/18045, but we don't have it yet (it
was discussed though, a nice to have).
The real
Thanks for pointing out the typo!
Yes, as the annoucement states - they're compatible; we worked on 2.4 to keep
it binary compatible with 2.3 (even though in terms of naming those used to
mean major) :-)
We have not tried combining ActorSubscriber / ActorPublisher with
PersistentActor yet...
I read the discussion about the read-side, it's going to be in 2.5 right?
That'll be awesome :)
In fact, in 2.4 it will be in but experimental - it'll be a new module, working
well together with the current one, but separate.
If you don't need any query power you don't need to use it - i.e.
Hi there,
what you've provided using DefaultJsonProtocol._ is Format objects (from spray
json) to and from Boolean/Integer etc.
Then you've provided a Format for your case class – so far so good.
The problem here is that Akka Http does not know anything about Spray Json, as
we want to allow
Sounds great, thanks!
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 22 October 2015 at 13:12:17, Robert Budźko
(robert.krzysztof.bud...@gmail.com) wrote:
Sure. I'm preparing workshops for my colleagues soon, so I'll merge part about
intents into it and check if my examples are clear
Yup, intent based approach makes it tick. I've already applied it successfully
to the project.
Btw, I guess this is something other developers may bump into as well, would
you be up to documenting this pattern?
Either as part of the documentation or as a blog maybe?
I fear intent hell now
That's private API, please do not use it (it is marked as "INTERNAL API").
If you find yourself needing such filtering things, you should maintain a stash
yourself (keep a list of items in the actor).
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 29 October 2015 at 14:10:41, Gohar
2.4 and 2.3 are binary compatible, so you can just give it a try with 2.4.0 :)
Happy hakking!
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 21 October 2015 at 23:19:20, Richard Rodseth (rrods...@gmail.com) wrote:
Is this possible?
I've learned that migration from Spray to Akka HTTP
Maatary – please do not cross post right away to multiple spots, it makes it
really hard to track what's been answered and what not.
If after a longer time you don't get a reply somewhere it's ok to cross post,
for more exposure, however then please do link back to the answer you get
somewhere
Hi David,
It's there already though :-)
Docs:
http://doc.akka.io/docs/akka-stream-and-http-experimental/2.0-M1/scala/http/routing-dsl/directives/method-directives/patch.html
/**
* Rejects all non-PATCH requests.
*/
def patch: Directive0 = _patch
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @
Hi Gary,
(I think I replied to this already, but maybe you're only on scala-user and not
akka-user? Sorry for duplicated email everyone else).
yes, you should read the AsyncStage => GraphStage migration:
l.1...@gmail.com>
wrote:
> Sorry thank you, I should have looked better. I am just getting started
> and when looking for patch I might have been looking at some older
> documentation.
>
> Thanks
>
> On Tuesday, November 10, 2015 at 12:22:12 PM UTC-5, Konrad Malawski wro
Usually one would do something like this:
trait MyModelJsonProtocol extends DefaultJsonProtocol {
implicit val feedFormat = jsonFormat2(Feed)
}
object MyModelJsonProtocol extends MyModelJsonProtocol
And use it like so:
trait MyHelloWorldRoute extends MyModelJsonProtocol = {
val route =
Yes it should.
It's "delete messages to sequence nr 12".
We have tests for it in the TCK, but it's up to the Journal implementations to
corrently implement this.
Which journal impl are you talking about?
By the way, these things are very simple to check for yourself - just write a
test which
you
should be able to figure out how to translate your Flexi things.
There will be an M2 soon, then we'll explain in detail how to migrate from
Flexi things.
Hope this helps!
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 7 November 2015 at 01:23:17, Konrad Malawski (konrad.ma
Hi all,
thanks for trying out the early Milestone and reporting the problem!
We believe there is a bug in how the idle timeout was added, not sure if that
specific problem is a manifestation of it,
but we'll add more tests and fixes for idle timeouts in M2 (coming out soon),
please keep an eye
Hi Chris,
Jim responded quicker than I managed to; thanks! :-)
I'll add a bit more positive hints to the above suggestion,
it seems that BouncyCastle does implement the cipher you're after:
Thats more of a task for monitoring tools, i.e. our reactive monitoring
than manually building the same :)
https://www.typesafe.com/blog/introducing-reactive-monitoring-v1-0-beta-reactive-platform
On Oct 29, 2015 23:03, "akkauser" wrote:
> is there any way to override
we had the help of 30 committers.
6354691117 Johannes Rudolph
46 5747 1609 Konrad Malawski
233331 688 Alexander Golubev
1775032397 Endre Sándor Varga
1527562955 Viktor Klang
12 499 345 2beaucoup
104160 689 Mathias
10 742 143 Martynas
Nice post, thanks for sharing! :-)
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 7 November 2015 at 12:41:50, Gabriel Volpe (volpegabr...@gmail.com) wrote:
The previous project was updated and the changes were pretty straight forward.
>
> On Friday, November 6, 2015 at 4:19:49 PM UTC+3, Martynas Mickevičius
> wrote:
>>
>> ... This is also the feature that will increase performance for various
>> use cases, including HTTP.
>>
>
> Is it just the first step, or significant part of the way, or almost the
> whole way to make
Hi Jan!
Thanks for asking,
This is expected behaviour though, not a bug.
The akka.test.timefactor affects only the testing utilities, like expectMsg and
it's friends.
If you want to you can apply dilation manually, based on env variables to your
timeouts (in prod code).
Thanks and happy
:31:09, Jan-Pieter van den Heuvel (jpie...@gmail.com)
wrote:
Then it must have been magic and not this configuration parameter that made the
tests pass :)
Thanks for your clear and fast reply!
Op woensdag 4 november 2015 16:27:32 UTC+1 schreef Konrad Malawski:
As I mentioned, akka.test.timefactor
hat. Did I
misunderstand?
Kind regards,
Jan-Pieter
Op woensdag 4 november 2015 16:09:05 UTC+1 schreef Konrad Malawski:
Hi Jan!
Thanks for asking,
This is expected behaviour though, not a bug.
The akka.test.timefactor affects only the testing utilities, like expectMsg and
it's friends.
If you want
Hi Jan!
Yes, it's definitely one of those
"Do not do this because you will most likely shoot yourself in the foot"?
methods, and we believe it's much safer to keep it internal than to make it
public, thus encouraging devs to use it (and end up in around-what-hell).
We have used it very heavily
My main beef with the scaladsl for FlowGraph.Builder is that it both requires
the builder to be implicit (as in { implicit builder => }) but also requires
import FlowGraph.Implicits._, both of which are hard to discover if all you do
is to work with the code (and not reading docs).
The
between
processes.
On Wed, Oct 14, 2015 at 9:54 AM, Konrad Malawski <kt...@typesafe.com> wrote:
> ZeroMQ support has been deprecated and phased out a while ago.
> More info about it's deprecation is mentioned in the RoadMap update in
> 2014:
> https://www.typesafe.com/blog/akka-r
ZeroMQ support has been deprecated and phased out a while ago.
More info about it's deprecation is mentioned in the RoadMap update in 2014:
https://www.typesafe.com/blog/akka-roadmap-update-2014
While doing the deprecation we practically didn't see any feedback (we went
around asking for it)
that
Hi Juan,
In general it's best to think of a Cluster as something coherent - of if
you want adding Roles to separate things a bit between nodes,
but the cluster still serves one purpose – for example "a service" is
backed by a cluster, which is multiple nodes but "one service" :)
On Sat, Oct 3,
Hi there,
Yes, please increase that setting, it does the limiting by counting how many
bytes where sent and if it's exceeded aborts.
No, increasing this setting to a large number will *not* cause the file be
buffered in completeness in memory (!) - while using Akka HTTP you're safe from
those
I'm not sure how many people actually use it - we have not seen too many
questions about it.
Which either means it 'just works' or no-one is using it :-)
If you'd like to give it a spin and provide feedback that'd be awesome!
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 21 October
On Thu, Oct 15, 2015 at 4:44 AM, Fahimeh Rahemi
wrote:
> Please let me see if I understand your answer correctly, do you mean that
> if I use thread.sleep(5000) inside an actor, the actor does not leave it's
> thread at all? and the thread is idle and jobless for 5
Hi there,
If the stream completes the actor will be stopped, you can use the usual
`postStop` method
to "do things in there" i.e. signal this max processed element or something
else somewhere.
If you can draw up a more specific example we could work on that.
Do you want to expose this value as
Are there any performance issues with the seconds approach
(scala.io.Source.fromFile(file).getLines()))?
If I remember correctly 5 to 10 times slower than SynchronousFileSource, *and*
the Source.fromFile used (like in the above) example leaks open
FileInputStreams which you never close.
Hi Jack,
please don't double post questions to multiple forums at the same time, it
makes tracking if something is resolved or not yet much harder for us.
Or post the solution on the relevant cross-posted threads once you have
found it, so others can benefit from fiding it, thanks a lot in
Hi there,
we recently implemented the needed internal infrastructure for timeouts to be
implemented efficiently,
however have not yet wired up the Http / TCP level idleTimeout option to
actually do it, the ticket covering it is:
https://github.com/akka/akka/issues/16597
So it's a simple setting
Hi Robert,
In order to get this right you'll need to pivot your thinking about
serialization a bit, i.e. the problem statement of "serializing dynamic
hierarchy of actors"
is not a good one to try to design for directly – actors are entities
"which do stuff and have state". The hierarchy is not
Merged, thanks a lot! Keep on hakking :-)
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 2 July 2015 at 07:10:54, Stephen McDonald (stephen...@gmail.com) wrote:
Hi all,
I just wanted to share a project I've been working on over the last 6 months.
I've called it CurioDB [1], it's a
That's pretty awesome! Thanks for sharing :-)
If you would like to we're happy to promote it on the community page:
http://akka.io/community/#projects-using-akka
Just submit a PR with your project details to
https://github.com/akka/akka.github.com/pulls and we'll happily merge it :)
--
Cheers,
Hi Sam,
Yes, interesting catch - we do not publish scaladocs as a jar.
I guess we did not bump into this previously since many Scala devs (including
us) use IDEs which understand Java = understand JavaDoc (or they use source
jars, I think IntelliJ does).
I don't know the initial reasoning about
Play is not compatible with Akka Streams "2.0-M##" yet - it's a development
milestone, not a release you can expect all libs to be ready for already.
Please wait until Akka Streams "2.0" is released at which point Play will be
updated to work with it.
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @
I wouldn't see it as a bad thing to use sharding locally to achieve the
lazily create actors for me semantics that it implements.
You're right that it's designed for a more powerful context - i.e. it is
*cluster* sharding, to shard the load across a number of nodes,
but hey - who says you won't
Hmm, weird - this should just work (sanity checked a similar example locally).
Can you paste a full snippet of code that showcases the problem? I don't see
how it shouldn't work here.
Are you sure you're importing the right Function interface?
--
Cheers,
Konrad `ktoso` Malawski
Akka @ Typesafe
Cool happy hakking!
On Sep 4, 2015 19:36, "Jeroen Kransen" <jer...@kransen.nl> wrote:
> Sorry, it was indeed a wrong Function. With akka.japi.function.Function it
> works fine!
>
> Op vrijdag 4 september 2015 18:19:51 UTC+2 schreef Konrad Malawski:
>>
>
Hi Guido, can you explain a bit more where you see the JMH dependency pop up?
It should only be in the akka-bench project, which is not published.
Akka-actor seems clean to me:
http://search.maven.org/#artifactdetails%7Ccom.typesafe.akka%7Cakka-actor_2.11%7C2.4.0-RC2%7Cjar
--
Cheers,
Konrad
; achieve is having one json per message being pushed to kafka
>>
>> On Monday, September 7, 2015 at 3:53:38 PM UTC+2, Konrad Malawski wrote:
>>>
>>> Why not .map(json => makeTheString(json))?
>>> On Sep 7, 2015 13:30, "Ivan Baisi" <iv...@falconso
Why not .map(json => makeTheString(json))?
On Sep 7, 2015 13:30, "Ivan Baisi" wrote:
> Hi all,
>
> So I have a problem I cannot find out how to solve.
>
> I have a flow that receives many elements, and as I have to access a db
> with that data, I have to group them so I
starting to think it may be an issue
outside of akka. We have Node proxying the request over to the akka server and
it might be something funky going on there.
Sorry to have wasted your time.
Charlie
On Wednesday, September 2, 2015 at 3:02:28 PM UTC+1, Konrad Malawski wrote:
Actually, follow up
Hi Chris,
that's definitely in the plans – here's the ticket for
it: https://github.com/akka/akka/issues/15307
You can build elements like this currently, however you're right that it
could be provided as an out of the box thing and certainly be pretty useful.
Thanks for the feedback! If you
301 - 400 of 903 matches
Mail list logo