[jira] [Commented] (ATLAS-222) UI: Tag drill down from details screen
[ https://issues.apache.org/jira/browse/ATLAS-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)
[jira] [Created] (ATLAS-222) UI: Tag drill down from details screen
Erik Bergenholtz created ATLAS-222: -- Summary: 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)
[jira] [Created] (ATLAS-221) UI: Ability to remove added attribute
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] [Updated] (ATLAS-221) UI: Ability to remove added attribute from Tag definition screen
[ 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] [Commented] (ATLAS-179) Atlas hook causes mem leak and hive server 2 crashes
[ https://issues.apache.org/jira/browse/ATLAS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953987#comment-14953987 ] Shwetha G S commented on ATLAS-179: --- Committed to master, Thanks [~suma.shivaprasad] for reviewing > Atlas hook causes mem leak and hive server 2 crashes > > > Key: ATLAS-179 > URL: https://issues.apache.org/jira/browse/ATLAS-179 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.5-incubating >Reporter: Shwetha G S >Assignee: Shwetha G S >Priority: Critical > Fix For: trunk > > Attachments: ATLAS-179-v2.patch, ATLAS-179.patch > > > Two issues: > 1. While queueing for ThreadPoolExecutor, we add hive query plan. Looks like > query plan contains the fetch tasks and their job confs. Job confs contain > java.util.Properties and can be huge > 2. We have unbounded queue in ThreadPoolExecutor -- 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"
[ 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] [Updated] (ATLAS-135) Re-model hive type system
[ 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-220) Gets on Enum attribute should return EnumValue
[ 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] [Created] (ATLAS-220) gets on Enum attribute should return EnumValue
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
[ https://issues.apache.org/jira/browse/ATLAS-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-220: --- Summary: Gets on Enum attribute should return EnumValue (was: gets on Enum attribute should return EnumValue) > 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-219) UI: Add ability to detach trait from the entity
[ 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] [Created] (ATLAS-219) UI: Add ability to detach trait from the entity
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-214) UI : For any hive_table, schema/input/output tabs are not displayed
[ 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] [Updated] (ATLAS-216) UI: showing invalid date and time values for hive table
[ https://issues.apache.org/jira/browse/ATLAS-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayub Khan updated ATLAS-216: Labels: ATLAS-UI-BUGS (was: ) > UI: showing invalid date and time values for hive table > --- > > Key: ATLAS-216 > URL: https://issues.apache.org/jira/browse/ATLAS-216 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Ayub Khan > Labels: ATLAS-UI-BUGS > Attachments: Invalid_Timestamps_for_hivetables.png > > > While viewing the hive tables metadata in Atlas UI, I see invalid time values > for createTime and transient_lastDdlTime entries. Please check the attached > UI snapshot. > The same query through API results in correct timestamps. Below is the API > response. > {code} > curl > http://localhost:21000/api/atlas/entity/f286e5d3-0514-4f28-9cef-373473cd > {"requestId":"qtp186909238-384 - > 71055c83-f290-4370-a279-24412918fb58","GUID":"f286e5d3-0514-4f28-9cef-373473cd","definition":"{\n > > \"jsonClass\":\"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference\",\n > \"id\":{\n > \"jsonClass\":\"org.apache.atlas.typesystem.json.InstanceSerialization$_Id\",\n > \"id\":\"f286e5d3-0514-4f28-9cef-373473cd\",\n\"version\":0,\n > \"typeName\":\"hive_table\"\n },\n \"typeName\":\"hive_table\",\n > \"values\":{\n\"tableType\":\"MANAGED_TABLE\",\n > \"name\":\"primary.default.t\",\n\"viewExpandedText\":null,\n > \"createTime\":1444395991,\n\"description\":null,\n > \"temporary\":false,\n\"db\":{\n > \"jsonClass\":\"org.apache.atlas.typesystem.json.InstanceSerialization$_Id\",\n > \"id\":\"cca28963-f7b1-44fd-a631-f4b6f3b09612\",\n > \"version\":0,\n \"typeName\":\"hive_db\"\n},\n > \"viewOriginalText\":null,\n\"retention\":0,\n\"tableName\":\"t\",\n > \"columns\":[\n {\n > \"jsonClass\":\"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference\",\n > \"id\":{\n > \"jsonClass\":\"org.apache.atlas.typesystem.json.InstanceSerialization$_Id\",\n > \"id\":\"5f89e208-a9ff-40eb-912b-b4394f8d8c0e\",\n > \"version\":0,\n \"typeName\":\"hive_column\"\n},\n > \"typeName\":\"hive_column\",\n\"values\":{\n > \"comment\":null,\n > \"qualifiedName\":\"primary.default.t.salary\",\n > \"type\":\"string\",\n \"name\":\"salary\"\n},\n > \"traitNames\":[\n \n],\n\"traits\":{\n \n > }\n },\n {\n > \"jsonClass\":\"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference\",\n > \"id\":{\n > \"jsonClass\":\"org.apache.atlas.typesystem.json.InstanceSerialization$_Id\",\n > \"id\":\"14870ed2-f596-46a3-9500-c720e559703e\",\n > \"version\":0,\n \"typeName\":\"hive_column\"\n},\n > \"typeName\":\"hive_column\",\n\"values\":{\n > \"comment\":null,\n > \"qualifiedName\":\"primary.default.t.integer\",\n > \"type\":\"int\",\n \"name\":\"integer\"\n},\n > \"traitNames\":[\n \n],\n\"traits\":{\n \n > }\n },\n {\n > \"jsonClass\":\"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference\",\n > \"id\":{\n > \"jsonClass\":\"org.apache.atlas.typesystem.json.InstanceSerialization$_Id\",\n > \"id\":\"535e002f-f7ed-4e6e-a363-4cc38ebc3b46\",\n > \"version\":0,\n \"typeName\":\"hive_column\"\n},\n > \"typeName\":\"hive_column\",\n\"values\":{\n > \"comment\":null,\n > \"qualifiedName\":\"primary.default.t.number\",\n > \"type\":\"int\",\n \"name\":\"number\"\n},\n > \"traitNames\":[\n \n],\n\"traits\":{\n \n > }\n }\n],\n\"comment\":null,\n\"lastAccessTime\":0,\n > \"owner\":\"apathan\",\n\"sd\":{\n > \"jsonClass\":\"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference\",\n > \"id\":{\n > \"jsonClass\":\"org.apache.atlas.typesystem.json.InstanceSerialization$_Id\",\n > \"id\":\"168ba76f-c5db-4398-bded-ed25bb626785\",\n > \"version\":0,\n\"typeName\":\"hive_storagedesc\"\n },\n > \"typeName\":\"hive_storagedesc\",\n \"values\":{\n > \"location\":\"hdfs:\/\/localhost:9000\/user\/hive\/warehouse\/t\",\n > \"serdeInfo\":{\n > \"jsonClass\":\"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct\",\n > \"typeName\":\"hive_serde\",\n \"values\":{\n > \"seri
[jira] [Created] (ATLAS-218) UI: Use different icons for entity and process in the lineage graph
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
[ 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] [Commented] (ATLAS-199) webapp build fails (grunt + tests)
[ https://issues.apache.org/jira/browse/ATLAS-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)