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

Posted to dev@sling.apache.org by "Nicolas Peltier (JIRA)" <ji...@apache.org> on 2018/09/21 08:03:01 UTC

[jira] [Closed] (SLING-7632) Pipe Execution Result should show an error list

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

Nicolas Peltier closed SLING-7632.
----------------------------------

Sling Pipes 3.0.2 is released

> Pipe Execution Result should show an error list
> -----------------------------------------------
>
>                 Key: SLING-7632
>                 URL: https://issues.apache.org/jira/browse/SLING-7632
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: pipes 2.0.2
>            Reporter: Nicolas Peltier
>            Assignee: Nicolas Peltier
>            Priority: Major
>             Fix For: pipes 3.0.2
>
>
> While not breaking the pipe execution at the first issue encountered is important in a production world when a content exception should/could be handled separately. Errors happening are "only" happening on logs. 
> They should be tracked in the execution result as well, with path excerpt, and total #, with same limit as for results. 



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