You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Marcelo Vanzin (JIRA)" <ji...@apache.org> on 2018/01/22 21:21:00 UTC

[jira] [Resolved] (SPARK-11930) StreamInterceptor causes channel to be closed if user code throws exceptions

     [ https://issues.apache.org/jira/browse/SPARK-11930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcelo Vanzin resolved SPARK-11930.
------------------------------------
    Resolution: Won't Fix

No point in looking at this until there's a use case. Current code works fine for its purpose.

> StreamInterceptor causes channel to be closed if user code throws exceptions
> ----------------------------------------------------------------------------
>
>                 Key: SPARK-11930
>                 URL: https://issues.apache.org/jira/browse/SPARK-11930
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>            Reporter: Marcelo Vanzin
>            Priority: Minor
>
> The current implementation of {{StreamInterceptor}} in the network library allows user exceptions to bubble up to the network layer, which would cause the channel to be closed.
> That's fine for the current use cases, but in some cases it might be better to swallow the exceptions and ignore any incoming data that is part of the stream, keeping the channel open. We should add that option.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org