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

Balu Vellanki updated FALCON-859:
---------------------------------
    Attachment: FALCON-859.patch

Please review

> EntitySummary RestAPI : Change pathParam "cluster" to queryParam
> ----------------------------------------------------------------
>
>                 Key: FALCON-859
>                 URL: https://issues.apache.org/jira/browse/FALCON-859
>             Project: Falcon
>          Issue Type: Bug
>          Components: webapp
>    Affects Versions: 0.6
>            Reporter: Balu Vellanki
>            Assignee: Balu Vellanki
>             Fix For: 0.6
>
>         Attachments: FALCON-859.patch
>
>
> All entity and instance Rest APIs have the following path structure 
> api/<resource>/<action>/<?entityName>/<?entityType>, where 
> - resource can be "entities" or "instance.
> - action : the action to be performed, like "list", "summary", "suspend" etc
> - entityName and entityType are optional
> EntitySummary is the only Rest API that does not adhere to this format. This 
> causes authorization error.
> {code}
> Problem accessing /api/entities/summary/process/primaryCluster. Reason:
>     INTERNAL_SERVER_ERROR
> Caused by:
> org.apache.falcon.FalconWebException
>       at 
> org.apache.falcon.FalconWebException.newException(FalconWebException.java:70)
>       at 
> org.apache.falcon.security.FalconAuthorizationFilter.doFilter(FalconAuthorizationFilter.java:76)
>       at 
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
>       at 
> org.apache.falcon.security.FalconAuthenticationFilter$2.doFilter(FalconAuthenticationFilter.java:184)
>       at 
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:572)
>       at 
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:542)
> {code}



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

Reply via email to