[GitHub] [tinkerpop] spmallette commented on pull request #1792: Implement Python Query/Connection Retry Logic

[GitBox <gi...@apache.org>]

spmallette commented on PR #1792:
URL: https://github.com/apache/tinkerpop/pull/1792#issuecomment-1244253241

   > Is this due to complexity or because the feature is not desirable?
   
   Just to clarify, as the feature was originally proposed it was, at the time, found not desirable. That wasn't to say that if it were re-proposed now under new circumstances that no one would want it. I'd also keep in mind that the last time this was discussed to my recollection was several years ago, prior to the introduction of the specific retry error code, so I was just trying to provide historical context. 
   
   I think the more important take here is feature parity in the drivers - if we do it for one, it should be done for all and any PR (or series of PRs) would need to have a plan for that. The further implication then is that that sort of makes this a major feature and requires a wide community consensus. Usually a feature with this sort of scope needs more than just a PR to get that consensus - it would require a DISCUSS thread on the dev mailing list with some sort of proposal for what the design would be. We've already had some discussion here on it so summarizing all this into a post and perhaps addressing some of the points made there would be a good start.


-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@tinkerpop.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org