[GitHub] [pulsar] Jim-Lambert-Bose opened a new issue #4307: OperationsTimeout in pulsar go client pulsar.ClientOptions is a time.Duration but it's treated as Seconds

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

Jim-Lambert-Bose opened a new issue #4307: OperationsTimeout in pulsar go client pulsar.ClientOptions is a time.Duration but it's treated as Seconds
URL: https://github.com/apache/pulsar/issues/4307
 
 
   **Describe the bug**
   OperationTimeoutSeconds is defined as type time.Duration (https://golang.org/pkg/time/#Duration), which leads the developer to believe they should set it to a time.Duration which for 5s would be 5000000000, since time.Duration is in nanoseconds.  Unfortunately, it's treated an integer representing seconds and it expects 5s to be represented as 5.
   
   **Expected behavior**
   If you're using time.Duration, then it should expect and deal with any valid time.Duration which is in nanoseconds not seconds.  If the pulsar only supports a timeout in seconds, then the client should define OperationTimeoutSeconds as an int
   
   Thanks.
   

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services