Jenkins build is back to normal : flume-trunk #482

[Apache Jenkins Server]

See 

[jira] [Commented] (FLUME-2139) upgrade morphline library dependency to a 0.5.0 release

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLUME-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728410#comment-13728410
 ] 

Hudson commented on FLUME-2139:
---

SUCCESS: Integrated in flume-trunk #482 (See 
[https://builds.apache.org/job/flume-trunk/482/])
FLUME-2139. Upgrade morphline CDK dependency to 0.5.0 release. (mpercy: 
http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=5bda4a70a1ee3fe45a19c90cb81b09ad1d2ec25b)
* flume-ng-sinks/flume-ng-morphline-solr-sink/pom.xml


> upgrade morphline library dependency to a 0.5.0 release
> ---
>
> Key: FLUME-2139
> URL: https://issues.apache.org/jira/browse/FLUME-2139
> Project: Flume
>  Issue Type: Improvement
>  Components: Build
>Affects Versions: v1.4.0
>Reporter: Roman Shaposhnik
>Assignee: Roman Shaposhnik
> Fix For: v1.4.1, v1.5.0
>
> Attachments: FLUME-2139.patch.txt
>
>
> I suggest we upgrade the dependency. Let me know if that wouldn't work for 
> somebody. Trivial patch is coming shortly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (FLUME-2139) upgrade morphline library dependency to a 0.5.0 release

[Mike Percy (JIRA)]

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

Mike Percy resolved FLUME-2139.
---

Resolution: Fixed

Having issues with unit tests but I think they're related to the recent HTTPS 
patch. Pushed to trunk and flume-1.5 branches.

> upgrade morphline library dependency to a 0.5.0 release
> ---
>
> Key: FLUME-2139
> URL: https://issues.apache.org/jira/browse/FLUME-2139
> Project: Flume
>  Issue Type: Improvement
>  Components: Build
>Affects Versions: v1.4.0
>Reporter: Roman Shaposhnik
>Assignee: Roman Shaposhnik
> Fix For: v1.4.1, v1.5.0
>
> Attachments: FLUME-2139.patch.txt
>
>
> I suggest we upgrade the dependency. Let me know if that wouldn't work for 
> somebody. Trivial patch is coming shortly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (FLUME-2139) upgrade morphline library dependency to a 0.5.0 release

[Mike Percy (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLUME-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728312#comment-13728312
 ] 

Mike Percy commented on FLUME-2139:
---

+1, if the tests pass I'll commit this.

> upgrade morphline library dependency to a 0.5.0 release
> ---
>
> Key: FLUME-2139
> URL: https://issues.apache.org/jira/browse/FLUME-2139
> Project: Flume
>  Issue Type: Improvement
>  Components: Build
>Affects Versions: v1.4.0
>Reporter: Roman Shaposhnik
>Assignee: Roman Shaposhnik
> Fix For: v1.4.1, v1.5.0
>
> Attachments: FLUME-2139.patch.txt
>
>
> I suggest we upgrade the dependency. Let me know if that wouldn't work for 
> somebody. Trivial patch is coming shortly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (FLUME-2140) Support diverting bad events from pipeline

[Arvind Prabhakar (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLUME-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727912#comment-13727912
 ] 

Arvind Prabhakar commented on FLUME-2140:
-

Another case - a downstream filter is buggy and causes a batch to fail 
repeatedly due to a malformed header or some other details.

> Support diverting bad events from pipeline
> --
>
> Key: FLUME-2140
> URL: https://issues.apache.org/jira/browse/FLUME-2140
> Project: Flume
>  Issue Type: New Feature
>  Components: Node
>Reporter: Arvind Prabhakar
>
> A *bad event* can be any event that causes persistent sink side processing 
> failure due to the inherent nature of the event itself. Note that failures 
> that are not related to the inherent nature of the event such as network 
> communication failure, downstream capacity failure etc., do not make the 
> event a bad-event.
> The presence of a bad event in a channel can cause the entire pipleline to 
> choke and become unusable. Flume should therefore be able to identify bad 
> events and provide a facility to route them out of the pipleline in order to 
> ensure the transport of other events continues uninterrupted.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (FLUME-2139) upgrade morphline library dependency to a 0.5.0 release

[Roman Shaposhnik (JIRA)]

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

Roman Shaposhnik updated FLUME-2139:


Attachment: FLUME-2139.patch.txt

Attaching a trivial patch. It builds and tests pass.

> upgrade morphline library dependency to a 0.5.0 release
> ---
>
> Key: FLUME-2139
> URL: https://issues.apache.org/jira/browse/FLUME-2139
> Project: Flume
>  Issue Type: Improvement
>  Components: Build
>Affects Versions: v1.4.0
>Reporter: Roman Shaposhnik
>Assignee: Roman Shaposhnik
> Fix For: v1.4.1, v1.5.0
>
> Attachments: FLUME-2139.patch.txt
>
>
> I suggest we upgrade the dependency. Let me know if that wouldn't work for 
> somebody. Trivial patch is coming shortly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (FLUME-2140) Support diverting bad events from pipeline

[Roshan Naik (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLUME-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727742#comment-13727742
 ] 

Roshan Naik commented on FLUME-2140:


It appears that may be only the sink is able to know for certain (at the time 
to delivery) that a particular event is bad. 

One scenario that comes to mind here:
- an event that may be bad for one sink maynot be bad for another. for 
instance, logger sink or rolling file sink may not have trouble delivering an 
event that is troublesome for elastic search sink.

> Support diverting bad events from pipeline
> --
>
> Key: FLUME-2140
> URL: https://issues.apache.org/jira/browse/FLUME-2140
> Project: Flume
>  Issue Type: New Feature
>  Components: Node
>Reporter: Arvind Prabhakar
>
> A *bad event* can be any event that causes persistent sink side processing 
> failure due to the inherent nature of the event itself. Note that failures 
> that are not related to the inherent nature of the event such as network 
> communication failure, downstream capacity failure etc., do not make the 
> event a bad-event.
> The presence of a bad event in a channel can cause the entire pipleline to 
> choke and become unusable. Flume should therefore be able to identify bad 
> events and provide a facility to route them out of the pipleline in order to 
> ensure the transport of other events continues uninterrupted.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira