[CSHARP-4603] Investigate whether ZstdSharp.Port is affected by Zstd block splitter bug Created: 05/Apr/23  Updated: 05/Apr/23  Resolved: 05/Apr/23

Status: Closed
Project: C# Driver
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Unknown
Reporter: James Kovacs Assignee: James Kovacs
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
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   

Zstd reported a bug in its block splitter. Since .NET/C# Driver v2.18.0, the driver uses a managed implementation ZstdSharp.Port, which is a C# port of the C implementation. We currently depend on ZstdSharp.Port 0.6.2. The recently released version 0.7.0 implements Zstd v1.5.4, which is affected by the bug. Zstd fixed the bug in v1.5.5. Thus it is possible that the C# impl is also affected by this bug.

We should confirm that ZstdSharp.Port 0.6.2 and 0.7.0 are affected by the block splitter bug and if so file a GitHub issue with the ZstdSharp.Port project.



 Comments   
Comment by James Kovacs [ 05/Apr/23 ]

Won't fix because we use a hard-coded compression level 6, which is unaffected by the Zstd block splitter bug.

Comment by James Kovacs [ 05/Apr/23 ]

We currently use a default compression level of 6, which is unaffected by the block splitter bug. We do not provide a mechanism to alter the default compression level. So the driver is unaffected by the Zstd block splitter bug. I have filed an issue with ZstdSharp.Port to address the bug. We can pull in the fix if we ever decide to support user-configurable compression levels.

Generated at Wed Feb 07 21:48:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.