You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This query will reproduce IPPrefix compatibility issue: "
| encoding == kindEncoding Serialized encoding is not compatible with requested type: ROW. Expected ROW. Got VARIABLE_WIDTH."
SELECT CAST(ip AS ipprefix) BETWEEN ipprefix '1.2.0.0/24'
AND ipprefix '1.2.3.4/32' is_ipv4, CAST(ip AS ipprefix) as casted_ip FROM (
VALUES
(1, '1.2.0.0/24')
) AS t (id, ip);
The reason is because IPPrefix in Java is implemented as a slice of 17 bytes with the first 16 bytes stored as a big endian binary, and the last byte as the prefix length.
In Velox, IPPrefix is stored a ROW<IPAddress, TINYINT>, which means that there is a mismatch in the de-serialization and serialization when we get/sent data from/to Java.
System information
n/a
Relevant logs
No response
The text was updated successfully, but these errors were encountered:
Bug description
This query will reproduce IPPrefix compatibility issue: "
| encoding == kindEncoding Serialized encoding is not compatible with requested type: ROW. Expected ROW. Got VARIABLE_WIDTH."
The reason is because IPPrefix in Java is implemented as a slice of 17 bytes with the first 16 bytes stored as a big endian binary, and the last byte as the prefix length.
In Velox, IPPrefix is stored a ROW<IPAddress, TINYINT>, which means that there is a mismatch in the de-serialization and serialization when we get/sent data from/to Java.
System information
n/a
Relevant logs
No response
The text was updated successfully, but these errors were encountered: