[jira] [Updated] (ATLAS-1103) UI: Search type list is not refreshed

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1103:

Fix Version/s: 0.7.1-incubating

Committed to 0.7-incubating branch: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/1340bfc5

> UI: Search type list is not refreshed
> -
>
> Key: ATLAS-1103
> URL: https://issues.apache.org/jira/browse/ATLAS-1103
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Kalyani Kashikar
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-1103.patch
>
>
> The list of types fetched for DSL search is done on main page rendering and 
> not when the drop down is clicked. So, if a type is created after the main UI 
> page is opened, the type list is not refreshed



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

[jira] [Updated] (ATLAS-1099) UI : multiple tag assign button hides wrongly

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1099:

Affects Version/s: 0.7-incubating
Fix Version/s: (was: 0.7-incubating)
   0.7.1-incubating
   0.8-incubating

Committed to 0.7-incubating branch: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/cb28bb4f

> UI : multiple tag assign button hides wrongly
> -
>
> Key: ATLAS-1099
> URL: https://issues.apache.org/jira/browse/ATLAS-1099
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Kalyani Kashikar
>Assignee: Kalyani Kashikar
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-1099.patch
>
>
> Step to reproduce:
>  After selecting multiple tags to assign with entity, even if we de-select 
> one tag, "Assign Tags" button gets hidden. 



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

[jira] [Updated] (ATLAS-1105) Disable HiveLiteralRewriterTest since its not used currently

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1105:

Fix Version/s: 0.7.1-incubating

Committed in 0.7-incubating branch: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/368a2f90

> Disable HiveLiteralRewriterTest since its not used currently
> 
>
> Key: ATLAS-1105
> URL: https://issues.apache.org/jira/browse/ATLAS-1105
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-1105.patch
>
>
> Disable test since HiveLiteralRewriter is no longer used in 
> HiveHook.getProcessQualifiedName



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

[jira] [Updated] (ATLAS-1104) Get outgoing edges by label doesn't work in some cases

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1104:

Fix Version/s: 0.7.1-incubating

Committed to 0.7-incubating branch: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/0cfd957d

> Get outgoing edges by label doesn't work in some cases
> --
>
> Key: ATLAS-1104
> URL: https://issues.apache.org/jira/browse/ATLAS-1104
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Shwetha G S
>Priority: Critical
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-1104.1.patch, ATLAS-1104.patch
>
>
> In one of the concurrent API scenario of add trait APIs and search API, the 
> edge for add trait was added, but get edge by label doesn't return the edge. 



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

[jira] [Comment Edited] (ATLAS-1108) In Atlas HA mode , import-hive.sh in Passive instance fails.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj edited comment on ATLAS-1108 at 1/4/17 7:53 AM:
-

Committed in 0.7-incubating branch:
- http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/e1b108f6
- http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/f1e8906a


was (Author: madhan.neethiraj):
Committed in 0.7-incubating branch: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/f1e8906a

> In Atlas HA mode , import-hive.sh in Passive instance fails.
> 
>
> Key: ATLAS-1108
> URL: https://issues.apache.org/jira/browse/ATLAS-1108
> Project: Atlas
>  Issue Type: Bug
>Reporter: Sharmadha Sainath
>Assignee: Ayub Khan
>Priority: Critical
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-1108-1.patch, ATLAS-1108.patch
>
>
> rest address configuration in atlas-application.properties is not present in 
> hive 's conf directory . Hence , in passive instance , makes a call to 
> localhost and import-hive.sh fails.



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

[jira] [Updated] (ATLAS-1112) Hive table GET response from atlas server had duplicate column entries

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1112:

Fix Version/s: 0.7.1-incubating

Committed to 0.7-incubating branch: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/f8bdac05

> Hive table GET response from atlas server had duplicate column entries
> --
>
> Key: ATLAS-1112
> URL: https://issues.apache.org/jira/browse/ATLAS-1112
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Ayub Khan
>Assignee: Ayub Khan
>Priority: Critical
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-1112-1.patch, ATLAS-1112-2.patch, ATLAS-1112.patch
>
>
> Atlas server overwrites the entities when entity create message is sent with 
> duplicate ID. 
> In this case, HiveHook uses system.nanotime() for generating the ID for 
> entities which does not guarantee the uniqueness of ID string. So, hiveHook 
> creates an entity with duplicate id for columns(not all times) - which 
> results in overwriting the columns and hence duplicate columns are seen.
> For example: One such entity create message seen from hiveHook is
> {noformat}
> {
>   
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
>   "id":{
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"-8986778765230",
> "version":0,
> "typeName":"hive_db",
> "state":"ACTIVE"
>   },
>   "typeName":"hive_db",
>   "values":{
> "name":"default",
> 
> "location":"hdfs://nat-r6-itvs-atlas-1.openstacklocal:8020/apps/hive/warehouse",
> "description":"Default Hive database",
> "ownerType":2,
> "qualifiedName":"default@cl1",
> "owner":"public",
> "clusterName":"cl1",
> "parameters":{
>   
> }
>   },
>   "traitNames":[
> 
>   ],
>   "traits":{
> 
>   }
> },{
>   
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
>   "id":{
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"-8986813055475",
> "version":0,
> "typeName":"hive_table",
> "state":"ACTIVE"
>   },
>   "typeName":"hive_table",
>   "values":{
> "tableType":"MANAGED_TABLE",
> "name":"allparams1px9g6chqv",
> "createTime":"2016-08-10T04:26:50.000Z",
> "temporary":false,
> "db":{
>   
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
>   "id":{
> 
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"-8986778765230",
> "version":0,
> "typeName":"hive_db",
> "state":"ACTIVE"
>   },
>   "typeName":"hive_db",
>   "values":{
> "name":"default",
> 
> "location":"hdfs://nat-r6-itvs-atlas-1.openstacklocal:8020/apps/hive/warehouse",
> "description":"Default Hive database",
> "ownerType":2,
> "qualifiedName":"default@cl1",
> "owner":"public",
> "clusterName":"cl1",
> "parameters":{
>   
> }
>   },
>   "traitNames":[
> 
>   ],
>   "traits":{
> 
>   }
> },
> "retention":0,
> "qualifiedName":"default.allparams1px9g6chqv@cl1",
> "columns":[
>   {
> 
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "id":{
>   
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>   "id":"-8986813593492",
>   "version":0,
>   "typeName":"hive_column",
>   "state":"ACTIVE"
> },
> "typeName":"hive_column",
> "values":{
>   "name":"inttype",
>   "qualifiedName":"default.allparams1px9g6chqv.inttype@cl1",
>   "owner":"hrt_qa",
>   "type":"int",
>   "table":{
> 
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"-8986813055475",
> "version":0,
> "typeName":"hive_table",
> "state":"ACTIVE"
>   }
> },
> "traitNames":[
>   
> ],
> "traits":{
>   
> }
>   },
>   {
> 
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "id":{
>   
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>   "id":"-8986813606611",
>   "version":0,
>   "typeName":"hive_column",
>   "state":"ACTIVE"
> },
> "typeName":"hive_column",
> "values":{
>   "name":"tinyinttype",
>   "qualifiedName":"default.allparams1px9g6chqv.tinyinttype@cl1",
>   "ow

[jira] [Updated] (ATLAS-1115) Show Tag / Taxonomy Listing in sorted order

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1115:

Fix Version/s: 0.7.1-incubating

Committed in 0.7-incubating branch: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/7d819153

> Show Tag / Taxonomy Listing in sorted order
> ---
>
> Key: ATLAS-1115
> URL: https://issues.apache.org/jira/browse/ATLAS-1115
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Kalyani Kashikar
>Priority: Minor
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-1115.patch
>
>
> To show tag, taxonomy drop-down listing in sorted order. so that it is 
> uniform across atlas application.



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

[jira] [Updated] (ATLAS-1108) In Atlas HA mode , import-hive.sh in Passive instance fails.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1108:

Fix Version/s: 0.7.1-incubating

Committed in 0.7-incubating branch: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/f1e8906a

> In Atlas HA mode , import-hive.sh in Passive instance fails.
> 
>
> Key: ATLAS-1108
> URL: https://issues.apache.org/jira/browse/ATLAS-1108
> Project: Atlas
>  Issue Type: Bug
>Reporter: Sharmadha Sainath
>Assignee: Ayub Khan
>Priority: Critical
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-1108-1.patch, ATLAS-1108.patch
>
>
> rest address configuration in atlas-application.properties is not present in 
> hive 's conf directory . Hence , in passive instance , makes a call to 
> localhost and import-hive.sh fails.



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

[jira] [Updated] (ATLAS-1111) Data loss is observed when atlas is restarted while hive_table metadata ingestion into kafka topic is in-progress

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-:

Fix Version/s: 0.7.1-incubating

Committed to 0.7-incubating branch: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/9ea1ad6d

> Data loss is observed when atlas is restarted while hive_table metadata 
> ingestion into kafka topic is in-progress
> -
>
> Key: ATLAS-
> URL: https://issues.apache.org/jira/browse/ATLAS-
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Sharmadha Sainath
>Assignee: Shwetha G S
>Priority: Critical
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-.1.patch, ATLAS-.2.patch, 
> ATLAS-.3.patch, ATLAS-.4.patch, ATLAS-.5.patch, ATLAS-.patch
>
>
> During atlas stop, the graph is shutdown first and then the services like 
> NotificationHookConsumer is shutdown. After graph is shutdown and before 
> NotificationHookConsumer is shutdown, the message handling fails as the graph 
> is down, but the NotificationHookConsumer commits the message(updating the 
> offset). So, the messages during this time are lost



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

[jira] [Updated] (ATLAS-1121) NPE while submitting topology in StormHook

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1121:

Fix Version/s: 0.7.1-incubating

Committed in 0.7-incubating branch: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/dea202ca

> NPE while submitting topology in StormHook
> --
>
> Key: ATLAS-1121
> URL: https://issues.apache.org/jira/browse/ATLAS-1121
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Ayub Khan
>Assignee: Ayub Khan
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-1121-1.patch, ATLAS-1121.patch, Atlas 2016-08-16 
> 19-48-59.png
>
>
> NPE while submitting topology in StormHook
> {code}
> [storm@ctr-e25-1471039652053-0001-01-09 erie]$ storm jar 
> hcube-storm-topology-0.0.1.jar org.hw.hcube.storm.LogStreamingToplogyV2 
> phoenix.properties 
> Running: /usr/jdk64/jdk1.8.0_60/bin/java -server -Ddaemon.name= 
> -Dstorm.options= -Dstorm.home=/usr/hdp/2.5.0.0-1201/storm 
> -Dstorm.log.dir=/var/log/storm 
> -Djava.library.path=/usr/local/lib:/opt/local/lib:/usr/lib -Dstorm.conf.file= 
> -cp 
> /usr/hdp/2.5.0.0-1201/storm/lib/log4j-slf4j-impl-2.1.jar:/usr/hdp/2.5.0.0-1201/storm/lib/clojure-1.7.0.jar:/usr/hdp/2.5.0.0-1201/storm/lib/servlet-api-2.5.jar:/usr/hdp/2.5.0.0-1201/storm/lib/log4j-api-2.1.jar:/usr/hdp/2.5.0.0-1201/storm/lib/objenesis-2.1.jar:/usr/hdp/2.5.0.0-1201/storm/lib/minlog-1.3.0.jar:/usr/hdp/2.5.0.0-1201/storm/lib/storm-core-1.0.1.2.5.0.0-1201.jar:/usr/hdp/2.5.0.0-1201/storm/lib/log4j-over-slf4j-1.6.6.jar:/usr/hdp/2.5.0.0-1201/storm/lib/disruptor-3.3.2.jar:/usr/hdp/2.5.0.0-1201/storm/lib/zookeeper.jar:/usr/hdp/2.5.0.0-1201/storm/lib/slf4j-api-1.7.7.jar:/usr/hdp/2.5.0.0-1201/storm/lib/asm-5.0.3.jar:/usr/hdp/2.5.0.0-1201/storm/lib/reflectasm-1.10.1.jar:/usr/hdp/2.5.0.0-1201/storm/lib/log4j-core-2.1.jar:/usr/hdp/2.5.0.0-1201/storm/lib/ring-cors-0.1.5.jar:/usr/hdp/2.5.0.0-1201/storm/lib/kryo-3.0.3.jar:/usr/hdp/2.5.0.0-1201/storm/lib/storm-rename-hack-1.0.1.2.5.0.0-1201.jar:/usr/hdp/2.5.0.0-1201/storm/lib/ambari-metrics-storm-sink.jar:/usr/hdp/2.5.0.0-1201/storm/extlib/storm-bridge-shim-0.7.0.2.5.0.0-1201.jar:/usr/hdp/2.5.0.0-1201/storm/extlib/atlas-plugin-classloader-0.7.0.2.5.0.0-1201.jar
>  org.apache.storm.daemon.ClientJarTransformerRunner 
> org.apache.storm.hack.StormShadeTransformer hcube-storm-topology-0.0.1.jar 
> /tmp/9e206b70636a11e685530242ac1b1bc0.jar
> Running: /usr/jdk64/jdk1.8.0_60/bin/java -client -Ddaemon.name= 
> -Dstorm.options= -Dstorm.home=/usr/hdp/2.5.0.0-1201/storm 
> -Dstorm.log.dir=/var/log/storm 
> -Djava.library.path=/usr/local/lib:/opt/local/lib:/usr/lib:/usr/hdp/current/storm-client/lib
>  -Dstorm.conf.file= -cp 
> /usr/hdp/2.5.0.0-1201/storm/lib/log4j-slf4j-impl-2.1.jar:/usr/hdp/2.5.0.0-1201/storm/lib/clojure-1.7.0.jar:/usr/hdp/2.5.0.0-1201/storm/lib/servlet-api-2.5.jar:/usr/hdp/2.5.0.0-1201/storm/lib/log4j-api-2.1.jar:/usr/hdp/2.5.0.0-1201/storm/lib/objenesis-2.1.jar:/usr/hdp/2.5.0.0-1201/storm/lib/minlog-1.3.0.jar:/usr/hdp/2.5.0.0-1201/storm/lib/storm-core-1.0.1.2.5.0.0-1201.jar:/usr/hdp/2.5.0.0-1201/storm/lib/log4j-over-slf4j-1.6.6.jar:/usr/hdp/2.5.0.0-1201/storm/lib/disruptor-3.3.2.jar:/usr/hdp/2.5.0.0-1201/storm/lib/zookeeper.jar:/usr/hdp/2.5.0.0-1201/storm/lib/slf4j-api-1.7.7.jar:/usr/hdp/2.5.0.0-1201/storm/lib/asm-5.0.3.jar:/usr/hdp/2.5.0.0-1201/storm/lib/reflectasm-1.10.1.jar:/usr/hdp/2.5.0.0-1201/storm/lib/log4j-core-2.1.jar:/usr/hdp/2.5.0.0-1201/storm/lib/ring-cors-0.1.5.jar:/usr/hdp/2.5.0.0-1201/storm/lib/kryo-3.0.3.jar:/usr/hdp/2.5.0.0-1201/storm/lib/storm-rename-hack-1.0.1.2.5.0.0-1201.jar:/usr/hdp/2.5.0.0-1201/storm/lib/ambari-metrics-storm-sink.jar:/usr/hdp/2.5.0.0-1201/storm/extlib/storm-bridge-shim-0.7.0.2.5.0.0-1201.jar:/usr/hdp/2.5.0.0-1201/storm/extlib/atlas-plugin-classloader-0.7.0.2.5.0.0-1201.jar:/tmp/9e206b70636a11e685530242ac1b1bc0.jar:/usr/hdp/current/storm-supervisor/conf:/usr/hdp/2.5.0.0-1201/storm/bin
>  -Dstorm.jar=/tmp/9e206b70636a11e685530242ac1b1bc0.jar 
> org.hw.hcube.storm.LogStreamingToplogyV2 phoenix.properties
> 1269 [main] INFO  o.a.s.StormSubmitter - Generated ZooKeeper secret payload 
> for MD5-digest: -5580857394466738431:-5449170806113196196
> 1320 [main] INFO  o.a.s.s.a.AuthUtils - Got AutoCreds []
> 1533 [main] INFO  o.a.s.m.n.Login - successfully logged in.
> 1682 [main] INFO  o.a.s.m.n.Login - successfully logged in.
> 1710 [main] INFO  o.a.s.m.n.Login - successfully logged in.
> 1738 [main] INFO  o.a.s.m.n.Login - successfully logged in.
> 1765 [main] INFO  o.a.s.StormSubmitter - Uploading topology jar 
> /tmp/9e206b70636a11e685530242ac1b1bc0.jar to assigned location: 
> /hadoop/storm/nimbus/inbox/stormjar-2d8edcfa-000b-41d3-a170-9982b45867c0.jar
> Start uploading file '/tmp/9e206b70636a11e685530242ac1b1bc0.jar' to 

[jira] [Updated] (ATLAS-1122) Change trait edge labels to have trait name alone

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1122:

Fix Version/s: 0.7.1-incubating

Committed in 0.7-incubating branch: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/dea202ca

> Change trait edge labels to have trait name alone
> -
>
> Key: ATLAS-1122
> URL: https://issues.apache.org/jira/browse/ATLAS-1122
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-1122.2.patch, ATLAS-1122.patch
>
>
> Currently when traits are added to classes they are added with 
> {{typeName.traitName}} and this is causing edge label creation to fail when 
> concurrent threads are running transactions. Event though adding retries 
> mitigates the issue to some extent in ATLAS-1119 and lets the transactions 
> succeed, there is lesser chance of them failing with edge label creation due 
> to concurrent transactions with the proposed change since this is a one time 
> operation that is done once per  trait when it is added the first time to any 
> entity. Also this could potentially be moved to type creation phase when the 
> trait is created.



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

[jira] [Updated] (ATLAS-1125) Enable compression on hbase audit table

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1125:

Fix Version/s: 0.7.1-incubating

Committed in 0.7-incubating branch: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/e0a0e25a

> Enable compression on hbase audit table
> ---
>
> Key: ATLAS-1125
> URL: https://issues.apache.org/jira/browse/ATLAS-1125
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Shwetha G S
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-1125.1.patch, ATLAS-1125.patch
>
>




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

[jira] [Updated] (ATLAS-675) Storm Hook should use timetsamps as Date type instead of Long

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-675:
---
Fix Version/s: 0.7.1-incubating

Committed to 0.7-incubating branch: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/1eb2c877

> Storm Hook should use timetsamps as Date type instead of Long
> -
>
> Key: ATLAS-675
> URL: https://issues.apache.org/jira/browse/ATLAS-675
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk, 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Ayub Khan
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-675-1.patch, ATLAS-675-2.patch, ATLAS-675-3.patch, 
> ATLAS-675.patch, Atlas 2016-08-18 15-24-55.png
>
>
> Storm topology startTime and endTime should be of type Date



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

[jira] [Updated] (ATLAS-674) Falcon Hook should use timestamps instead of long

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-674:
---
Fix Version/s: 0.7.1-incubating

Committed in 0.7-incubating branch: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/d82224d9

> Falcon Hook should use timestamps instead of long
> -
>
> Key: ATLAS-674
> URL: https://issues.apache.org/jira/browse/ATLAS-674
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Ayub Khan
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-674-1.patch, ATLAS-674-2.patch, ATLAS-674.patch
>
>
> For eg: TIMESTAMP attribute is of type LONG. should be of type Date.



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

[jira] [Updated] (ATLAS-1129) Remove notification failed logs on retry and add sleep between retries

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1129:

Fix Version/s: 0.7.1-incubating

Committed to 0.7-incubating branch: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/56d92cbb

> Remove notification failed logs on retry and add sleep between retries
> --
>
> Key: ATLAS-1129
> URL: https://issues.apache.org/jira/browse/ATLAS-1129
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Vimal Sharma
>Assignee: Vimal Sharma
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-1129-v2.patch, ATLAS-1129-v3.patch, 
> ATLAS-1129.3.patch, ATLAS-1129.patch
>
>
> Atlas notification interface logs the exception if it cannot send the message 
> successfully. Further, the retries are attempted immediately.
> Remove the exception logs for individual retry and add sleep between retries



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

[jira] [Updated] (ATLAS-1126) Fix NPE in getSchema calls

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1126:

Fix Version/s: 0.7.1-incubating

Committed in 0.7-incubating branch: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/03dd1384

> Fix NPE in getSchema calls 
> ---
>
> Key: ATLAS-1126
> URL: https://issues.apache.org/jira/browse/ATLAS-1126
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-1126.2.patch, ATLAS-1126.3.patch, ATLAS-1126.patch
>
>
> Lineage /schema API results in NPE when the config entry for a entity without 
> schema query is not found. 



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

[jira] [Updated] (ATLAS-1141) UI-Issue - Tag with spaces, when searched, then it is wrongly set in search textbox.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1141:

Fix Version/s: 0.7.1-incubating
   0.8-incubating

Committed to master: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/0023236f
Committed to 0.7-incubating: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/b52ad646

> UI-Issue - Tag with spaces, when searched, then it is wrongly set in search 
> textbox.
> 
>
> Key: ATLAS-1141
> URL: https://issues.apache.org/jira/browse/ATLAS-1141
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Kalyani Kashikar
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-1141.1.patch, ATLAS-1141.patch
>
>
> If a Tag is created with space i.e "Tags for Test" and through "Search Tag" 
> link it is searched, then in search box it only displays " for Test` " 
> instead ​ of whole Tag name



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

[jira] [Updated] (ATLAS-1140) All the tag's attributes are not seen while applying a tag to entity.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1140:

Fix Version/s: 0.7.1-incubating
   0.8-incubating

Committed to master: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/a2c3faad
Committed to 0.7-incubating: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/9f5027b6

> All the tag's attributes are not seen while applying a tag to entity.
> -
>
> Key: ATLAS-1140
> URL: https://issues.apache.org/jira/browse/ATLAS-1140
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Keval Bhatt
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-1140.patch
>
>
> All the tag attributes (self + inherited ) are not while adding its value 
> when tag is applied to an entity, the tag was created with attribute 
> inherited from other tag.
> Steps to reproduce the issue.
> 1.Create a Tag with Attribute e.g Tag - T1, Attribute - A1 & Attribute - A2
> 2.Create another Tag having parent Tag as T1 and few Attribute e.g Tag 2 - 
> T2, Attribute - A3 & Attribute - A4
> 3.Now go to any entity and click on it Add tag button
> 4.Now select second Tag i.e T2
> Error:-
> Only attribute A1 and A2 (ie inheritated one's) are displayed, Second Tag(T2) 
> Attributes (A3 & A4) are not displayed"



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

[jira] [Updated] (ATLAS-772) Ordering of columns is not maintained in schema query response, where as hive table entity response maintains the ordering

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-772:
---
Fix Version/s: (was: 0.7-incubating)
   0.7.1-incubating
   0.8-incubating

Committed to master: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/e817b214
Committed to 0.7-incubating: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/049e56ba

> Ordering of columns is not maintained in schema query response, where as hive 
> table entity response maintains the ordering
> --
>
> Key: ATLAS-772
> URL: https://issues.apache.org/jira/browse/ATLAS-772
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Ayub Khan
>Assignee: Sarath Subramanian
>  Labels: patch
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-772.patch
>
>
> Ordering of columns is not maintained in schema query response, where as hive 
> table entity response maintains the ordering
> Table schema
> {noformat}
> 0: jdbc:hive2://localhost:1/default> describe formatted table_pbrscdldkm;
> +---+--++--+
> |   col_name|  data_type  
>  |comment |
> +---+--++--+
> | # col_name| data_type   
>  | comment|
> |   | NULL
>  | NULL   |
> | viewtime  | int 
>  ||
> | userid| bigint  
>  ||
> | page_url  | string  
>  ||
> | referrer_url  | string  
>  ||
> | ip| string  
>  ||
> |   | NULL
>  | NULL   |
> | # Partition Information   | NULL
>  | NULL   |
> | # col_name| data_type   
>  | comment|
> |   | NULL
>  | NULL   |
> | dt| string  
>  ||
> | country   | string  
>  | partitioned columns comments.  |
> |   | NULL
>  | NULL   |
> | # Detailed Table Information  | NULL
>  | NULL   |
> | Database: | db2pbrscdldkm   
>  | NULL   |
> | Owner:| apathan 
>  | NULL   |
> | CreateTime:   | Tue May 10 16:36:56 IST 2016
>  | NULL   |
> | LastAccessTime:   | UNKNOWN 
>  | NULL   |
> | Protect Mode: | None
>  | NULL   |
> | Retention:| 0   
>  | NULL

[jira] [Updated] (ATLAS-1147) UI: column name doesn't show up in schema tab for hive table

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1147:

Fix Version/s: 0.7.1-incubating
   0.8-incubating

Committed to 0.7-incubating branch: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/edfa009c

> UI: column name doesn't show up in schema tab for hive table
> 
>
> Key: ATLAS-1147
> URL: https://issues.apache.org/jira/browse/ATLAS-1147
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Kalyani Kashikar
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-1147.patch, SchemaLayoutView.js, Screen Shot 
> 2016-08-30 at 9.21.07 PM.png
>
>




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

[jira] [Updated] (ATLAS-1154) Errors in Eclipse with web.xml

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1154:

Affects Version/s: 0.7.1-incubating

Committed to 0.7-incubating branch: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/120e4b97

> Errors in Eclipse with web.xml
> --
>
> Key: ATLAS-1154
> URL: https://issues.apache.org/jira/browse/ATLAS-1154
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating, 0.7.1-incubating
>Reporter: David Radley
>Assignee: David Radley
> Fix For: 0.8-incubating
>
> Attachments: atlas1154.patch
>
>
> I have set up a development environment in Eclipse. I notice that the project 
> atlas-webapp has 2 errors like this :
> The content of element type "web-app" must match 
> "(icon?,display-name?,description?,distributable?,context-param*,filter*,filter-mapping*,listener*,servlet*,servlet-
>  
> mapping*,session-config?,mime-mapping*,welcome-file-list?,error-page*,taglib*,resource-env-ref*,resource-ref*,security-constraint*,login-config?,security-role*,env-entry*,ejb-
>  ref*,ejb-local-ref*)".
> The reason for the error is that the xml elements were filter, filter 
> mapping, filter, filter mapping. This does not match the DTD element order 
> (which Eclipse seems to be policing).  If I move the elements so all the 
> filters are next to each other - there are no errors.
> Like this : 
> {noformat}
> 
> springSecurityFilterChain
> 
> org.springframework.web.filter.DelegatingFilterProxy
> 
> 
> guiceFilter
> com.google.inject.servlet.GuiceFilter
> 
> 
> springSecurityFilterChain
> /*
> 
> 
> guiceFilter
> /*
> 
> {noformat}
>



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

[jira] [Updated] (ATLAS-1160) Update Atlas hive hook to read configuration from atlas-application.properties instead of hive-site.xml

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1160:

Fix Version/s: 0.7.1-incubating
   0.8-incubating

Committed to 0.7-incubating branch: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/d0d0f82b

> Update Atlas hive hook to read configuration from 
> atlas-application.properties instead of hive-site.xml
> ---
>
> Key: ATLAS-1160
> URL: https://issues.apache.org/jira/browse/ATLAS-1160
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-1160.patch
>
>
> Atlas hook for Hive reads atlas.hook.hive.synchronous configuration from 
> hive-site.xml. The hook should be updated to read from 
> atlas-application.properties file, to be consistent with other properties 
> like atlas.hook.hive.queueSize, atlas.hook.hive.minThreads, ..



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

[jira] [Updated] (ATLAS-1162) Register shutdown hooks with Hadoop's ShutdownHookManager, instead of directly with Java Runtime

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1162:

Fix Version/s: 0.7.1-incubating

Committed to 0.7-incubating branch: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/d0d0f82b

> Register shutdown hooks with Hadoop's ShutdownHookManager, instead of 
> directly with Java Runtime
> 
>
> Key: ATLAS-1162
> URL: https://issues.apache.org/jira/browse/ATLAS-1162
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-1162.patch
>
>
> Atlas hooks and server currently register a shutdown hook directly with java 
> Runtime object. Hadoop provides an utility class, ShutdownHookManager, which 
> helps to ensure that the hooks are called in a well defined order. Atlas hook 
> registration should be updated to register its shutdown hook with Hadoop's 
> ShutdownHookManager:
> https://github.com/apache/hadoop/blob/master/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/ShutdownHookManager.java.
> Ref: RANGER-891



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

[jira] [Updated] (ATLAS-1149) Changes to UI to sort the hive table schema based on "position" attribute of hive_column

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1149:

Fix Version/s: 0.7.1-incubating
   0.8-incubating

Committed to 0.7-incubating branch: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/8404ac2e

> Changes to UI to sort the hive table schema based on "position" attribute of 
> hive_column
> 
>
> Key: ATLAS-1149
> URL: https://issues.apache.org/jira/browse/ATLAS-1149
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Sarath Subramanian
>Assignee: Kalyani Kashikar
>  Labels: ui
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-1149.1.patch, ATLAS-1149.patch, attach1.json, 
> attach2.json
>
>
> This is related to ATLAS-772, hive column needs to be sorted based on its 
> original column order. New attribute "position" has been added to hive_column 
> type which maintains the column order number. UI needs to use this 
> information to sort the column based on this attribute



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

[jira] [Updated] (ATLAS-1133) Jetty Server start doesn't throw exception when user-credential.properties file is not found

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1133:

Fix Version/s: 0.7.1-incubating
   0.8-incubating

Committed to 0.7-incubating branch: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/ae02a2fa

> Jetty Server start doesn't throw exception when user-credential.properties 
> file is not found
> 
>
> Key: ATLAS-1133
> URL: https://issues.apache.org/jira/browse/ATLAS-1133
> Project: Atlas
>  Issue Type: Bug
>Reporter: Vimal Sharma
>Assignee: Nixon Rodrigues
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-1133-1.patch, ATLAS-1133.patch
>
>
> In webapp module, the command mvn jetty:run doesn't throw any exception even 
> when the file user-credentials.properties is not found. The command should 
> throw an exception and jetty server should not start.



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

[jira] [Updated] (ATLAS-1173) Doc: Minor editorial bug in the example given for property atlas.server.ha.zookeeper.auth

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1173:

Fix Version/s: 0.7.1-incubating

Committed to 0.7-incubating branch: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/dc888328

> Doc: Minor editorial bug in the example given for property 
> atlas.server.ha.zookeeper.auth
> -
>
> Key: ATLAS-1173
> URL: https://issues.apache.org/jira/browse/ATLAS-1173
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
>Priority: Minor
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-1173.patch
>
>
> In {{Configuration.twiki}}, we have specified the example for Zookeeper 
> security configs as follows (under the High Availability Properties).
> {code}
> atlas.server.ha.zookeeper.acl=auth:sasl:cli...@comany.com
> {code}
> The auth: prefix in the value is incorrect and should be removed.



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

[jira] [Updated] (ATLAS-712) Support getTrait() API

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-712:
---
Fix Version/s: 0.7.1-incubating

Committed to 0.7-incubating branch: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/0de7ce34

> Support getTrait() API
> --
>
> Key: ATLAS-712
> URL: https://issues.apache.org/jira/browse/ATLAS-712
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Suma Shivaprasad
>Assignee: Vimal Sharma
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-712-v2.patch, ATLAS-712-v3.patch, 
> ATLAS-712-v4.patch, ATLAS-712.patch
>
>
> Given entity id and trait name, support rest API that returns the trait 
> instance for the entity. Currently, the other way of getting it is 
> getEntity() which returns full entity with all trait instances 



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

[jira] [Updated] (ATLAS-1142) Lineage UI Improvement.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1142:

Fix Version/s: 0.7.1-incubating

Committed to 0.7-incubating branch: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/a8307be0

> Lineage UI Improvement.
> ---
>
> Key: ATLAS-1142
> URL: https://issues.apache.org/jira/browse/ATLAS-1142
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nixon Rodrigues
>Assignee: Keval Bhatt
>Priority: Minor
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-1142.1.patch, ATLAS-1142.patch, Screen Shot 
> 2016-09-15 at 2.16.57 PM.png
>
>
> Following improvement to be done in Lineage UI & entity detail page
> * Lineage UI should be resizable.
> * All the nodes to be shown in format *name (typename)*



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

[jira] [Updated] (ATLAS-1098) Atlas allows creation of tag with name "isa" which causes exceptions during search

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1098:

Fix Version/s: 0.7.1-incubating

Fix committed in 0.7-incubating branch:
 - http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/5eaf6b40
 - http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/f0e58eda

> Atlas allows creation of tag with name "isa" which causes exceptions during 
> search
> --
>
> Key: ATLAS-1098
> URL: https://issues.apache.org/jira/browse/ATLAS-1098
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-1098.patch, ATLAS-1098.patch
>
>
> Created a tag with name "isa". DSL query "Table where Table isa isa" throws 
> exception . Search in Tag tab also throws exception.
>  



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

[jira] [Updated] (ATLAS-1206) Atlas UI not working with IE or Chrome on Windows OS in Kerberos mode.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1206:

Fix Version/s: 0.7.1-incubating

Fix committed in 0.7-incubating branch: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/26c14780

> Atlas UI not working with IE or Chrome on Windows OS in Kerberos mode.
> --
>
> Key: ATLAS-1206
> URL: https://issues.apache.org/jira/browse/ATLAS-1206
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-1206.patch
>
>
> Atlas UI works in Firefox browser and NOT with IE or Chrome on Windows OS in 
> Kerberos mode.
> Error:-
> HTTP ERROR 403
> Problem accessing /index.html. Reason:
> GSSException: Defective token detected (Mechanism level: GSSHeader did not 
> find the right tag)



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

[jira] [Updated] (ATLAS-1155) Errors in Eclipse when I bring in the latest code

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1155:

Fix Version/s: 0.7.1-incubating

Fix committed in 0.7-incubating branch: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/6545187d

> Errors in Eclipse when I bring in the latest code
> -
>
> Key: ATLAS-1155
> URL: https://issues.apache.org/jira/browse/ATLAS-1155
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: David Radley
>Assignee: David Radley
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: atlas1155.patch
>
>
> I have brought the latest atlas code into an Eclipse environment and see an 
> error in GraphBackedDiscoveryService, 
> line 154
>  scala.collection.immutable.List.empty()); it says method empty is ambiguous.
> if I replace this expression with null it complies.



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

[jira] [Updated] (ATLAS-1199) Atlas UI not loading after fresh build due to jquery-asBreadcrumbs plugin upgrade.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1199:

Fix Version/s: 0.7.1-incubating

> Atlas UI not loading after fresh build due to jquery-asBreadcrumbs plugin 
> upgrade.
> --
>
> Key: ATLAS-1199
> URL: https://issues.apache.org/jira/browse/ATLAS-1199
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Keval Bhatt
>Priority: Blocker
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-1199.patch
>
>
> Atlas UI not loading after fresh build due jquery-asBreadcrumbs plugin 
> changes.
> Found following error in browser console
> Overrides.js:22 Uncaught TypeError: Cannot set property 
> 'generateChildrenInfo' of undefined
> GET http://localhost:21000/js/libs/jquery-asBreadcrumbs/css/asBreadcrumbs.css 
> 404



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

[jira] [Updated] (ATLAS-1215) Atlas UI not working in firefox due to fix in ATLAS-1199

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1215:

Fix Version/s: 0.7.1-incubating

> Atlas UI not working in firefox due to fix in ATLAS-1199
> 
>
> Key: ATLAS-1215
> URL: https://issues.apache.org/jira/browse/ATLAS-1215
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Blocker
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-1215.patch
>
>




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

[jira] [Updated] (ATLAS-1119) Add retries for edge label creation

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1119:

Fix Version/s: 0.7.1-incubating

Committed in 0.7-incubating branch: 
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/59477783

> Add retries for edge label creation
> ---
>
> Key: ATLAS-1119
> URL: https://issues.apache.org/jira/browse/ATLAS-1119
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-1119.2.patch, ATLAS-1119.patch
>
>
> Concurrent operations will fail when trying to create edge label which tries 
> to define a new property key for the edge label if it doesnt exist. 
> {noformat}
> 2016-08-15 04:08:28,475 DEBUG - [pool-8-thread-1:] ~ Adding a new trait=PII 
> for entity=b1630277-e8dc-4fcf-94af-c0c8b0b51c09 
> (GraphBackedMetadataRepository:222)
> 2016-08-15 04:08:28,476 DEBUG - [pool-8-thread-2:] ~ Adding a new trait=PII 
> for entity=5e335fed-4a74-496d-8521-1678caf85813 
> (GraphBackedMetadataRepository:222)
> 2016-08-15 04:08:28,477 DEBUG - [pool-8-thread-1:] ~ Finding vertex with 
> __guid = b1630277-e8dc-4fcf-94af-c0c8b0b51c09,  (GraphHelper:182)
> 2016-08-15 04:08:28,477 DEBUG - [pool-8-thread-2:] ~ Finding vertex with 
> __guid = 5e335fed-4a74-496d-8521-1678caf85813,  (GraphHelper:182)
> 2016-08-15 04:08:28,477 DEBUG - [pool-8-thread-3:] ~ Executing dsl 
> query=hive_table (GraphBackedDiscoveryService:133)
> 2016-08-15 04:08:28,483 DEBUG - [pool-8-thread-2:] ~ Found a vertex 
> vertex[id=8704 type=hive_database guid=5e335fed-4a74-496d-8521-1678caf85813] 
> with __guid = 5e335fed-4a74-496d-8521-1678caf85813,  (GraphHelper:192)
> 2016-08-15 04:08:28,484 DEBUG - [pool-8-thread-2:] ~ Creating vertex for type 
> PII id null (GraphHelper:97)
> 2016-08-15 04:08:28,485 DEBUG - [pool-8-thread-2:] ~ Setting property 
> __typeName = "PII" to vertex[id=8960 type=null guid=null] (GraphHelper:290)
> 2016-08-15 04:08:28,487 DEBUG - [pool-8-thread-2:] ~ Set property __typeName 
> = "PII" to vertex[id=8960 type=null guid=null] (GraphHelper:300)
> 2016-08-15 04:08:28,487 DEBUG - [pool-8-thread-2:] ~ Setting property __state 
> = "ACTIVE" to vertex[id=8960 type=PII guid=null] (GraphHelper:290)
> 2016-08-15 04:08:28,488 DEBUG - [pool-8-thread-2:] ~ Set property __state = 
> "ACTIVE" to vertex[id=8960 type=PII guid=null] (GraphHelper:300)
> 2016-08-15 04:08:28,488 DEBUG - [pool-8-thread-1:] ~ Found a vertex 
> vertex[id=8448 type=hive_database guid=b1630277-e8dc-4fcf-94af-c0c8b0b51c09] 
> with __guid = b1630277-e8dc-4fcf-94af-c0c8b0b51c09,  (GraphHelper:192)
> 2016-08-15 04:08:28,488 DEBUG - [pool-8-thread-2:] ~ Setting property 
> __timestamp = "1471234108488" to vertex[id=8960 type=PII guid=null] 
> (GraphHelper:290)
> 2016-08-15 04:08:28,489 DEBUG - [pool-8-thread-1:] ~ Creating vertex for type 
> PII id null (GraphHelper:97)
> 2016-08-15 04:08:28,490 DEBUG - [pool-8-thread-2:] ~ Set property __timestamp 
> = "1471234108488" to vertex[id=8960 type=PII guid=null] (GraphHelper:300)
> 2016-08-15 04:08:28,490 DEBUG - [pool-8-thread-2:] ~ Setting property 
> __modificationTimestamp = "1471234108488" to vertex[id=8960 type=PII 
> guid=null] (GraphHelper:290)
> 2016-08-15 04:08:28,490 DEBUG - [pool-8-thread-1:] ~ Setting property 
> __typeName = "PII" to vertex[id=9216 type=null guid=null] (GraphHelper:290)
> 2016-08-15 04:08:28,490 DEBUG - [pool-8-thread-2:] ~ Set property 
> __modificationTimestamp = "1471234108488" to vertex[id=8960 type=PII 
> guid=null] (GraphHelper:300)
> 2016-08-15 04:08:28,491 DEBUG - [pool-8-thread-2:] ~ created vertex 
> vertex[id=8960 type=PII guid=null] for trait PII 
> (TypedInstanceToGraphMapper:665)
> 2016-08-15 04:08:28,492 DEBUG - [pool-8-thread-2:] ~ Mapping instance 
> struct[type=PII] to vertex vertex[id=8960 type=PII guid=null] 
> (TypedInstanceToGraphMapper:181)
> 2016-08-15 04:08:28,492 DEBUG - [pool-8-thread-2:] ~ Setting property 
> __modificationTimestamp = "1471234108488" to vertex[id=8960 type=PII 
> guid=null] (GraphHelper:290)
> 2016-08-15 04:08:28,492 DEBUG - [pool-8-thread-2:] ~ Finding edges for 
> vertex[id=8960 type=PII guid=null] with label hive_database.PII 
> (GraphHelper:201)
> 2016-08-15 04:08:28,493 DEBUG - [pool-8-thread-2:] ~ Adding edge for 
> vertex[id=8704 type=hive_database guid=5e335fed-4a74-496d-8521-1678caf85813] 
> -> label hive_database.PII -> vertex[id=8960 type=PII guid=null] 
> (GraphHelper:122)
> 2016-08-15 04:08:28,493 DEBUG - [pool-8-thread-1:] ~ Set property __typeName 
> = "PII" to vertex[id=9216 type=null guid=null] (GraphHelper:300)
> 2016-08-15 04:08:28,494 DEBUG - [pool-8-thread-1:] ~ Setting property __state 
> = "ACTIVE" to vertex[id=9216 type=PI

[jira] [Commented] (ATLAS-1417) HIveHook: synchronous execution fails to notify

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj commented on ATLAS-1417:
-

+1 for the patch for master

> HIveHook: synchronous execution fails to notify 
> 
>
> Key: ATLAS-1417
> URL: https://issues.apache.org/jira/browse/ATLAS-1417
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-1417.patch
>
>
> Fix regression in ATLAS-1364 which fails to notify in synchronous execution 
> case.



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

[jira] [Commented] (ATLAS-1308) Discovery/Search REST API v2 model and implementation

[Keval Bhatt (JIRA)]

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

Keval Bhatt commented on ATLAS-1308:


[~sarath.ku...@gmail.com] Can you please rebase the patch.

CC [~madhan.neethiraj]

> Discovery/Search REST API v2 model and implementation
> -
>
> Key: ATLAS-1308
> URL: https://issues.apache.org/jira/browse/ATLAS-1308
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.8-incubating
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
> Attachments: ATLAS-1308.3.patch
>
>
> Model and implement the new Discovery REST API's for the following search 
> types:
> * DSL Search
> * Full Text Search
> * Gremlin Search
> and retrieve search results in a structured model using AtlasEntityHeader 
> information.



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

[jira] [Created] (ATLAS-1425) Integrate Discovery/Search API in Atlas UI

[Keval Bhatt (JIRA)]

Keval Bhatt created ATLAS-1425:
--

 Summary: Integrate Discovery/Search API in Atlas UI 
 Key: ATLAS-1425
 URL: https://issues.apache.org/jira/browse/ATLAS-1425
 Project: Atlas
  Issue Type: Sub-task
Reporter: Keval Bhatt
Assignee: Keval Bhatt






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

Re: Hook for Non Supported Data stores

[Hemanth Yamijala]

Hi,

It is possible to write Hooks for new data stores, as long as there is a 
mechanism in the data store (in your case, Impala) to invoke a class / method 
when there is a change to metadata. For all hooks that currently exist (Hive, 
Storm, Falcon, Sqoop) we have leveraged such plugin mechanisms exposed by the 
hosting systems.

I am not familiar with Impala to answer if such a plugin mechanism exists. 
Perhaps you could check with the Impala integration APIs and see. If not, there 
are other alternatives we can discuss on how you can integrate with Atlas, 
still.

Thanks
hemanth

From: Karthik K 
Sent: Tuesday, January 03, 2017 3:45 PM
To: dev@atlas.incubator.apache.org
Subject: Hook for Non Supported Data stores

Team,

Is there we could write or extend Hook for non supported data store like
Impala.

Hive, HDFS, Kafka, Storm are supported now but would like to know if i have
Impala table and will it be possible to create hook for the same.

Thanks & Regards,
K.Karthikeyan

[jira] [Commented] (ATLAS-1416) UI: It would be nice to sort the properties in the details page of an entity by name

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-1416:
-

[~davidrad], I was thinking of the sort functionality in the UI. I was however 
imagining they would be pre-sorted, but maybe having an explicit sort would 
work too. To be clear, the JIRA is only about the UX, and nothing to do with 
the API.

> UI: It would be nice to sort the properties in the details page of an entity 
> by name
> 
>
> Key: ATLAS-1416
> URL: https://issues.apache.org/jira/browse/ATLAS-1416
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Hemanth Yamijala
>
> The Atlas UI has a Details page for every entity. In the "Properties" tab of 
> this pane, it currently enumerates all properties of the entity. Currently 
> the order seems random and hence is not very easy to grok. It would be nice 
> to have these sorted by property name to make location of required details 
> easier.



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

Re: searching for entities with tags by name

[Hemanth Yamijala]

Hi,

I suspect the tag you searched for is a business term under a taxonomy, and not 
a regular tag. If yes, this behavior can be explained.

It is a by-product of how business terms are implemented today. AFAIK, they are 
implemented as traits. For regular traits (or tags), new instances are created 
whenever they are associated with an entity. However, terms are 'singleton' 
traits, i.e only one instance is created and this is looked up and associated 
with entities whenever the term association happens. The singleton instance is 
attached to the 'Taxonomy' instance by the Business Taxonomy implementation as 
a way of easily looking it up when required for association.

The side effect of this, is that when we search for a business term - because 
it is a tag, the search API gets both objects (the actual association and the 
implicit Taxonomy object association) in the results.

You must not see this behavior for regular tags.

Thanks
Hemanth

From: Avi Levi 
Sent: Wednesday, December 28, 2016 5:45 PM
To: dev@atlas.incubator.apache.org
Subject: searching for entities with tags by name

Hi

According to the documentation, searching for entities that are
associated to tags is done using the search/dsl api:

http:/// api/atlas/
discovery/search/dsl?query= %60tag-name%60

in the documentation the response contains one instance in the
results, but when I execute the api call, I get two instances in the
results, one of them
is the actual entity that I've tagged, and the other one is an object
of type Taxonomy.

can anyone explain this behavior ?

thanks

Build failed in Jenkins: apache-atlas-nightly #532

[Apache Jenkins Server]

See 

Changes:

[madhan] ATLAS-1391 Add exclusion mechanism for Atlas audit

--
[...truncated 6968 lines...]
127.0.0.1 - - [04/Jan/2017:02:52:40 +] "GET 
/api/atlas/entities?type=hive_table&property=qualifiedName&value=default.tablexckyoq7py8@primary
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jan/2017:02:52:40 +] "GET 
/api/atlas/entities?type=hive_process&property=qualifiedName&value=TRUNCATETABLE-%3E:default.tablexckyoq7py8@primary:1483498355000
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jan/2017:02:52:40 +] "GET 
/api/atlas/entities?type=hive_process&property=qualifiedName&value=TRUNCATETABLE-%3E:default.tablexckyoq7py8@primary:1483498355000
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jan/2017:02:52:40 +] "GET 
/api/atlas/entities/f8c081fe-f3c2-412b-81f3-de1c601c0d20 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [04/Jan/2017:02:52:40 +] "GET 
/api/atlas/entities/ec10f38b-5797-4349-8260-3a9090e3eefd HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [04/Jan/2017:02:52:40 +] "GET 
/api/atlas/lineage/hive/table/default.tablexckyoq7py8@primary/inputs/graph 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jan/2017:02:52:45 +] "GET 
/api/atlas/entities?type=hive_process&property=qualifiedName&value=QUERY:default.tableacx4kda8s4@primary:1483498363000-%3E:PATH_WRITE
 HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jan/2017:02:52:50 +] "GET 
/api/atlas/entities?type=hive_process&property=qualifiedName&value=QUERY:default.tableacx4kda8s4@primary:1483498363000-%3E:PATH_WRITE
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jan/2017:02:52:50 +] "GET 
/api/atlas/entities?type=hive_process&property=qualifiedName&value=QUERY:default.tableacx4kda8s4@primary:1483498363000-%3E:PATH_WRITE
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jan/2017:02:52:50 +] "GET 
/api/atlas/entities/2bee6315-689b-4843-a301-6828418c211d HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [04/Jan/2017:02:52:50 +] "GET 
/api/atlas/entities/c8cfce9f-1d49-41f2-88fd-1671f3827cd3 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [04/Jan/2017:02:52:50 +] "GET 
/api/atlas/entities/8042cb93-c673-4e7c-8bba-d3cc0c998886 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [04/Jan/2017:02:52:50 +] "GET 
/api/atlas/entities?type=hdfs_path&property=qualifiedName&value=p
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jan/2017:02:52:50 +] "GET 
/api/atlas/entities?type=hdfs_path&property=qualifiedName&value=p
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jan/2017:02:52:50 +] "GET 
/api/atlas/entities/8042cb93-c673-4e7c-8bba-d3cc0c998886 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [04/Jan/2017:02:52:50 +] "GET 
/api/atlas/entities?type=hive_table&property=qualifiedName&value=default.tableacx4kda8s4@primary
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jan/2017:02:52:50 +] "GET 
/api/atlas/entities?type=hive_table&property=qualifiedName&value=default.tableacx4kda8s4@primary
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jan/2017:02:52:50 +] "GET 
/api/atlas/entities/c8cfce9f-1d49-41f2-88fd-1671f3827cd3 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [04/Jan/2017:02:52:53 +] "GET 
/api/atlas/entities?type=hive_table&property=qualifiedName&value=default.tableacx4kda8s4@primary
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jan/2017:02:52:53 +] "GET 
/api/atlas/entities?type=hive_table&property=qualifiedName&value=default.tableacx4kda8s4@primary
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jan/2017:02:52:53 +] "GET 
/api/atlas/entities?type=hive_process&property=qualifiedName&value=QUERY:default.tableacx4kda8s4@primary:1483498363000-%3E:PATH_WRITE
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jan/2017:02:52:53 +] "GET 
/api/atlas/entities?type=hive_process&property=qualifiedName&value=QUERY:default.tableacx4kda8s4@primary:1483498363000-%3E:PATH_WRITE
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [04/Jan/2017:02:52:53 +] "GET 
/api/atlas/entities/2bee6315-689b-4843-a301-6828418c211d HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [04/Jan/2017:02:52:53 +] "GET 
/api/atlas/entities/c8cfce9f-1d49-41f2-88fd-1671f3827cd3 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [04/Jan/2017:02:52:53 +] "GET 
/api/atlas/entities/8042cb93-c673-4e7c-8bba-d3cc0c998886 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [04/Jan/2017:02:52:53 +] "GET 
/api/atlas/entities?type=hdfs_path&property=qualifiedName&value=p

Re: Review Request 54759: ATLAS-1379 Avoid object query overhead when report query selects class type alias

[David Kantor]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54759/#review160451
---



This change has been available for review since Dec 16. It will be committed 
tomorrow (Wed Jan 4 2016) unless there are further comments on review board.

- David Kantor


On Jan. 3, 2017, 8:21 p.m., Neeru Gupta wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/54759/
> ---
> 
> (Updated Jan. 3, 2017, 8:21 p.m.)
> 
> 
> Review request for atlas and David Kantor.
> 
> 
> Bugs: ATLAS-1379
> https://issues.apache.org/jira/browse/ATLAS-1379
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> OMS-743 when an object instance is selected in select query then only fetch 
> the id (guid, typename, version and state) for performance reasons
> 
> 
> Diffs
> -
> 
>   
> repository/src/main/java/org/apache/atlas/discovery/DataSetLineageService.java
>  fb027efc1ad9a7b2c562fc6670a8f9647b3b54f0 
>   
> repository/src/main/java/org/apache/atlas/discovery/graph/DefaultGraphPersistenceStrategy.java
>  aad056f5247cd5ac0e5c84d2f1fa9c4bb5458fb3 
>   
> repository/src/main/java/org/apache/atlas/discovery/graph/GraphBackedDiscoveryService.java
>  f2a1fe975bc720e3003389806f1e32d3edf74713 
>   
> repository/src/main/java/org/apache/atlas/repository/MetadataRepository.java 
> a2a9ab6dafcefaa29110051c35d3b6762017a28f 
>   
> repository/src/main/java/org/apache/atlas/repository/graph/DeleteHandler.java 
> 51e9ab1fb6bfe7e854bcf40bfc3d92136de4c60f 
>   
> repository/src/main/java/org/apache/atlas/repository/graph/FullTextMapper.java
>  2c12bc3e82109819759c3c54ba3a786fee656594 
>   
> repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedMetadataRepository.java
>  f6b3fc5ffb6dd76271ccf8217b587b52b98cf78b 
>   repository/src/main/java/org/apache/atlas/repository/graph/GraphHelper.java 
> 7eacc5dbf186885a3e51294b8717bc9c05bd0b66 
>   
> repository/src/main/java/org/apache/atlas/repository/graph/TypedInstanceToGraphMapper.java
>  19ca328a7f4240ea62fdd171f23c6c5c14d25af5 
>   
> repository/src/main/scala/org/apache/atlas/query/GraphPersistenceStrategies.scala
>  eb6d119b2eca699d67fe071fe2659de2fddb9285 
>   repository/src/main/scala/org/apache/atlas/query/GremlinEvaluator.scala 
> 9e336cf2abb90141a16220cae078952cdc410475 
>   
> repository/src/test/java/org/apache/atlas/discovery/GraphBackedDiscoveryServiceTest.java
>  aaa8fa0d594e97fabfa51c5c76c5aab879bf8e7f 
>   typesystem/src/main/java/org/apache/atlas/typesystem/types/TypeSystem.java 
> d73a7b32add5d9e4eb24afefed042cf894964992 
> 
> Diff: https://reviews.apache.org/r/54759/diff/
> 
> 
> Testing
> ---
> 
> All Unit tests executed successfully.
> 
> Added new test cases in GraphBackedDiscoveryTest to valiadte the fields 
> coming back with id type report queries.
> 
> 
> Thanks,
> 
> Neeru Gupta
> 
>

[jira] [Commented] (ATLAS-1346) Search APIs should return empty list instead of throwing exception

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj commented on ATLAS-1346:
-

+1 for the patch. Thanks [~apoorvnaik].

[~yhemanth] - thanks for the note about ATLAS-805. This patch doesn't change 
the transaction semantics but only avoids logging the exception to 
application.log.

> Search APIs should return empty list instead of throwing exception
> --
>
> Key: ATLAS-1346
> URL: https://issues.apache.org/jira/browse/ATLAS-1346
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1346.v1.patch
>
>
> When the search call yields no results either return an empty list or avoid 
> logging the error in the logs.



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

Re: Review Request 54907: ATLAS-1391 Add exclusion mechanism for Atlas audit mechanism

[Madhan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54907/#review160432
---


Fix it, then Ship it!





webapp/src/main/java/org/apache/atlas/web/filters/AuditFilter.java (line 100)


After changes in ATLAS-1281, audit logs are saved only to audit.log (in 
audit() method below, using AUDIT_LOG logger) and not to application.log.

If you didn't mean to revert this change, I can remove line #100 before 
committing this patch. Please let me know.


- Madhan Neethiraj


On Jan. 3, 2017, 8:09 p.m., Neeru Gupta wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/54907/
> ---
> 
> (Updated Jan. 3, 2017, 8:09 p.m.)
> 
> 
> Review request for atlas.
> 
> 
> Bugs: ATLAS-1391
> https://issues.apache.org/jira/browse/ATLAS-1391
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Merge branch 'master' into OMS_852
> 
> 
> Diffs
> -
> 
>   
> repository/src/main/java/org/apache/atlas/util/AtlasRepositoryConfiguration.java
>  4b6f88f45dc6bf5ec9a149c06b38059c0c43559a 
>   webapp/src/main/java/org/apache/atlas/web/filters/AuditFilter.java 
> 7499cde4c5dc6a2c5253cd7a354a6add7d8e02e4 
>   webapp/src/test/java/org/apache/atlas/web/filters/AuditFilterTest.java 
> PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/54907/diff/
> 
> 
> Testing
> ---
> 
> Added new test class 'AuditFilterTest'
> 
> 
> Thanks,
> 
> Neeru Gupta
> 
>

[jira] [Updated] (ATLAS-1379) Avoid object query overhead when report query selects class type alias

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-1379:
---
Attachment: (was: rb54759.patch)

> Avoid object query overhead when report query selects class type alias
> --
>
> Key: ATLAS-1379
> URL: https://issues.apache.org/jira/browse/ATLAS-1379
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
>  Labels: performance
> Fix For: 0.8-incubating
>
> Attachments: rb54759(1).patch
>
>
> When the DSL query is selecting the class alias, which causes Atlas to run an 
> object query. Atlas should detect this query construct and avoid the overhead 
> of full entity retrieval, when the entity ends up being serialized as an 
> structure that just contains the guid, type, and status.
> For queries like: 'from hive_db  as h select h', even though the end result 
> only contains id object, Atlas code initially loads the entire object with 
> all its properties and while serializing it ends up serializing only the id 
> part. This bug is to avoid the overhead of loading the entire object when 
> fields other than id will be discarded anyways. This added a lot of overhead 
> and was identified as hotspot in our internal testing. This is specially 
> relevant when large number of objects are retrieved as search results. 
> Note that the fixes are backward compatible. The end result remains the same. 
> Only the overwork to load unnecessary fields is avoided.
> Sample Query: 'from hive_db as h select h'
> Result:
> rows":[
> {
>   "$typeName$":"__tempQueryResultStruct2",
>   "id":{
> "id":"8159ee38-ec29-4d9a-845a-86fe17ab6bdb",
> "$typeName$":"hive_db",
> "version":0,
> "state":"ACTIVE"
>   }
> },
> {
>   "$typeName$":"__tempQueryResultStruct2",
>   "id":{
> "id":"33016845-4b71-4d56-b131-b48ea38e5507",
> "$typeName$":"hive_db",
> "version":0,
> "state":"ACTIVE"
>   }
> },
> {
>   "$typeName$":"__tempQueryResultStruct2",
>   "id":{
> "id":"b6fb9c53-680e-4be7-b143-f8d9355c5726",
> "$typeName$":"hive_db",
> "version":0,
> "state":"ACTIVE"
>   }
> }
>   ]



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

[jira] [Updated] (ATLAS-1379) Avoid object query overhead when report query selects class type alias

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-1379:
---
Attachment: rb54759(1).patch

> Avoid object query overhead when report query selects class type alias
> --
>
> Key: ATLAS-1379
> URL: https://issues.apache.org/jira/browse/ATLAS-1379
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
>  Labels: performance
> Fix For: 0.8-incubating
>
> Attachments: rb54759(1).patch
>
>
> When the DSL query is selecting the class alias, which causes Atlas to run an 
> object query. Atlas should detect this query construct and avoid the overhead 
> of full entity retrieval, when the entity ends up being serialized as an 
> structure that just contains the guid, type, and status.
> For queries like: 'from hive_db  as h select h', even though the end result 
> only contains id object, Atlas code initially loads the entire object with 
> all its properties and while serializing it ends up serializing only the id 
> part. This bug is to avoid the overhead of loading the entire object when 
> fields other than id will be discarded anyways. This added a lot of overhead 
> and was identified as hotspot in our internal testing. This is specially 
> relevant when large number of objects are retrieved as search results. 
> Note that the fixes are backward compatible. The end result remains the same. 
> Only the overwork to load unnecessary fields is avoided.
> Sample Query: 'from hive_db as h select h'
> Result:
> rows":[
> {
>   "$typeName$":"__tempQueryResultStruct2",
>   "id":{
> "id":"8159ee38-ec29-4d9a-845a-86fe17ab6bdb",
> "$typeName$":"hive_db",
> "version":0,
> "state":"ACTIVE"
>   }
> },
> {
>   "$typeName$":"__tempQueryResultStruct2",
>   "id":{
> "id":"33016845-4b71-4d56-b131-b48ea38e5507",
> "$typeName$":"hive_db",
> "version":0,
> "state":"ACTIVE"
>   }
> },
> {
>   "$typeName$":"__tempQueryResultStruct2",
>   "id":{
> "id":"b6fb9c53-680e-4be7-b143-f8d9355c5726",
> "$typeName$":"hive_db",
> "version":0,
> "state":"ACTIVE"
>   }
> }
>   ]



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

Re: Review Request 54759: ATLAS-1379 Avoid object query overhead when report query selects class type alias

[Neeru Gupta]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54759/
---

(Updated Jan. 3, 2017, 8:21 p.m.)


Review request for atlas and David Kantor.


Bugs: ATLAS-1379
https://issues.apache.org/jira/browse/ATLAS-1379


Repository: atlas


Description
---

OMS-743 when an object instance is selected in select query then only fetch the 
id (guid, typename, version and state) for performance reasons


Diffs (updated)
-

  
repository/src/main/java/org/apache/atlas/discovery/DataSetLineageService.java 
fb027efc1ad9a7b2c562fc6670a8f9647b3b54f0 
  
repository/src/main/java/org/apache/atlas/discovery/graph/DefaultGraphPersistenceStrategy.java
 aad056f5247cd5ac0e5c84d2f1fa9c4bb5458fb3 
  
repository/src/main/java/org/apache/atlas/discovery/graph/GraphBackedDiscoveryService.java
 f2a1fe975bc720e3003389806f1e32d3edf74713 
  repository/src/main/java/org/apache/atlas/repository/MetadataRepository.java 
a2a9ab6dafcefaa29110051c35d3b6762017a28f 
  repository/src/main/java/org/apache/atlas/repository/graph/DeleteHandler.java 
51e9ab1fb6bfe7e854bcf40bfc3d92136de4c60f 
  
repository/src/main/java/org/apache/atlas/repository/graph/FullTextMapper.java 
2c12bc3e82109819759c3c54ba3a786fee656594 
  
repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedMetadataRepository.java
 f6b3fc5ffb6dd76271ccf8217b587b52b98cf78b 
  repository/src/main/java/org/apache/atlas/repository/graph/GraphHelper.java 
7eacc5dbf186885a3e51294b8717bc9c05bd0b66 
  
repository/src/main/java/org/apache/atlas/repository/graph/TypedInstanceToGraphMapper.java
 19ca328a7f4240ea62fdd171f23c6c5c14d25af5 
  
repository/src/main/scala/org/apache/atlas/query/GraphPersistenceStrategies.scala
 eb6d119b2eca699d67fe071fe2659de2fddb9285 
  repository/src/main/scala/org/apache/atlas/query/GremlinEvaluator.scala 
9e336cf2abb90141a16220cae078952cdc410475 
  
repository/src/test/java/org/apache/atlas/discovery/GraphBackedDiscoveryServiceTest.java
 aaa8fa0d594e97fabfa51c5c76c5aab879bf8e7f 
  typesystem/src/main/java/org/apache/atlas/typesystem/types/TypeSystem.java 
d73a7b32add5d9e4eb24afefed042cf894964992 

Diff: https://reviews.apache.org/r/54759/diff/


Testing
---

All Unit tests executed successfully.

Added new test cases in GraphBackedDiscoveryTest to valiadte the fields coming 
back with id type report queries.


Thanks,

Neeru Gupta

[jira] [Updated] (ATLAS-1391) Add exclusion mechanism for Atlas audit mechanism

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-1391:
---
Attachment: (was: rb54907.patch)

> Add exclusion mechanism for Atlas audit mechanism
> -
>
> Key: ATLAS-1391
> URL: https://issues.apache.org/jira/browse/ATLAS-1391
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
> Attachments: rb54907(1).patch
>
>
> As a consumer of Atlas, I want to be able to exclude certain operations, such 
> as ping, from the audit log so that it does not get filled up with noise.
> This should be a general mechanism. It should be possible to configure the 
> endpoints being excluded in the Atlas configuration file. The only 
> requirement at this time is to be able to filter based on the high level 
> operation being invoked (ie ping, version, etc). There is no need to be able 
> to filter based on the arguments to the operation.



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

[jira] [Updated] (ATLAS-1391) Add exclusion mechanism for Atlas audit mechanism

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-1391:
---
Attachment: rb54907(1).patch

Rebased with trunk.

> Add exclusion mechanism for Atlas audit mechanism
> -
>
> Key: ATLAS-1391
> URL: https://issues.apache.org/jira/browse/ATLAS-1391
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
> Attachments: rb54907(1).patch
>
>
> As a consumer of Atlas, I want to be able to exclude certain operations, such 
> as ping, from the audit log so that it does not get filled up with noise.
> This should be a general mechanism. It should be possible to configure the 
> endpoints being excluded in the Atlas configuration file. The only 
> requirement at this time is to be able to filter based on the high level 
> operation being invoked (ie ping, version, etc). There is no need to be able 
> to filter based on the arguments to the operation.



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

Re: Review Request 54907: ATLAS-1391 Add exclusion mechanism for Atlas audit mechanism

[Neeru Gupta]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54907/
---

(Updated Jan. 3, 2017, 8:09 p.m.)


Review request for atlas.


Bugs: ATLAS-1391
https://issues.apache.org/jira/browse/ATLAS-1391


Repository: atlas


Description
---

Merge branch 'master' into OMS_852


Diffs (updated)
-

  
repository/src/main/java/org/apache/atlas/util/AtlasRepositoryConfiguration.java
 4b6f88f45dc6bf5ec9a149c06b38059c0c43559a 
  webapp/src/main/java/org/apache/atlas/web/filters/AuditFilter.java 
7499cde4c5dc6a2c5253cd7a354a6add7d8e02e4 
  webapp/src/test/java/org/apache/atlas/web/filters/AuditFilterTest.java 
PRE-CREATION 

Diff: https://reviews.apache.org/r/54907/diff/


Testing
---

Added new test class 'AuditFilterTest'


Thanks,

Neeru Gupta

Jenkins build is back to normal : apache-atlas-nightly #531

[Apache Jenkins Server]

See 

[jira] [Commented] (ATLAS-1379) Avoid object query overhead when report query selects class type alias

[David Kantor (JIRA)]

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

David Kantor commented on ATLAS-1379:
-

This change has been available for review since Dec 16.  It will be committed 
tomorrow (Wed Jan 4 2016) unless there are further comments on review board.

> Avoid object query overhead when report query selects class type alias
> --
>
> Key: ATLAS-1379
> URL: https://issues.apache.org/jira/browse/ATLAS-1379
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
>  Labels: performance
> Fix For: 0.8-incubating
>
> Attachments: rb54759.patch
>
>
> When the DSL query is selecting the class alias, which causes Atlas to run an 
> object query. Atlas should detect this query construct and avoid the overhead 
> of full entity retrieval, when the entity ends up being serialized as an 
> structure that just contains the guid, type, and status.
> For queries like: 'from hive_db  as h select h', even though the end result 
> only contains id object, Atlas code initially loads the entire object with 
> all its properties and while serializing it ends up serializing only the id 
> part. This bug is to avoid the overhead of loading the entire object when 
> fields other than id will be discarded anyways. This added a lot of overhead 
> and was identified as hotspot in our internal testing. This is specially 
> relevant when large number of objects are retrieved as search results. 
> Note that the fixes are backward compatible. The end result remains the same. 
> Only the overwork to load unnecessary fields is avoided.
> Sample Query: 'from hive_db as h select h'
> Result:
> rows":[
> {
>   "$typeName$":"__tempQueryResultStruct2",
>   "id":{
> "id":"8159ee38-ec29-4d9a-845a-86fe17ab6bdb",
> "$typeName$":"hive_db",
> "version":0,
> "state":"ACTIVE"
>   }
> },
> {
>   "$typeName$":"__tempQueryResultStruct2",
>   "id":{
> "id":"33016845-4b71-4d56-b131-b48ea38e5507",
> "$typeName$":"hive_db",
> "version":0,
> "state":"ACTIVE"
>   }
> },
> {
>   "$typeName$":"__tempQueryResultStruct2",
>   "id":{
> "id":"b6fb9c53-680e-4be7-b143-f8d9355c5726",
> "$typeName$":"hive_db",
> "version":0,
> "state":"ACTIVE"
>   }
> }
>   ]



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

[jira] [Commented] (ATLAS-1416) UI: It would be nice to sort the properties in the details page of an entity by name

[David Radley (JIRA)]

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

David Radley commented on ATLAS-1416:
-

Hi [~yhemanth] I would think that the order of the attributes in an entity 
should be defined in the Atlas data model and exposed that way in API, then 
displayed as such in the UI. There could be a sort button in the browser UI so 
the user can alphabetically sort ascending and descending implemented in 
javascript. Is this what you are thinking?   

> UI: It would be nice to sort the properties in the details page of an entity 
> by name
> 
>
> Key: ATLAS-1416
> URL: https://issues.apache.org/jira/browse/ATLAS-1416
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Hemanth Yamijala
>
> The Atlas UI has a Details page for every entity. In the "Properties" tab of 
> this pane, it currently enumerates all properties of the entity. Currently 
> the order seems random and hence is not very easy to grok. It would be nice 
> to have these sorted by property name to make location of required details 
> easier.



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

Re: Review Request 55138: ATLAS-1424 - Avoid stack-trace in REST API error response

[Madhan Neethiraj]

> On Jan. 3, 2017, 4:08 p.m., David Radley wrote:
> > Hi, Can you confirm that after fix, the stack trace for this exception will 
> > be logged - even if it is not sent back in the REST response.

The fix only removes the stack trace from HTTP response. I confirmed that the 
error log generated continues to include the stack trace.


- Madhan


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/55138/#review160391
---


On Jan. 3, 2017, 2:23 p.m., Nixon Rodrigues wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/55138/
> ---
> 
> (Updated Jan. 3, 2017, 2:23 p.m.)
> 
> 
> Review request for atlas, keval bhatt, Madhan Neethiraj, and Vimal Sharma.
> 
> 
> Bugs: ATLAS-1424
> https://issues.apache.org/jira/browse/ATLAS-1424
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> This patch provides fix to avoid stack-trace in REST API error response, by 
> removing stacktrace attribute from json response.
> 
> 
> Diffs
> -
> 
>   webapp/src/main/java/org/apache/atlas/web/util/Servlets.java b4f0839 
>   
> webapp/src/test/java/org/apache/atlas/web/resources/EntityJerseyResourceIT.java
>  23203ec 
> 
> Diff: https://reviews.apache.org/r/55138/diff/
> 
> 
> Testing
> ---
> 
> Execute test cases using mvn clean install
> 
> Tested json response for discovery, types, entity type of api's in normal & 
> exceptional conditions.
> 
> 
> Thanks,
> 
> Nixon Rodrigues
> 
>

Re: Review Request 55138: ATLAS-1424 - Avoid stack-trace in REST API error response

[Madhan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/55138/#review160394
---


Fix it, then Ship it!





webapp/src/main/java/org/apache/atlas/web/util/Servlets.java (line 140)


printStackTrace() method is no more referenced; hence can be removed. I 
will remove it before committing the patch.


- Madhan Neethiraj


On Jan. 3, 2017, 2:23 p.m., Nixon Rodrigues wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/55138/
> ---
> 
> (Updated Jan. 3, 2017, 2:23 p.m.)
> 
> 
> Review request for atlas, keval bhatt, Madhan Neethiraj, and Vimal Sharma.
> 
> 
> Bugs: ATLAS-1424
> https://issues.apache.org/jira/browse/ATLAS-1424
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> This patch provides fix to avoid stack-trace in REST API error response, by 
> removing stacktrace attribute from json response.
> 
> 
> Diffs
> -
> 
>   webapp/src/main/java/org/apache/atlas/web/util/Servlets.java b4f0839 
>   
> webapp/src/test/java/org/apache/atlas/web/resources/EntityJerseyResourceIT.java
>  23203ec 
> 
> Diff: https://reviews.apache.org/r/55138/diff/
> 
> 
> Testing
> ---
> 
> Execute test cases using mvn clean install
> 
> Tested json response for discovery, types, entity type of api's in normal & 
> exceptional conditions.
> 
> 
> Thanks,
> 
> Nixon Rodrigues
> 
>

Re: Review Request 55138: ATLAS-1424 - Avoid stack-trace in REST API error response

[David Radley]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/55138/#review160391
---



Hi, Can you confirm that after fix, the stack trace for this exception will be 
logged - even if it is not sent back in the REST response.

- David Radley


On Jan. 3, 2017, 2:23 p.m., Nixon Rodrigues wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/55138/
> ---
> 
> (Updated Jan. 3, 2017, 2:23 p.m.)
> 
> 
> Review request for atlas, keval bhatt, Madhan Neethiraj, and Vimal Sharma.
> 
> 
> Bugs: ATLAS-1424
> https://issues.apache.org/jira/browse/ATLAS-1424
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> This patch provides fix to avoid stack-trace in REST API error response, by 
> removing stacktrace attribute from json response.
> 
> 
> Diffs
> -
> 
>   webapp/src/main/java/org/apache/atlas/web/util/Servlets.java b4f0839 
>   
> webapp/src/test/java/org/apache/atlas/web/resources/EntityJerseyResourceIT.java
>  23203ec 
> 
> Diff: https://reviews.apache.org/r/55138/diff/
> 
> 
> Testing
> ---
> 
> Execute test cases using mvn clean install
> 
> Tested json response for discovery, types, entity type of api's in normal & 
> exceptional conditions.
> 
> 
> Thanks,
> 
> Nixon Rodrigues
> 
>

Re: searching for entities with tags by name

[David Radley]

Hi Avi,
If you have a term that has available_as_tag set then I would expect the 
taxonomy object to be tagged as internally the taxonomy object is an 
entity. You have tagged an entity as well. I suspect this search is 
returning both of these entities. I think this is a bit confusing - I 
suggest raising a Jira to make the API cleaner to not return glossary 
entities in this case,all the best, David. 

 
 



From:   Avi Levi 
To: dev@atlas.incubator.apache.org
Date:   28/12/2016 12:16
Subject:searching for entities with tags by name



Hi

According to the documentation, searching for entities that are
associated to tags is done using the search/dsl api:

http:/// api/atlas/
discovery/search/dsl?query= %60tag-name%60

in the documentation the response contains one instance in the
results, but when I execute the api call, I get two instances in the
results, one of them
is the actual entity that I've tagged, and the other one is an object
of type Taxonomy.

can anyone explain this behavior ?

thanks




Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

[jira] [Updated] (ATLAS-1424) Avoid stack-trace in REST API error response

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1424:
---
Attachment: ATLAS-1424-0.7-incubating.patch

ATLAS-1424-0.7-incubating.patch for 0.7-incubating branch

> Avoid stack-trace in REST API error response
> 
>
> Key: ATLAS-1424
> URL: https://issues.apache.org/jira/browse/ATLAS-1424
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Madhan Neethiraj
>Assignee: Nixon Rodrigues
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1424-0.7-incubating.patch, ATLAS-1424.patch
>
>
> In case of errors while executing REST API calls, Atlas server response 
> includes stack trace, which should be avoided to not return 
> excessive/internal information.



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

[jira] [Updated] (ATLAS-1424) Avoid stack-trace in REST API error response

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1424:
---
Attachment: ATLAS-1424.patch

> Avoid stack-trace in REST API error response
> 
>
> Key: ATLAS-1424
> URL: https://issues.apache.org/jira/browse/ATLAS-1424
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Madhan Neethiraj
>Assignee: Nixon Rodrigues
> Attachments: ATLAS-1424.patch
>
>
> In case of errors while executing REST API calls, Atlas server response 
> includes stack trace, which should be avoided to not return 
> excessive/internal information.



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

[jira] [Assigned] (ATLAS-1424) Avoid stack-trace in REST API error response

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues reassigned ATLAS-1424:
--

Assignee: Nixon Rodrigues

> Avoid stack-trace in REST API error response
> 
>
> Key: ATLAS-1424
> URL: https://issues.apache.org/jira/browse/ATLAS-1424
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Madhan Neethiraj
>Assignee: Nixon Rodrigues
>
> In case of errors while executing REST API calls, Atlas server response 
> includes stack trace, which should be avoided to not return 
> excessive/internal information.



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

Review Request 55138: ATLAS-1424 - Avoid stack-trace in REST API error response

[Nixon Rodrigues]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/55138/
---

Review request for atlas, keval bhatt, Madhan Neethiraj, and Vimal Sharma.


Bugs: ATLAS-1424
https://issues.apache.org/jira/browse/ATLAS-1424


Repository: atlas


Description
---

This patch provides fix to avoid stack-trace in REST API error response, by 
removing stacktrace attribute from json response.


Diffs
-

  webapp/src/main/java/org/apache/atlas/web/util/Servlets.java b4f0839 
  
webapp/src/test/java/org/apache/atlas/web/resources/EntityJerseyResourceIT.java 
23203ec 

Diff: https://reviews.apache.org/r/55138/diff/


Testing
---

Execute test cases using mvn clean install

Tested json response for discovery, types, entity type of api's in normal & 
exceptional conditions.


Thanks,

Nixon Rodrigues

[jira] [Updated] (ATLAS-1421) Regression : HTML is displayed for deleted entities in Atlas search results and in details page of any entity(ACTIVE/DELETED)

[Kalyani Kashikar (JIRA)]

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

Kalyani Kashikar updated ATLAS-1421:

Attachment: ATLAS-1421.patch

> Regression : HTML is displayed for deleted entities in Atlas search results 
> and in details page of any entity(ACTIVE/DELETED)
> -
>
> Key: ATLAS-1421
> URL: https://issues.apache.org/jira/browse/ATLAS-1421
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Sharmadha Sainath
>Assignee: Kalyani Kashikar
>Priority: Critical
> Attachments: ATLAS-1421.patch, Active_entity_result.png, 
> Deleted_entity_result.png, detailsPage_of_entity.png
>
>
> Created a hive table , test_table . Searched the same table in Atlas which 
> renders the result properly. 
> 1. On clicking the test_table, the details page shows entities as HTML text 
> instead of the entity itself.
> 2. Deleted the test_table . Link to the entity in HTML is displayed as plain 
> text instead of the clickable link of the entity.



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

Hook for Non Supported Data stores

[Karthik K]

Team,

Is there we could write or extend Hook for non supported data store like
Impala.

Hive, HDFS, Kafka, Storm are supported now but would like to know if i have
Impala table and will it be possible to create hook for the same.

Thanks & Regards,
K.Karthikeyan

[jira] [Created] (ATLAS-1424) Avoid stack-trace in REST API error response

[Madhan Neethiraj (JIRA)]

Madhan Neethiraj created ATLAS-1424:
---

 Summary: Avoid stack-trace in REST API error response
 Key: ATLAS-1424
 URL: https://issues.apache.org/jira/browse/ATLAS-1424
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Madhan Neethiraj


In case of errors while executing REST API calls, Atlas server response 
includes stack trace, which should be avoided to not return excessive/internal 
information.




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