I've been using the Streams API to build a few things for the past couple months, and I have a humble suggestion for an API enhancement. I'm not sure if this is even possible to do given the contract of how a Flow operates, adding a method to FlowOps with the following signature would be quite useful -
def recover(f: PartialFunction[(In, Throwable), Out]): Repr[Out, Mat] It's likely due to the fact that I have yet to fully internalize the Flow API, but I've found that the supervision functionality isn't exactly what I need. On the top-level, it makes complete sense, but there is no way to deal with an error in a stream and not have at least one message silently dropped. It would be nice to be able to set up more fine-grained error handling. As an example, imagine a stream that was processing incoming deltas to a set of records held either in memory or some persistent data store. A failure of a given delta should not necessarily shut down the whole pipeline, but the associated record should be marked as inconsistent and dealt with appropriately. Using the current supervision API, there's no way to determine the actual element that caused the failure, and thus there's no real way to handle it or signal an external system with the details of the error. Of course, you can work around this by making the stream operate on a Try[T] instead of T, but that just seems unwieldy. Am I looking at this the wrong way? -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
