falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Narayan Periwal (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1477) Adding "-debug" option to Falcon CLI for debug statements to stdout.
Date Fri, 25 Sep 2015 07:24:04 GMT

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

Narayan Periwal commented on FALCON-1477:

[~sriksun], IMO either we should print the jersey object in printClientResponse() at all places,
or if we print in checkIfSuccessful(), then we need to add the call at places where it is
missing. This will make the solution clean.

> Adding "-debug" option to Falcon CLI for debug statements to stdout.
> --------------------------------------------------------------------
>                 Key: FALCON-1477
>                 URL: https://issues.apache.org/jira/browse/FALCON-1477
>             Project: Falcon
>          Issue Type: New Feature
>            Reporter: Narayan Periwal
>            Assignee: Narayan Periwal
>         Attachments: FALCON-1477-v0.patch
> With this feature, users can specify "-debug" in CLI arguments to get the debug statements
in Stdout. 
> eg. falcon entity -type feed -name in-feed.xml -submit -debug
> Also, users can export the env variable FALCON_DEBUG to a non-zero value to get the debug
statements on stdout.
> Starting right now with getting basic debug output such as the Http connection URL to
the server, this can be later extended for printing more debug statements at various stages.

This message was sent by Atlassian JIRA

View raw message