[JAVA-5135] Deprecate org.bson.io.ByteBuf Created: 06/Sep/23 Updated: 11/Oct/23 |
|
| Status: | Backlog |
| Project: | Java Driver |
| Component/s: | API, BSON |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Tom Selander | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | FY25Q1-candidate | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Let's ship 5.x with a deprecation warning for this and all the methods that use it. We won't deprecate or remove it in 5.0, we can do it in the next minor version that follows. Once StreamFactory is removed, there will be less need for ByteBuf directly and we could replace it with methods that use Java's ByteBuffer class. It's currently still used in RawBsonDocument and RawBsonArray. |
| Comments |
| Comment by Tom Selander [ 06/Sep/23 ] |
|
jeff.yemin@mongodb.com just updated the ticket description and set the fixVersion to 5.1.0 |
| Comment by Jeffrey Yemin [ 06/Sep/23 ] |
|
I don't think we should deprecate anything new in a major release. We should do it in 5.1 instead. We want to make upgrading to 5.0 as simple as possible, and introducing new deprecations complicates it. |
| Comment by Tom Selander [ 06/Sep/23 ] |
|
jeff.yemin@mongodb.com Would we not deprecate in 5.0 to remove it post-5.0? I assumed that's what you meant since we didn't want to do it in 4.x. Or is the idea to do the deprecation in 5.x just not the 5.0 version? |
| Comment by Jeffrey Yemin [ 06/Sep/23 ] |
|
The proposal was to do this post-5.0, not in 5.0. |