[JAVA-4938] Consider returning/accepting Duration instead of long TimeUnit in API Created: 17/Apr/23  Updated: 06/Sep/23

Status: Backlog
Project: Java Driver
Component/s: API
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Unknown
Reporter: Valentin Kavalenka Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to JAVA-3897 Wrong type for ClusterSettings.Builde... Closed
Documentation Changes Summary:

1. What would you like to communicate to the user about this feature?
2. Would you like the user to see examples of the syntax and/or executable code and its output?
3. Which versions of the driver/connector does this apply to?


 Description   

If we decide to do this, we need to deprecate all API's returning/accepting long&unit as a duration in 4.x.



 Comments   
Comment by Jeffrey Yemin [ 22/Aug/23 ]

I haven't analyzed in detail to see how many of these are in the API, but there are 735 usages of TimeUnit in driver production code. So this will not be a small effort even if it's largely mechanical. And potentially a large effort for applications trying to upgrade.

Generated at Thu Feb 08 09:03:20 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.