The GitHub Actions job "Flink CI (beta)" on flink.git/master has succeeded.
Run started by GitHub user raminqaf (triggered by raminqaf).

Head commit for run:
dab40d31eba000411f919fe9b77afc6d77bfa1a7 / Ramin Gharib <[email protected]>
[FLINK-41180][core] Sort VARIANT object fields by UTF-8 bytes

The variant spec orders the fields of an object by the unsigned UTF-8 bytes of 
their names. The builder sorted them with String.compareTo, which is UTF-16 
order, and getField binary-searched objects of 32 or more fields in the same 
order. The two orders differ when, at the first differing character, one name 
has a code point from U+E000 to U+FFFF and the other one from U+10000 up. In a 
spec-ordered object of 32 fields with the keys U+FF61 and U+1F600, 
getField(U+1F600) returned null.

The builder now sorts fields by their stored key bytes, and getField 
binary-searches in the same order. Objects written in UTF-16 order stay 
readable: after a miss for a key with a code point from U+E000 up, getField 
scans the fields linearly. For any other key both orders agree, so the miss 
stands.

Keys that differ as Strings but are stored as the same bytes, such as "a\uD800" 
and "a?", are now duplicates. Such an object held two fields with the same name 
before. getField("a\uD800") now finds the field in objects of any size.

Objects with keys from U+E000 up can have a different field order now, which 
shows in getFieldNames and in CAST to STRING. A Flink version without this 
change can miss such keys in objects of 32 or more fields. Such an object 
stored before the upgrade is not byte-equal to the same object built after it.

Generated-by: Claude Code 2.1.310 (Claude Opus 5.5)

Report URL: https://github.com/apache/flink/actions/runs/40360407600

With regards,
GitHub Actions via GitBox

Reply via email to