[
https://issues.apache.org/jira/browse/LUCY-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marvin Humphrey resolved LUCY-81.
---------------------------------
Resolution: Fixed
That covers serialization for all current candidate classes.
As a footnote, this serialization implementation doesn't seek to solve the
problems associated with references or reference cycles. If you have a Hash
or a VArray where the same object serves as a value for multiple slots, it
will be exploded to multiple objects on deserialization. Similarly, reference
cycles are not detected and will trigger an infinite loop.
> Object serialization
> --------------------
>
> Key: LUCY-81
> URL: https://issues.apache.org/jira/browse/LUCY-81
> Project: Lucy
> Issue Type: New Feature
> Components: Core
> Reporter: Marvin Humphrey
> Assignee: Marvin Humphrey
> Attachments: bytebuf_serialization.diff, charbuf_serialization.diff,
> freezer.diff, hash_serialization.diff, hash_serialization.diff,
> num_serialization.diff, obj_serialize.diff, varray_serialization.diff
>
>
> Objects are serialized to OutStreams and deserialized from InStreams. Hooks
> are provided for the Perl core serialization module Storable, so that e.g.
> Storable::freeze($query) works as expected; hopefully it will prove practical
> to hook into canonical serialization routines for other hosts as well.
> The primary utility for serialization is communication between machines within
> search clusters, so all classes that may need to be sent across the network
> will eventually get serialization routines. However, only Lucy installations
> with exactly the same version can be guaranteed to serialize and deserialize
> each others data; rolling updates are not supported.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
