You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@daffodil.apache.org by "Steve Lawrence (JIRA)" <ji...@apache.org> on 2019/01/07 16:09:00 UTC

[jira] [Resolved] (DAFFODIL-1440) JAPI/SAPI DataProcessor should be serializable

     [ https://issues.apache.org/jira/browse/DAFFODIL-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Lawrence resolved DAFFODIL-1440.
--------------------------------------
    Resolution: Fixed

Fixed in commit fc0b2ed3809d7d310efe74c8a4a092f896bda76a

> JAPI/SAPI DataProcessor should be serializable
> ----------------------------------------------
>
>                 Key: DAFFODIL-1440
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-1440
>             Project: Daffodil
>          Issue Type: Bug
>          Components: API
>    Affects Versions: 2.0.0
>            Reporter: Steve Lawrence
>            Assignee: Steve Lawrence
>            Priority: Critical
>             Fix For: 2.3.0
>
>
> Some tools, such as Apache Spark, may need to serialize the DataProcessor to be able to send it to cluster nodes. Although we have the save/reload functions to support serialization, apache spark doesn't know how to use those, and just serializes the DataProcessor. So the SAPI/JAPI DataProcessors (which wrap the real DataProcessors) must also be made serializable.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)