falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1743) Entity summary does not work via prism
Date Thu, 10 Mar 2016 11:25:40 GMT

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

ASF GitHub Bot commented on FALCON-1743:
----------------------------------------

GitHub user ajayyadava opened a pull request:

    https://github.com/apache/falcon/pull/65

    FALCON-1743 Entity summary does not work via prism.

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ajayyadava/falcon 1743

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/falcon/pull/65.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #65
    
----
commit 4eff7e6c15588e05c2f6fc27f73d84e8e2007762
Author: Ajay Yadava <ajaynsit@gmail.com>
Date:   2016-01-29T14:54:33Z

    FALCON-1743 Entity summary does not work via prism.

----


> Entity summary does not work via prism
> --------------------------------------
>
>                 Key: FALCON-1743
>                 URL: https://issues.apache.org/jira/browse/FALCON-1743
>             Project: Falcon
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 0.8, 0.9
>            Reporter: Pragya Mittal
>            Assignee: Ajay Yadava
>
> 1. Entity summary is supposed to show N most recent instances of entity of given cluster.
But that is not the case. It shows output only if query is fired via server. Null object is
returned in case of prism.
> For prism :
> {noformat}
> dataqa@lda01:~$ falcon entity -type process -cluster ProcessMultipleClustersTest-corp-3aae3ae9
-summary -url http://192.168.138.236:16000
> Consolidated Status: SUCCEEDED
> Entity Summary Result :
> Additional Information:
> Response: Entity Summary ResultRequest Id: 878228784@qtp-477289012-155 - c29758fa-10a4-4d22-b5ee-1946f11d7ac1
> {noformat}
> 2. Giving cluster with start and end parameter on prism fails with the following error.
> {noformat}
> dataqa@lda01:~$ falcon entity -type process -cluster ProcessMultipleClustersTest-corp-54289831
-summary -start 2016-01-08T12:38Z -end 2016-01-08T14:18Z
> ERROR: Bad Request;Current colo (default) is not ua1
> {noformat}
> Prism logs stack trace :
> {noformat}
> 2016-01-11 13:46:48,568 INFO  - [878228784@qtp-477289012-155 - 7a9795a5-db9b-4b7c-8344-43db3368fe95:dataqa:GET//entities/summary/process]
~ Request from authenticated user: dataqa, URL=/api/entities/summary/process?cluster=ProcessMultipleClustersTest-corp-54289831&start=2016-01-08T12:38Z&end=2016-01-08T14:18Z&offset=0&numInstances=7,
doAs user: null (FalconAuthenticationFilter:185)
> 2016-01-11 13:46:48,569 ERROR - [878228784@qtp-477289012-155 - 7a9795a5-db9b-4b7c-8344-43db3368fe95:dataqa:GET//entities/summary/process]
~ Action failed: Bad Request
> Error: Current colo (default) is not ua1 (FalconWebException:81)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message