Open shamimashik opened 3 months ago
I noticed this a while ago too. I thought that it was intentional to save space if all the values after a certain index are null.
I wrote my code the following way to accommodate the key
and value
array lengths not being the same.
Library Version
4.23.4
OS
Windows
OS Architecture
64 bit
How to reproduce?
I'm seeing a difference in DataColumn.Data.Length for the keyColumn and the valueColumn of the partitionValues column.
Here's the paths I'm using - keyPath: "add/partitionValues/key_value/key" valuePath: "add/partitionValues/key_value/value"
For the keyPath, I'm getting 64865 as the DataColumn.Data.Length whereas valuePath returns 64867.
Note that this issue was not present in version 3.10.0
Failing test