[GitHub] [tinkerpop] github5775 commented on issue #1172: Handle closed connections gracefully instead of bubbling up exceptions

["github5775 (GitHub)" <gi...@apache.org>]

As Florian pointed out, a provider, such as CosmosDB, may simply close a connection for lack of activity...each provider with its own specs.  Therefore, I would prefer to have state, not raise an error.  I would prefer to check state in submit before the connection error occurs.

WiredUK mentioned the Parse code checking for null data.  I also added that code to prevent error, but that may be best handled by dealing with the connection drop.  I will try to prove this by removing this if statement and seeing if my workaround prevents this as well.  Specifically, it's possible that this error only comes about when we call the database after the connection has dropped.  I'll let everyone know what happens.  https://issues.apache.org/jira/browse/TINKERPOP-2268?focusedCommentId=16903268&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16903268


[ Full content available at: https://github.com/apache/tinkerpop/pull/1172 ]
This message was relayed via gitbox.apache.org for dev@tinkerpop.apache.org