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/incubator-fury-site.git
The following commit(s) were added to refs/heads/main by this push:
new 48e075d 🔄 synced local 'docs/guide/' with remote 'docs/guide/'
48e075d is described below
commit 48e075d11e33968ebcfe4e714ff94e5c1e30fe1b
Author: chaokunyang <[email protected]>
AuthorDate: Mon May 27 02:30:25 2024 +0000
🔄 synced local 'docs/guide/' with remote 'docs/guide/'
---
docs/guide/java_serialization_guide.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/guide/java_serialization_guide.md
b/docs/guide/java_serialization_guide.md
index a86c39e..ec9fdf3 100644
--- a/docs/guide/java_serialization_guide.md
+++ b/docs/guide/java_serialization_guide.md
@@ -110,7 +110,7 @@ public class Example {
| `requireClassRegistration` | Disabling may allow unknown classes to
be deserialized, potentially causing security risks.
[...]
| `suppressClassRegistrationWarnings` | Whether to suppress class registration
warnings. The warnings can be used for security audit, but may be annoying,
this suppression will be enabled by default.
[...]
| `shareMetaContext` | Enables or disables meta share mode.
[...]
-| `deserializeUnexistedClass` | Enables or disables
deserialization/skipping of data for non-existent classes.
[...]
+| `deserializeNonexistentClass` | Enables or disables
deserialization/skipping of data for non-existent classes.
[...]
| `codeGenEnabled` | Disabling may result in faster initial
serialization but slower subsequent serializations.
[...]
| `asyncCompilationEnabled` | If enabled, serialization uses
interpreter mode first and switches to JIT serialization after async serializer
JIT for a class is finished.
[...]
| `scalaOptimizationEnabled` | Enables or disables Scala-specific
serialization optimization.
[...]
@@ -363,13 +363,13 @@ MetaContext context=xxx;
### Deserialize non-existent classes
Fury support deserializing non-existent classes, this feature can be enabled
-by `FuryBuilder#deserializeUnexistedClass(true)`. When enabled, and metadata
sharing enabled, Fury will store
+by `FuryBuilder#deserializeNonexistentClass(true)`. When enabled, and metadata
sharing enabled, Fury will store
the deserialized data of this type in a lazy subclass of Map. By using the
lazy map implemented by Fury, the rebalance
cost of filling map during deserialization can be avoided, which further
improves performance. If this data is sent to
another process and the class exists in this process, the data will be
deserialized into the object of this type without
losing any information.
-If metadata sharing is not enabled, the new class data will be skipped and an
`UnexistedSkipClass` stub object will be
+If metadata sharing is not enabled, the new class data will be skipped and an
`NonexistentSkipClass` stub object will be
returned.
## Migration
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]