You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Martin Kleppmann (JIRA)" <ji...@apache.org> on 2014/06/03 01:01:03 UTC

[jira] [Updated] (SAMZA-7) Update website docs

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

Martin Kleppmann updated SAMZA-7:
---------------------------------

    Attachment: SAMZA-7.v2.patch

I have updated the RB https://reviews.apache.org/r/21866/ and also attached a patch with the latest edit of the docs. I could keep going forever, but I think it's sufficient for now for purposes of a 0.7.0 release, so please could someone review it.

The pages in the "api" and "container" section are pretty much entirely rewritten, now hopefully clearer, more complete and easier to follow. As a general trend, I've tried to present things more from the point of view of someone writing a Samza job, less from the point of view of Samza's internals. There are some new diagrams, and a new page on serialization. In the later sections ("jobs", "YARN", "Operations") I have only made basic edits to use Samza 0.7 terminology instead of 0.6 terminology. At some point in future they would also benefit from some thorough editing, but that's not urgent.

This patch doesn't cover the configuration table (SAMZA-165) or the javadocs (SAMZA-35).

> Update website docs
> -------------------
>
>                 Key: SAMZA-7
>                 URL: https://issues.apache.org/jira/browse/SAMZA-7
>             Project: Samza
>          Issue Type: Bug
>          Components: docs
>    Affects Versions: 0.6.0
>            Reporter: Chris Riccomini
>            Assignee: Martin Kleppmann
>             Fix For: 0.7.0
>
>         Attachments: SAMZA-7.v2.patch
>
>
> The website docs refer to TaskRunner, StreamConsumer, etc. These classes have been refactored to SamzaContainer, SystemConsumer, etc. We should go through and update the docs to make sure they reflect reality.



--
This message was sent by Atlassian JIRA
(v6.2#6252)