[
https://issues.apache.org/jira/browse/FALCON-788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14162975#comment-14162975
]
Sowmya Ramesh commented on FALCON-788:
--------------------------------------
[~svenkat]: FalconWebException#newException does the required logging.
{noformat}
public static FalconWebException newException(String message,
Response.Status status) {
LOG.error("Action failed: {}\nError: {}", status, message);
APIResult result = new APIResult(APIResult.Status.FAILED, message);
return new FalconWebException(Response.status(status).
entity(result).type(MediaType.TEXT_XML_TYPE).build());
}
{noformat}
> Lineage: Minor bug fixes
> ------------------------
>
> Key: FALCON-788
> URL: https://issues.apache.org/jira/browse/FALCON-788
> Project: Falcon
> Issue Type: Bug
> Affects Versions: 0.6
> Reporter: Sowmya Ramesh
> Assignee: Sowmya Ramesh
> Labels: lineage
> Fix For: 0.6
>
> Attachments: FALCON-788.patch
>
>
> Couple of issues
> 1> Currently in LineageMetadataResource if there is a JSONException then
> WebApplicationException is thrown. Client receives INTERNAL_SERVER_ERROR with
> no message. Also Falcon applicaiton logs doesn't have stack trace. Throw
> FalconWebException which would log exception message and throw it for
> debugging purposes
> 2> Fixed couple of minor bugs if MetadataMappingService is not enabled
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
