[ 
https://issues.apache.org/jira/browse/BEAM-9548?focusedWorklogId=408385&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-408385
 ]

ASF GitHub Bot logged work on BEAM-9548:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 23/Mar/20 23:07
            Start Date: 23/Mar/20 23:07
    Worklog Time Spent: 10m 
      Work Description: pabloem commented on pull request #11163: [BEAM-9548] 
Add better error handling to the TestStreamServiceController
URL: https://github.com/apache/beam/pull/11163#discussion_r396810340
 
 

 ##########
 File path: sdks/python/apache_beam/runners/interactive/interactive_runner.py
 ##########
 @@ -170,8 +170,13 @@ def run_pipeline(self, pipeline, options):
               user_pipeline)):
         streaming_cache_manager = ie.current_env().cache_manager()
         if streaming_cache_manager:
+
+          def exception_handler(e):
+            _LOGGER.error(str(e))
 
 Review comment:
   Same as above. Do we just log and not stop processing?
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 408385)
    Time Spent: 0.5h  (was: 20m)

> Bad error handling with errors from TestStreamService when using Interactive 
> Beam
> ---------------------------------------------------------------------------------
>
>                 Key: BEAM-9548
>                 URL: https://issues.apache.org/jira/browse/BEAM-9548
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-py-interactive
>            Reporter: Sam Rohde
>            Assignee: Sam Rohde
>            Priority: Major
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The error handling when an error is generated on the GRPC server side is very 
> verbose and hides the problem.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to