streams-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (STREAMS-62) Ensure that all streams-contrib/processors are serializable
Date Tue, 29 Apr 2014 18:42:17 GMT


ASF GitHub Bot commented on STREAMS-62:

GitHub user robdouglas opened a pull request:

    STREAMS-62 | Serializability in processors

    Ensured that all processors were serializable (already merged into apache/incubator-streams)

You can merge this pull request into a Git repository by running:

    $ git pull master

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #5
commit c4da5e536c1e29e41a7a10cf395d0145846593b4
Author: Robert Douglas <>
Date:   2014-04-24T20:58:51Z

    STREAMS-62 | Ensured that all processors in incubator-streams/streams-contrib were serializable

commit 665f3040ed48bed799c62c40e07aa88b9943db52
Author: Robert Douglas <>
Date:   2014-04-24T21:46:04Z

    STREAMS-62 | Removed author information and included Apache License header for new classes

commit 1e3d0f182205a3b0f816d645f4cafaeec3f8940a
Author: Robert Douglas <>
Date:   2014-04-25T20:00:33Z

    STREAMS-62 | Moved license headers to correct locations


> Ensure that all streams-contrib/processors are serializable
> -----------------------------------------------------------
>                 Key: STREAMS-62
>                 URL:
>             Project: Streams
>          Issue Type: Task
>            Reporter: Robert Douglas
>   Original Estimate: 1.25h
>  Remaining Estimate: 1.25h
> Need to ensure that all processor components are serializable in streams-contrib. This
can be tested by using SerializationUtils.clone(processor object) in a unit test. If the test
passes, then that respective component is serializable.

This message was sent by Atlassian JIRA

View raw message