falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Venkatesh Seetharam (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-149) Print FileSystem exception for debugging purposes
Date Wed, 06 Nov 2013 19:54:19 GMT

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

Venkatesh Seetharam commented on FALCON-149:
--------------------------------------------

[~sureshms], the change related to propagating exception looks good. I'm not sure I understand
the second change in org.apache.falcon.service.SLAMonitoringService.Monitor#addNewPendingEntities

You have removed the following block of code. How do you ascertain that the entity is not
null for the given key?
{code}
                if (entity == null) {
                    LOG.warn("No entity for " + key);
                    continue;
                }
{code}

> Print FileSystem exception for debugging purposes
> -------------------------------------------------
>
>                 Key: FALCON-149
>                 URL: https://issues.apache.org/jira/browse/FALCON-149
>             Project: Falcon
>          Issue Type: Improvement
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>         Attachments: FALCON-149.patch
>
>
> SharedLibraryHostingService#pushLibsToHDFS should print the file system exception for
debugging.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message