This is an automated email from the ASF dual-hosted git repository.

wangweipeng pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-fury.git


The following commit(s) were added to refs/heads/main by this push:
     new dd9f9128 chore(doc): fixed a typo (#1572)
dd9f9128 is described below

commit dd9f9128d24b418f6a420880c7780ce83d6448a2
Author: huisman6 <[email protected]>
AuthorDate: Thu Apr 25 10:58:39 2024 +0800

    chore(doc): fixed a typo (#1572)
    
    Update java_serialization_guide.md
    
    <!--
    **Thanks for contributing to Fury.**
    
    **If this is your first time opening a PR on fury, you can refer to
    
[CONTRIBUTING.md](https://github.com/apache/incubator-fury/blob/main/CONTRIBUTING.md).**
    
    Contribution Checklist
    
    - The **Apache Fury (incubating)** community has restrictions on the
    naming of pr titles. You can also find instructions in
    
[CONTRIBUTING.md](https://github.com/apache/incubator-fury/blob/main/CONTRIBUTING.md).
    
    - Fury has a strong focus on performance. If the PR you submit will have
    an impact on performance, please benchmark it first and provide the
    benchmark result here.
    -->
    
    ## What does this PR do?
    
    <!-- Describe the purpose of this PR. -->
    
    
    ## Related issues
    
    <!--
    Is there any related issue? Please attach here.
    
    - #xxxx0
    - #xxxx1
    - #xxxx2
    -->
    
    
    ## Does this PR introduce any user-facing change?
    
    <!--
    If any user-facing interface changes, please [open an
    issue](https://github.com/apache/incubator-fury/issues/new/choose)
    describing the need to do so and update the document if necessary.
    -->
    
    - [ ] Does this PR introduce any public API change?
    - [ ] Does this PR introduce any binary protocol compatibility change?
    
    
    ## Benchmark
    
    <!--
    When the PR has an impact on performance (if you don't know whether the
    PR will have an impact on performance, you can submit the PR first, and
    if it will have impact on performance, the code reviewer will explain
    it), be sure to attach a benchmark data here.
    -->
---
 docs/guide/java_serialization_guide.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/guide/java_serialization_guide.md 
b/docs/guide/java_serialization_guide.md
index 673e6a8c..8f076765 100644
--- a/docs/guide/java_serialization_guide.md
+++ b/docs/guide/java_serialization_guide.md
@@ -341,9 +341,9 @@ Object newObj = fury.execute(
 );
 ```
 
-### Deserialize un-exited classes.
+### Deserialize non-existent classes
 
-Fury support deserializing unexisted classes, this feature can be enabled
+Fury support deserializing non-existent classes, this feature can be enabled
 by `FuryBuilder#deserializeUnexistedClass(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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to