You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "lan xiaoming (JIRA)" <ji...@apache.org> on 2018/04/26 02:26:00 UTC

[jira] [Commented] (RANGER-1466) Tag sync doesn't give enough information when there is error

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

lan xiaoming commented on RANGER-1466:
--------------------------------------

Hi,Dear Don Bosco Durai ,what version of ranger are you using when encounter this bug?We encounter this bug when using ranger version 1.1.is there any stable version of ranger ?we use both ranger and atlas.

> Tag sync doesn't give enough information when there is error
> ------------------------------------------------------------
>
>                 Key: RANGER-1466
>                 URL: https://issues.apache.org/jira/browse/RANGER-1466
>             Project: Ranger
>          Issue Type: Improvement
>          Components: tagsync
>            Reporter: Don Bosco Durai
>            Assignee: Don Bosco Durai
>            Priority: Major
>
> Debugging is a challenge for tag sync. There are couple of places more information would be useful.
> 21 Mar 2017 02:29:40 ERROR TagAdminRESTSink [Thread-8] - 177 Upload of service-tags failed with message HTTP 400
> java.lang.Exception: attributes clusterName, qualifiedName' not found in entity
>                 at org.apache.ranger.tagsync.source.atlas.AtlasResourceMapper.throwExceptionWithMessage(AtlasResourceMapper.java:119)
>                 at 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)