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

Graham Gear updated FLUME-2652:
-------------------------------
    Description: The Developer Guide Transaction and Source descriptions and 
Source example are misleading, stating that transactions must be managed within 
the Source space, when in fact they are managed within the ChannelProcessor. 
The Source example code does not compile against the current API, nor is the 
intention Source space transaction management possible with the current 
ChannelProcessor.processEvent() and BasicTransactionSemantics.begin() 
implementations.  (was: The Developer Guide Transaction and Source descriptions 
and Source example are misleading, stating that transactions must be managed 
within the Source space code, when in fact they are managed within the 
ChannelProcessor. The Source example code does not compile against the current 
API, nor is the intention source space transaction management possible with the 
current ChannelProcessor.processEvent and BasicTransactionSemantics 
implementations.)

> Documented transaction handling semantics incorrect
> ---------------------------------------------------
>
>                 Key: FLUME-2652
>                 URL: https://issues.apache.org/jira/browse/FLUME-2652
>             Project: Flume
>          Issue Type: Bug
>          Components: Docs
>    Affects Versions: v1.5.1
>            Reporter: Graham Gear
>            Priority: Minor
>         Attachments: FLUME-2652-1.patch
>
>
> The Developer Guide Transaction and Source descriptions and Source example 
> are misleading, stating that transactions must be managed within the Source 
> space, when in fact they are managed within the ChannelProcessor. The Source 
> example code does not compile against the current API, nor is the intention 
> Source space transaction management possible with the current 
> ChannelProcessor.processEvent() and BasicTransactionSemantics.begin() 
> implementations.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to