This is an automated email from the ASF dual-hosted git repository. chaokunyang pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/fory-site.git
commit 107e8670866f8adce4306f2f532b66a8e4b9c776 Author: chaokunyang <[email protected]> AuthorDate: Sun Jun 7 17:33:56 2026 +0000 🔄 synced local 'docs/guide/' with remote 'docs/guide/' --- docs/guide/java/schema-evolution.md | 3 +++ docs/guide/python/schema-metadata.md | 7 ++++--- docs/guide/xlang/serialization.md | 2 +- 3 files changed, 8 insertions(+), 4 deletions(-) diff --git a/docs/guide/java/schema-evolution.md b/docs/guide/java/schema-evolution.md index 18e2613f5c..6f056f4525 100644 --- a/docs/guide/java/schema-evolution.md +++ b/docs/guide/java/schema-evolution.md @@ -48,6 +48,9 @@ is lost. Numeric strings use finite ASCII decimal syntax. Nullable and boxed fie these conversions, but reference-tracked scalar type changes are incompatible. Invalid strings and lossy conversions fail during deserialization. +Extra writer fields with no matching local field are skipped. A field that matches by tag ID or name +but has an incompatible schema is not treated as missing; deserialization fails instead. + ```java Fory fory = Fory.builder().withXlang(false) .build(); diff --git a/docs/guide/python/schema-metadata.md b/docs/guide/python/schema-metadata.md index 2af95f9ccb..50e4456a6e 100644 --- a/docs/guide/python/schema-metadata.md +++ b/docs/guide/python/schema-metadata.md @@ -320,9 +320,10 @@ written as tagged int64. Runtime type inference is used only for dynamic or unkn schemas. In compatible mode, readers consume field bytes using the remote schema metadata. Python assigns the -decoded value only when it can safely satisfy the local declared schema. Different integer encodings -in the same signedness and width domain are compatible, and same-signedness narrowing is assigned -only after range validation. +decoded value only when it can safely satisfy the local declared schema. Scalar conversion and +integer encoding adaptation apply only to the immediate matched field schema. Nested collection +elements, map keys, and map values must keep exact nullability, reference-tracking, and type shape +metadata, except for user-type family normalization such as named and unnamed struct metadata. ## Complete Example diff --git a/docs/guide/xlang/serialization.md b/docs/guide/xlang/serialization.md index 409f91cf53..338f58fcb6 100644 --- a/docs/guide/xlang/serialization.md +++ b/docs/guide/xlang/serialization.md @@ -34,7 +34,7 @@ Reduced-precision floating-point values are also part of the built-in xlang type Use the language-specific carrier types documented in the type mapping reference. Python uses `pyfory.Float16` and `pyfory.BFloat16` as annotation markers only; scalar values are native Python `float`, and dense reduced-precision arrays use `pyfory.Float16Array` and `pyfory.BFloat16Array`. Go uses the `float16` and `bfloat16` packages for scalar, slice, and array carriers; JavaScript uses `number` for scalar `float16` and `bfloat16`, and dense array carriers `BoolArray`, `Float16Array`, [...] -When `compatible=true`, a direct struct/class field can evolve between `list<T>` and `array<T>` for dense bool/numeric `T`. Integer list element encodings in the same signedness and width domain match the corresponding dense array element domain. This applies only to the immediate matched field schema. It does not apply to nested collection, map, array, union, or generic positions. If a peer `list<T>` payload declares nullable or ref-tracked elements, reading it into a local `array<T>` f [...] +When `compatible=true`, a direct struct/class field can evolve between `list<T>` and `array<T>` for dense bool/numeric `T`. Integer list element encodings in the same signedness and width domain match the corresponding dense array element domain. This applies only to the immediate matched field schema. It does not apply to nested collection, map, array, union, or generic positions. A peer `list<T?>` schema can be read into a local `array<T>` field when the actual payload has no null elem [...] ### Java --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
