[jira] [Created] (ATLAS-219) UI: Add ability to detach trait from the entity

2015-10-12 Thread Ayub Khan (JIRA) 
Ayub Khan created ATLAS-219:
---

 Summary: UI: Add ability to detach trait from the entity
 Key: ATLAS-219
 URL: https://issues.apache.org/jira/browse/ATLAS-219
 Project: Atlas
  Issue Type: Improvement
Reporter: Ayub Khan


Currently we are able to detach trait from the entity using REST API.  Similar 
support can be provided via ATLAS-UI.


{code}
curl -X DELETE -v 
'http://localhost:21000/api/atlas/entity/9646d28d-bbea-4cc5-9d84-0d37f0ca536c/traits/PII'
*   Trying ::1...
* Connected to localhost (::1) port 21000 (#0)
> DELETE /api/atlas/entity/9646d28d-bbea-4cc5-9d84-0d37f0ca536c/traits/PII 
> HTTP/1.1
> Host: localhost:21000
> User-Agent: curl/7.43.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Mon, 12 Oct 2015 15:34:15 GMT
< Content-Type: application/json; charset=UTF-8
< Transfer-Encoding: chunked
< Server: Jetty(9.2.12.v20150709)
<
* Connection #0 to host localhost left intact
{"requestId":"qtp468469-162 - 
387b46eb-4fca-4547-aef7-f53590b9c069","GUID":"9646d28d-bbea-4cc5-9d84-0d37f0ca536c","traitName":"PII"}
{code}



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

[jira] [Updated] (ATLAS-219) UI: Add ability to detach trait from the entity

2015-10-12 Thread Ayub Khan (JIRA) 

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

Ayub Khan updated ATLAS-219:

Labels:   (was: ATLAS-UI-BUGS)

> UI: Add ability to detach trait from the entity
> ---
>
> Key: ATLAS-219
> URL: https://issues.apache.org/jira/browse/ATLAS-219
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Ayub Khan
>
> Currently we are able to detach trait from the entity using REST API.  
> Similar support can be provided via ATLAS-UI.
> {code}
> curl -X DELETE -v 
> 'http://localhost:21000/api/atlas/entity/9646d28d-bbea-4cc5-9d84-0d37f0ca536c/traits/PII'
> *   Trying ::1...
> * Connected to localhost (::1) port 21000 (#0)
> > DELETE /api/atlas/entity/9646d28d-bbea-4cc5-9d84-0d37f0ca536c/traits/PII 
> > HTTP/1.1
> > Host: localhost:21000
> > User-Agent: curl/7.43.0
> > Accept: */*
> >
> < HTTP/1.1 200 OK
> < Date: Mon, 12 Oct 2015 15:34:15 GMT
> < Content-Type: application/json; charset=UTF-8
> < Transfer-Encoding: chunked
> < Server: Jetty(9.2.12.v20150709)
> <
> * Connection #0 to host localhost left intact
> {"requestId":"qtp468469-162 - 
> 387b46eb-4fca-4547-aef7-f53590b9c069","GUID":"9646d28d-bbea-4cc5-9d84-0d37f0ca536c","traitName":"PII"}
> {code}



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

[jira] [Commented] (ATLAS-199) webapp build fails (grunt + tests)

2015-10-12 Thread Darshan Kumar (JIRA) 

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

Darshan Kumar commented on ATLAS-199:
-

This issue is solved with the dependent patch 
https://issues.apache.org/jira/browse/ATLAS-159 since the profile is removed  
and please verify. Thanks [~suma.shivaprasad]

> webapp build fails (grunt + tests)
> --
>
> Key: ATLAS-199
> URL: https://issues.apache.org/jira/browse/ATLAS-199
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.6-incubating
>Reporter: Erik Bergenholtz
>Assignee: Darshan Kumar
>Priority: Critical
>  Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-199-v0.patch
>
>
> When building Atlas webapp, I see the following issues:
> mvn clean install:
> {code}
> [INFO] Running 'grunt bower --no-color' in 
> /Users/ebergenholtz/git3/incubator-atlas/dashboard
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 34.282 s
> [INFO] Finished at: 2015-09-30T13:55:30-05:00
> [INFO] Final Memory: 35M/420M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> com.github.eirslett:frontend-maven-plugin:0.0.23:grunt (install bower) on 
> project atlas-webapp: Failed to run task: 'grunt bower --no-color' failed. 
> java.io.IOException: Cannot run program 
> "/Users/ebergenholtz/git3/incubator-atlas/dashboard/node/node" (in directory 
> "/Users/ebergenholtz/git3/incubator-atlas/dashboard"): error=2, No such file 
> or directory -> [Help 1]
> {code}
> Also, if I bypass the grunt task some of the tests fail.



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

[jira] [Updated] (ATLAS-214) UI : For any hive_table, schema/input/output tabs are not displayed

2015-10-12 Thread Ayub Khan (JIRA) 

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

Ayub Khan updated ATLAS-214:

Labels: ATLAS-UI-BUGS  (was: )

> UI : For any hive_table, schema/input/output tabs are not displayed
> ---
>
> Key: ATLAS-214
> URL: https://issues.apache.org/jira/browse/ATLAS-214
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.6-incubating
>Reporter: Ayub Khan
>  Labels: ATLAS-UI-BUGS
> Attachments: Hive_Table_snapshot.png, Table_snapshot.png
>
>
> In Atlas UI, for any hive_tables schema/input/output tabs are not displayed. 
> whereas for other tables these tabs are shown.
> Please take a look at the UI snapshots.



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

[jira] [Created] (ATLAS-218) UI: Use different icons for entity and process in the lineage graph

2015-10-12 Thread Ayub Khan (JIRA) 
Ayub Khan created ATLAS-218:
---

 Summary: UI: Use different icons for entity and process in the 
lineage graph
 Key: ATLAS-218
 URL: https://issues.apache.org/jira/browse/ATLAS-218
 Project: Atlas
  Issue Type: Bug
Affects Versions: 0.6-incubating
Reporter: Ayub Khan
 Attachments: LineageSnapshot.png

Currently Atlas uses same icon for all entities and there is no clear 
differentiation between hive_table and hive_process. Pleas check the attached 
snapshot.

>From an end user's perspective, it is good to have a clear difference for 
>better understanding.



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

[jira] [Updated] (ATLAS-218) UI: Use different icons for entity and process in the lineage graph

2015-10-12 Thread Ayub Khan (JIRA) 

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

Ayub Khan updated ATLAS-218:

Attachment: LineageSnapshot.png

Attaching lineage snapshot.

> UI: Use different icons for entity and process in the lineage graph
> ---
>
> Key: ATLAS-218
> URL: https://issues.apache.org/jira/browse/ATLAS-218
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.6-incubating
>Reporter: Ayub Khan
>  Labels: ATLAS-UI-BUGS
> Attachments: LineageSnapshot.png
>
>
> Currently Atlas uses same icon for all entities and there is no clear 
> differentiation between hive_table and hive_process. Pleas check the attached 
> snapshot.
> From an end user's perspective, it is good to have a clear difference for 
> better understanding.



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

[jira] [Updated] (ATLAS-135) Re-model hive type system

2015-10-12 Thread Erik Bergenholtz (JIRA) 

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

Erik Bergenholtz updated ATLAS-135:
---
Assignee: John Speidel

> Re-model hive type system
> -
>
> Key: ATLAS-135
> URL: https://issues.apache.org/jira/browse/ATLAS-135
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: John Speidel
>
> As of now, hive model looks like copy of hive metastore schema. For example, 
> some important info like table type is part of parameters which is 
> map. We should re-model this to make search easier



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

[jira] [Updated] (ATLAS-212) Remove test class usage of hive configuration property "atlas.rest.address"

2015-10-12 Thread Shwetha G S (JIRA) 

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

Shwetha G S updated ATLAS-212:
--
Attachment: ATLAS-212.patch

> Remove test class usage of hive configuration property "atlas.rest.address"
> ---
>
> Key: ATLAS-212
> URL: https://issues.apache.org/jira/browse/ATLAS-212
> Project: Atlas
>  Issue Type: Task
>Reporter: John Speidel
>Assignee: John Speidel
> Attachments: ATLAS-212.patch
>
>
> The property "atlas.rest.address" has been removed from hive-site 
> configuration but is still referenced by the class HiveHookIT.



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

[jira] [Created] (ATLAS-220) gets on Enum attribute should return EnumValue

2015-10-12 Thread Suma Shivaprasad (JIRA) 
Suma Shivaprasad created ATLAS-220:
--

 Summary: gets on Enum attribute should return EnumValue
 Key: ATLAS-220
 URL: https://issues.apache.org/jira/browse/ATLAS-220
 Project: Atlas
  Issue Type: Bug
Reporter: Suma Shivaprasad


Referenceable tableDefinition = 
InstanceSerialization.fromJsonReferenceable(tableDefinitionJson, true);
EnumValue enumStr = (EnumValue) tableDefinition.get("tableType");

The cast fails with

{noformat}
String tableDefinitionJson =
metadataService.getEntityDefinition(TestUtils.TABLE_TYPE, "name", 
(String) table.get("name"));
Referenceable tableDefinition = 
InstanceSerialization.fromJsonReferenceable(tableDefinitionJson, true);
EnumValue enumStr = (EnumValue) tableDefinition.get("tableType");
{noformat}




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

[jira] [Updated] (ATLAS-220) Gets on Enum attribute should return EnumValue

2015-10-12 Thread Suma Shivaprasad (JIRA) 

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

Suma Shivaprasad updated ATLAS-220:
---
Description: 
Referenceable tableDefinition = 
InstanceSerialization.fromJsonReferenceable(tableDefinitionJson, true);
EnumValue enumStr = (EnumValue) tableDefinition.get("tableType");

The cast fails with

{noformat}
java.lang.ClassCastException: scala.collection.convert.Wrappers$MapWrapper 
cannot be cast to org.apache.atlas.typesystem.types.EnumValue
at 
org.apache.atlas.service.DefaultMetadataServiceTest.testUpdateEnums(DefaultMetadataServiceTest.java:172)
{noformat}


  was:
Referenceable tableDefinition = 
InstanceSerialization.fromJsonReferenceable(tableDefinitionJson, true);
EnumValue enumStr = (EnumValue) tableDefinition.get("tableType");

The cast fails with

{noformat}
String tableDefinitionJson =
metadataService.getEntityDefinition(TestUtils.TABLE_TYPE, "name", 
(String) table.get("name"));
Referenceable tableDefinition = 
InstanceSerialization.fromJsonReferenceable(tableDefinitionJson, true);
EnumValue enumStr = (EnumValue) tableDefinition.get("tableType");
{noformat}



> Gets on Enum attribute should return EnumValue
> --
>
> Key: ATLAS-220
> URL: https://issues.apache.org/jira/browse/ATLAS-220
> Project: Atlas
>  Issue Type: Bug
>Reporter: Suma Shivaprasad
>
> Referenceable tableDefinition = 
> InstanceSerialization.fromJsonReferenceable(tableDefinitionJson, true);
> EnumValue enumStr = (EnumValue) tableDefinition.get("tableType");
> The cast fails with
> {noformat}
> java.lang.ClassCastException: scala.collection.convert.Wrappers$MapWrapper 
> cannot be cast to org.apache.atlas.typesystem.types.EnumValue
>   at 
> org.apache.atlas.service.DefaultMetadataServiceTest.testUpdateEnums(DefaultMetadataServiceTest.java:172)
> {noformat}



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

[jira] [Updated] (ATLAS-221) UI: Ability to remove added attribute from Tag definition screen

2015-10-12 Thread Erik Bergenholtz (JIRA) 

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

Erik Bergenholtz updated ATLAS-221:
---
Summary: UI: Ability to remove added attribute from Tag definition screen  
(was: UI: Ability to remove added attribute )

> UI: Ability to remove added attribute from Tag definition screen
> 
>
> Key: ATLAS-221
> URL: https://issues.apache.org/jira/browse/ATLAS-221
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.6-incubating
>Reporter: Erik Bergenholtz
>Assignee: Rohit
> Fix For: 0.6-incubating
>
>
> Currently on the Tag screen when creating a new Trait definition it is not 
> possible to remove an added attribute and the UI does not allow you to "save" 
> until you have filled out a value. The UI should allow a user to remove 
> attributes prior to saving - an x or similar should be made available to 
> allow removal of an attribute.



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

[jira] [Created] (ATLAS-221) UI: Ability to remove added attribute

2015-10-12 Thread Erik Bergenholtz (JIRA) 
Erik Bergenholtz created ATLAS-221:
--

 Summary: UI: Ability to remove added attribute 
 Key: ATLAS-221
 URL: https://issues.apache.org/jira/browse/ATLAS-221
 Project: Atlas
  Issue Type: Improvement
Affects Versions: 0.6-incubating
Reporter: Erik Bergenholtz
Assignee: Rohit
 Fix For: 0.6-incubating


Currently on the Tag screen when creating a new Trait definition it is not 
possible to remove an added attribute and the UI does not allow you to "save" 
until you have filled out a value. The UI should allow a user to remove 
attributes prior to saving - an x or similar should be made available to allow 
removal of an attribute.



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

[jira] [Commented] (ATLAS-222) UI: Tag drill down from details screen

2015-10-12 Thread Erik Bergenholtz (JIRA) 

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

Erik Bergenholtz commented on ATLAS-222:


This may require API enhancement to get details of a particular trait/entity 
association.

> UI: Tag drill down from details screen
> --
>
> Key: ATLAS-222
> URL: https://issues.apache.org/jira/browse/ATLAS-222
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.6-incubating
>Reporter: Erik Bergenholtz
>Assignee: Rohit
> Fix For: 0.6-incubating
>
>
> There should be a way of drilling down on a Tag for the ones that have values 
> and display those values. I would appreciate it if someone could come up with 
> a proposal for how this could work.



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