[jira] [Commented] (ATLAS-232) Fix the API incompatibility introduced in ATLAS-58
[ https://issues.apache.org/jira/browse/ATLAS-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14979977#comment-14979977 ] Shwetha G S commented on ATLAS-232: --- In 0.5 release, submit API was in 'entity' path. As part of ATLAS-58, I moved it to 'entities' path as submit is a batch API. I didn't know anyone who was using 0.5, thought its better to fix it before anyone starts using atlas in production. ATLAS-58 will be part of 0.6 release which is yet to be released. Looks like some users are already using atlas in production, so I moved submit API back to 'entity' path, and current trunk code is compatible with 0.5. Makes sense? > Fix the API incompatibility introduced in ATLAS-58 > -- > > Key: ATLAS-232 > URL: https://issues.apache.org/jira/browse/ATLAS-232 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S > Fix For: 0.6-incubating, trunk > > Attachments: ATLAS-232.patch > > > 1. Entity create should handle with single entity json or jsonarray > 2. Move the APIs from entities/entity -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-136) Add trait API to org.apache.atlas.AtlasClient
[ https://issues.apache.org/jira/browse/ATLAS-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14979995#comment-14979995 ] Shwetha G S edited comment on ATLAS-136 at 10/29/15 7:55 AM: - [~vantonevich], are you working on this? will you address the review comments [~patel_satya], addTrait() function in AtlasClient is a simple wrapper over rest API. Feel free to provide a patch if you have one was (Author: shwethags): @vantonevich, are you working on this? will you address the review comments [~patel_satya], addTrait() function in AtlasClient is a simple wrapper over rest API. Feel free to provide a patch if you have one > Add trait API to org.apache.atlas.AtlasClient > - > > Key: ATLAS-136 > URL: https://issues.apache.org/jira/browse/ATLAS-136 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Vladimir Antonevich` > Fix For: 0.6-incubating > > Attachments: atlas.client.patch > > > API to manipulate entity traits must be added to > org.apache.atlas.AtlasClient. These should include methods to add/remove a > trait POST/DELETE to /api/atlas/entities/{guid}/traits[/traitName], as > supported by exposed entities resource -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-136) Add trait API to org.apache.atlas.AtlasClient
[ https://issues.apache.org/jira/browse/ATLAS-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14979995#comment-14979995 ] Shwetha G S commented on ATLAS-136: --- @vantonevich, are you working on this? will you address the review comments [~patel_satya], addTrait() function in AtlasClient is a simple wrapper over rest API. Feel free to provide a patch if you have one > Add trait API to org.apache.atlas.AtlasClient > - > > Key: ATLAS-136 > URL: https://issues.apache.org/jira/browse/ATLAS-136 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Vladimir Antonevich` > Fix For: 0.6-incubating > > Attachments: atlas.client.patch > > > API to manipulate entity traits must be added to > org.apache.atlas.AtlasClient. These should include methods to add/remove a > trait POST/DELETE to /api/atlas/entities/{guid}/traits[/traitName], as > supported by exposed entities resource -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-208) Remove "\n" characters in the REST API json response
[ https://issues.apache.org/jira/browse/ATLAS-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-208: -- Assignee: Ayub Khan > Remove "\n" characters in the REST API json response > > > Key: ATLAS-208 > URL: https://issues.apache.org/jira/browse/ATLAS-208 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Ayub Khan >Assignee: Ayub Khan >Priority: Minor > Fix For: 0.6-incubating > > Attachments: ATLAS-208.txt > > > "\n" characters are seen in REST API response, which is not needed and can be > removed.. > curl -k -s --negotiate -u : > http://localhost:21000/api/atlas/types/traitWithSuperTypefxgy2bhnev | python > -m json.tool > { > "definition": "{\n \"enumTypes\":[\n\n ],\n \"structTypes\":[\n > \n ],\n \"traitTypes\":[\n{\n \"superTypes\":[\n > \"traitSuperType1fxgy2bhnev\",\n\"traitSuperType2fxgy2bhnev\"\n > ],\n > \"hierarchicalMetaTypeName\":\"org.apache.atlas.typesystem.types.TraitType\",\n > \"typeName\":\"traitWithSuperTypefxgy2bhnev\",\n > \"attributeDefinitions\":[\n{\n \"name\":\"string\",\n >\"dataTypeName\":\"string\",\n \"multiplicity\":\"optional\",\n >\"isComposite\":false,\n \"isUnique\":false,\n > \"isIndexable\":true,\n \"reverseAttributeName\":null\n}\n >]\n}\n ],\n \"classTypes\":[\n\n ]\n}", > "requestId": "1146437560@qtp-1778535015-267 - > d982526c-f6b6-4fe5-a4ed-722cbc29eb38", > "typeName": "traitWithSuperTypefxgy2bhnev" > } -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-208) Remove "\n" characters in the REST API json response
[ https://issues.apache.org/jira/browse/ATLAS-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-208: -- Assignee: Satya Narayan (was: Ayub Khan) > Remove "\n" characters in the REST API json response > > > Key: ATLAS-208 > URL: https://issues.apache.org/jira/browse/ATLAS-208 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Ayub Khan >Assignee: Satya Narayan >Priority: Minor > Fix For: 0.6-incubating > > Attachments: ATLAS-208.txt > > > "\n" characters are seen in REST API response, which is not needed and can be > removed.. > curl -k -s --negotiate -u : > http://localhost:21000/api/atlas/types/traitWithSuperTypefxgy2bhnev | python > -m json.tool > { > "definition": "{\n \"enumTypes\":[\n\n ],\n \"structTypes\":[\n > \n ],\n \"traitTypes\":[\n{\n \"superTypes\":[\n > \"traitSuperType1fxgy2bhnev\",\n\"traitSuperType2fxgy2bhnev\"\n > ],\n > \"hierarchicalMetaTypeName\":\"org.apache.atlas.typesystem.types.TraitType\",\n > \"typeName\":\"traitWithSuperTypefxgy2bhnev\",\n > \"attributeDefinitions\":[\n{\n \"name\":\"string\",\n >\"dataTypeName\":\"string\",\n \"multiplicity\":\"optional\",\n >\"isComposite\":false,\n \"isUnique\":false,\n > \"isIndexable\":true,\n \"reverseAttributeName\":null\n}\n >]\n}\n ],\n \"classTypes\":[\n\n ]\n}", > "requestId": "1146437560@qtp-1778535015-267 - > d982526c-f6b6-4fe5-a4ed-722cbc29eb38", > "typeName": "traitWithSuperTypefxgy2bhnev" > } -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-238) atlas_start.py- the Atlas server won’t restart after umproper shutdown
[ https://issues.apache.org/jira/browse/ATLAS-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-238: -- Assignee: Naima Djouhri > atlas_start.py- the Atlas server won’t restart after umproper shutdown > --- > > Key: ATLAS-238 > URL: https://issues.apache.org/jira/browse/ATLAS-238 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Naima Djouhri >Assignee: Naima Djouhri >Priority: Minor > > Steps to reproduce > 1.Open a Windows/terminal/shell and start the Atlas server with > “atlas_start.py” script > 2.Log in to your Atlas server http://localhost:21000/ to make sure that > you can connect > 3. Close the Windows/terminal/shell where the Atlas server process > started –step1 > Or just kill the process - the process id can be found in a file called > “atlas.pid” in the logs directory (this file is created by the > “atlas_start.py” script > 4.Try to login to your Atlas server again and a “Unable to connect” > message will pop up > 5.From a command prompt Windows/ Terminal/Shell start the server > (atlas_start.py) > 6.A message “atlas.pid already exists, exiting” will pop up in the screen > and the server will not start > Expected Result > The server should start since it has been shut down >Actual: > The server can not start > If the server is stopped using “atlas_stop.py” , the server restart after > running "atlas_start.py" with no issue. > Since the server has not been stopped with “atlas_stop.py” that kill the > process, and delete the “atlas.pid” file, the script “atlas_start.py” will > not start the server. > The turnaround is to delete the “atlas.pid” file in the logs directory but it > is not always obvious, and user friendly!! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-136) Add trait API to org.apache.atlas.AtlasClient
[ https://issues.apache.org/jira/browse/ATLAS-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980005#comment-14980005 ] ASF GitHub Bot commented on ATLAS-136: -- GitHub user rishabhbhardwaj opened a pull request: https://github.com/apache/incubator-atlas/pull/20 ATLAS-136 Add trait API to org.apache.atlas.AtlasClient Added the following trait API methods in AtlasClient createTrait addTrait deleteTrait I have tested the methods and they are working fine. Kindly review the changes. You can merge this pull request into a Git repository by running: $ git pull https://github.com/rishabhbhardwaj/incubator-atlas master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-atlas/pull/20.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #20 commit fd23d4c998b1714a85479034c90b2d324b84ee81 Author: Rishabh Bhardwaj Date: 2015-10-13T13:06:14Z Atlas-201 Renamed org.apache.atlas.Main to org.apache.atlas.Atlas. commit 66fe404120a48a4af25b6aa4b1081b7c0f8cd155 Author: Rishabh Bhardwaj Date: 2015-10-15T06:07:40Z Merge remote-tracking branch 'upstream/master' commit 715401ae4d34e922753fc3356bd52ae04a2d875c Author: Rishabh Bhardwaj Date: 2015-10-21T17:36:49Z Merge remote-tracking branch 'upstream/master' commit 071425baa7bab1c8d34e45cddad6df5357b91b57 Author: Rishabh Bhardwaj Date: 2015-10-26T06:06:17Z Merge remote-tracking branch 'upstream/master' commit a27fb7af29beafebcca8e1596a7ce4978badf8d2 Author: Rishabh Bhardwaj Date: 2015-10-28T10:36:54Z Merge remote-tracking branch 'upstream/master' commit aac3f83d9ee255e24fe92b56532772358b69d135 Author: Rishabh Bhardwaj Date: 2015-10-29T07:55:12Z Merge remote-tracking branch 'upstream/master' commit c31d5ed98a80b369c7855a65d9411a37637247cd Author: Rishabh Bhardwaj Date: 2015-10-29T07:57:26Z ATLAS-136 Add trait API to org.apache.atlas.AtlasClient > Add trait API to org.apache.atlas.AtlasClient > - > > Key: ATLAS-136 > URL: https://issues.apache.org/jira/browse/ATLAS-136 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Vladimir Antonevich` > Fix For: 0.6-incubating > > Attachments: atlas.client.patch > > > API to manipulate entity traits must be added to > org.apache.atlas.AtlasClient. These should include methods to add/remove a > trait POST/DELETE to /api/atlas/entities/{guid}/traits[/traitName], as > supported by exposed entities resource -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-238) atlas_start.py- the Atlas server won’t restart after umproper shutdown
[ https://issues.apache.org/jira/browse/ATLAS-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980012#comment-14980012 ] Shwetha G S commented on ATLAS-238: --- Done. Thanks for taking it up > atlas_start.py- the Atlas server won’t restart after umproper shutdown > --- > > Key: ATLAS-238 > URL: https://issues.apache.org/jira/browse/ATLAS-238 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Naima Djouhri >Assignee: Naima Djouhri >Priority: Minor > > Steps to reproduce > 1.Open a Windows/terminal/shell and start the Atlas server with > “atlas_start.py” script > 2.Log in to your Atlas server http://localhost:21000/ to make sure that > you can connect > 3. Close the Windows/terminal/shell where the Atlas server process > started –step1 > Or just kill the process - the process id can be found in a file called > “atlas.pid” in the logs directory (this file is created by the > “atlas_start.py” script > 4.Try to login to your Atlas server again and a “Unable to connect” > message will pop up > 5.From a command prompt Windows/ Terminal/Shell start the server > (atlas_start.py) > 6.A message “atlas.pid already exists, exiting” will pop up in the screen > and the server will not start > Expected Result > The server should start since it has been shut down >Actual: > The server can not start > If the server is stopped using “atlas_stop.py” , the server restart after > running "atlas_start.py" with no issue. > Since the server has not been stopped with “atlas_stop.py” that kill the > process, and delete the “atlas.pid” file, the script “atlas_start.py” will > not start the server. > The turnaround is to delete the “atlas.pid” file in the logs directory but it > is not always obvious, and user friendly!! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-136) Add trait API to org.apache.atlas.AtlasClient
[ https://issues.apache.org/jira/browse/ATLAS-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rishabh Bhardwaj updated ATLAS-136: --- Attachment: ATLAS-136.patch > Add trait API to org.apache.atlas.AtlasClient > - > > Key: ATLAS-136 > URL: https://issues.apache.org/jira/browse/ATLAS-136 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Vladimir Antonevich` > Fix For: 0.6-incubating > > Attachments: ATLAS-136.patch, atlas.client.patch > > > API to manipulate entity traits must be added to > org.apache.atlas.AtlasClient. These should include methods to add/remove a > trait POST/DELETE to /api/atlas/entities/{guid}/traits[/traitName], as > supported by exposed entities resource -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-247) hive_column leve lineage
[ https://issues.apache.org/jira/browse/ATLAS-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980014#comment-14980014 ] Shwetha G S commented on ATLAS-247: --- [~teeupdata], implementing column level lineage requires hive to provide this lineage information. Once the lineage information is available from hive, we need to re-model such that atlas can provide lineage for both column and table in a generic way. Right now, we are waiting for lineage info from hive > hive_column leve lineage > > > Key: ATLAS-247 > URL: https://issues.apache.org/jira/browse/ATLAS-247 > Project: Atlas > Issue Type: New Feature >Affects Versions: 0.5-incubating >Reporter: Herman Yu > > hive_column is not inherited from DataSet, thus can't be using hive_process > to track column level lineages > Is there specific reason that hive_column is not inheriting from Data Set? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-248) Enhance an implemented model
[ https://issues.apache.org/jira/browse/ATLAS-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S resolved ATLAS-248. --- Resolution: Duplicate > Enhance an implemented model > > > Key: ATLAS-248 > URL: https://issues.apache.org/jira/browse/ATLAS-248 > Project: Atlas > Issue Type: New Feature >Affects Versions: 0.5-incubating >Reporter: Herman Yu > > We have a model implemented, with entities/Tags created for different > classType definitions, is it possible to enhance the model (e.g. update > classType definitions) without recreating those entities/tags? It seems to > changes are only addictive for now. > Is an import/export feature going to help? export to JSON and then > modify/update JSON and then import back? > This might be related to ATLAS-171, which was asking for the ability of > updating exiting classType Definitions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-248) Enhance an implemented model
[ https://issues.apache.org/jira/browse/ATLAS-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980017#comment-14980017 ] Shwetha G S commented on ATLAS-248: --- Yes, ATLAS-171 will provide ability to update types - add an attribute/super type > Enhance an implemented model > > > Key: ATLAS-248 > URL: https://issues.apache.org/jira/browse/ATLAS-248 > Project: Atlas > Issue Type: New Feature >Affects Versions: 0.5-incubating >Reporter: Herman Yu > > We have a model implemented, with entities/Tags created for different > classType definitions, is it possible to enhance the model (e.g. update > classType definitions) without recreating those entities/tags? It seems to > changes are only addictive for now. > Is an import/export feature going to help? export to JSON and then > modify/update JSON and then import back? > This might be related to ATLAS-171, which was asking for the ability of > updating exiting classType Definitions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-242) lineage hive table schema REST API does not accept any tableName value
[ https://issues.apache.org/jira/browse/ATLAS-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980030#comment-14980030 ] Shwetha G S commented on ATLAS-242: --- The table name should be of format - dbname.tablename@clustername > lineage hive table schema REST API does not accept any tableName value > -- > > Key: ATLAS-242 > URL: https://issues.apache.org/jira/browse/ATLAS-242 > Project: Atlas > Issue Type: Bug >Reporter: David Kaspar > > This issue is filed for "RangerAtlasDemo_v4.ova" VM-image release. > When I call: > http://127.0.0.1:21000/api/atlas/lineage/hive/table/{tableName}/schema > REST API method, then it always returns 404 Not Found and returns an error > which claims that given {tableName} does not exist. > Since REST API documentation (application.wadl) does not state details, I > have tried to use existing Hive table names, existing GUIDs of Hive tables > but none of them works. > Similarly for /api/atlas/lineage/hive/table/{tableName}/outputs/graph and > /api/atlas/lineage/hive/table/{tableName}/inputs/graph. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-242) lineage hive table schema REST API does not accept any tableName value
[ https://issues.apache.org/jira/browse/ATLAS-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980030#comment-14980030 ] Shwetha G S edited comment on ATLAS-242 at 10/29/15 8:17 AM: - The table name should be of fully qualified name of format - dbname.tablename@clustername was (Author: shwethags): The table name should be of format - dbname.tablename@clustername > lineage hive table schema REST API does not accept any tableName value > -- > > Key: ATLAS-242 > URL: https://issues.apache.org/jira/browse/ATLAS-242 > Project: Atlas > Issue Type: Bug >Reporter: David Kaspar > > This issue is filed for "RangerAtlasDemo_v4.ova" VM-image release. > When I call: > http://127.0.0.1:21000/api/atlas/lineage/hive/table/{tableName}/schema > REST API method, then it always returns 404 Not Found and returns an error > which claims that given {tableName} does not exist. > Since REST API documentation (application.wadl) does not state details, I > have tried to use existing Hive table names, existing GUIDs of Hive tables > but none of them works. > Similarly for /api/atlas/lineage/hive/table/{tableName}/outputs/graph and > /api/atlas/lineage/hive/table/{tableName}/inputs/graph. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-242) lineage hive table schema REST API does not accept any tableName value
[ https://issues.apache.org/jira/browse/ATLAS-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980033#comment-14980033 ] David Kaspar commented on ATLAS-242: Hi, I am on vacation until November 1st, 2015. If you need any immediate assistance, please, contact my manager Martin Ryzl (martin.r...@merck.com). Otherwise I will get back to you when I return. Thanks, David Notice: This e-mail message, together with any attachments, contains information of Merck & Co., Inc. (2000 Galloping Hill Road, Kenilworth, New Jersey, USA 07033), and/or its affiliates Direct contact information for affiliates is available at http://www.merck.com/contact/contacts.html) that may be confidential, proprietary copyrighted and/or legally privileged. It is intended solely for the use of the individual or entity named on this message. If you are not the intended recipient, and have received this message in error, please notify us immediately by reply e-mail and then delete it from your system. > lineage hive table schema REST API does not accept any tableName value > -- > > Key: ATLAS-242 > URL: https://issues.apache.org/jira/browse/ATLAS-242 > Project: Atlas > Issue Type: Bug >Reporter: David Kaspar > > This issue is filed for "RangerAtlasDemo_v4.ova" VM-image release. > When I call: > http://127.0.0.1:21000/api/atlas/lineage/hive/table/{tableName}/schema > REST API method, then it always returns 404 Not Found and returns an error > which claims that given {tableName} does not exist. > Since REST API documentation (application.wadl) does not state details, I > have tried to use existing Hive table names, existing GUIDs of Hive tables > but none of them works. > Similarly for /api/atlas/lineage/hive/table/{tableName}/outputs/graph and > /api/atlas/lineage/hive/table/{tableName}/inputs/graph. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-136) Add trait API to org.apache.atlas.AtlasClient
[ https://issues.apache.org/jira/browse/ATLAS-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-136: -- Assignee: Rishabh Bhardwaj > Add trait API to org.apache.atlas.AtlasClient > - > > Key: ATLAS-136 > URL: https://issues.apache.org/jira/browse/ATLAS-136 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Vladimir Antonevich` >Assignee: Rishabh Bhardwaj > Fix For: 0.6-incubating > > Attachments: ATLAS-136.patch, atlas.client.patch > > > API to manipulate entity traits must be added to > org.apache.atlas.AtlasClient. These should include methods to add/remove a > trait POST/DELETE to /api/atlas/entities/{guid}/traits[/traitName], as > supported by exposed entities resource -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-262) UI: Entities displayed after attaching long tags cab be handled properly
Ayub Khan created ATLAS-262: --- Summary: UI: Entities displayed after attaching long tags cab be handled properly Key: ATLAS-262 URL: https://issues.apache.org/jira/browse/ATLAS-262 Project: Atlas Issue Type: Bug Reporter: Ayub Khan Assignee: Anilsg UI: Entities displayed after attaching long tags cab be handled properly Attaching the snsphot for reference. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-262) UI: Entities displayed after attaching long tags can be handled properly
[ https://issues.apache.org/jira/browse/ATLAS-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayub Khan updated ATLAS-262: Summary: UI: Entities displayed after attaching long tags can be handled properly (was: UI: Entities displayed after attaching long tags cab be handled properly) > UI: Entities displayed after attaching long tags can be handled properly > > > Key: ATLAS-262 > URL: https://issues.apache.org/jira/browse/ATLAS-262 > Project: Atlas > Issue Type: Bug >Reporter: Ayub Khan >Assignee: Anilsg > Attachments: Apache-Atlas-Entities-with-long-tags.png > > > UI: Entities displayed after attaching long tags cab be handled properly > Attaching the snsphot for reference. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-262) UI: Entities displayed after attaching long tags can be handled properly
[ https://issues.apache.org/jira/browse/ATLAS-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayub Khan updated ATLAS-262: Attachment: Apache-Atlas-Entities-with-long-tags.png > UI: Entities displayed after attaching long tags can be handled properly > > > Key: ATLAS-262 > URL: https://issues.apache.org/jira/browse/ATLAS-262 > Project: Atlas > Issue Type: Bug >Reporter: Ayub Khan >Assignee: Anilsg > Attachments: Apache-Atlas-Entities-with-long-tags.png > > > UI: Entities displayed after attaching long tags cab be handled properly > Attaching the snsphot for reference. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-211) UI: UI Facelift
[ https://issues.apache.org/jira/browse/ATLAS-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980117#comment-14980117 ] Ayub Khan commented on ATLAS-211: - 9) Entities displayed after attaching long tags can be handled properly(https://issues.apache.org/jira/browse/ATLAS-262). > UI: UI Facelift > --- > > Key: ATLAS-211 > URL: https://issues.apache.org/jira/browse/ATLAS-211 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Anilsg > Labels: patch-available > Fix For: 0.6-incubating > > Attachments: ATLAS-211-ATLAS-224_v0.patch, > ATLAS-211-ATLAS-224_v1.patch, Apache-Atlas-Same-Request-Twice.png, > Apache-Atlas-long-trait-name.png, Screen Shot 2015-10-26 at 11.29.19 PM.png, > Screen Shot 2015-10-26 at 11.34.57 PM.png, Screen Shot 2015-10-28 at 9.35.53 > AM.png, Screen Shot 2015-10-29 at 9.56.34 AM.png > > > Adopt new look and feel for all screens as shown here: > http://mprhost.com/hw/atlas/rahul/atlashtml/search.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-228) UI: JSON response for the successful tag addition can be hidden from the end user
[ https://issues.apache.org/jira/browse/ATLAS-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayub Khan updated ATLAS-228: Assignee: Anilsg > UI: JSON response for the successful tag addition can be hidden from the end > user > - > > Key: ATLAS-228 > URL: https://issues.apache.org/jira/browse/ATLAS-228 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Ayub Khan >Assignee: Anilsg > Labels: ATLAS-UI-BUGS > Attachments: Adding_tag_response.png > > > Currently, upon successful completion of tag addition, Atlas displays JSOn > response in the UI. From an end user's perspective, JSON response is not > required and can be hidden. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-211) UI: UI Facelift
[ https://issues.apache.org/jira/browse/ATLAS-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980117#comment-14980117 ] Ayub Khan edited comment on ATLAS-211 at 10/29/15 9:51 AM: --- 9) Entities displayed after attaching long tags can be handled properly(https://issues.apache.org/jira/browse/ATLAS-262). 10) Successful creation of tag results in dumping JSON on the page, which can be removed.(https://issues.apache.org/jira/browse/ATLAS-228). Attaching snapshot for refrence. was (Author: ayubkhan): 9) Entities displayed after attaching long tags can be handled properly(https://issues.apache.org/jira/browse/ATLAS-262). > UI: UI Facelift > --- > > Key: ATLAS-211 > URL: https://issues.apache.org/jira/browse/ATLAS-211 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Anilsg > Labels: patch-available > Fix For: 0.6-incubating > > Attachments: ATLAS-211-ATLAS-224_v0.patch, > ATLAS-211-ATLAS-224_v1.patch, Apache-Atlas-Same-Request-Twice.png, > Apache-Atlas-long-trait-name.png, Screen Shot 2015-10-26 at 11.29.19 PM.png, > Screen Shot 2015-10-26 at 11.34.57 PM.png, Screen Shot 2015-10-28 at 9.35.53 > AM.png, Screen Shot 2015-10-29 at 9.56.34 AM.png > > > Adopt new look and feel for all screens as shown here: > http://mprhost.com/hw/atlas/rahul/atlashtml/search.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-211) UI: UI Facelift
[ https://issues.apache.org/jira/browse/ATLAS-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980117#comment-14980117 ] Ayub Khan edited comment on ATLAS-211 at 10/29/15 9:52 AM: --- [~Anilg] 9) Entities displayed after attaching long tags can be handled properly(https://issues.apache.org/jira/browse/ATLAS-262). 10) Successful creation of tag results in dumping JSON on the page, which can be removed.(https://issues.apache.org/jira/browse/ATLAS-228). Attaching snapshot for refrence. was (Author: ayubkhan): 9) Entities displayed after attaching long tags can be handled properly(https://issues.apache.org/jira/browse/ATLAS-262). 10) Successful creation of tag results in dumping JSON on the page, which can be removed.(https://issues.apache.org/jira/browse/ATLAS-228). Attaching snapshot for refrence. > UI: UI Facelift > --- > > Key: ATLAS-211 > URL: https://issues.apache.org/jira/browse/ATLAS-211 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Anilsg > Labels: patch-available > Fix For: 0.6-incubating > > Attachments: ATLAS-211-ATLAS-224_v0.patch, > ATLAS-211-ATLAS-224_v1.patch, Apache-Atlas-Same-Request-Twice.png, > Apache-Atlas-long-trait-name.png, Screen Shot 2015-10-26 at 11.29.19 PM.png, > Screen Shot 2015-10-26 at 11.34.57 PM.png, Screen Shot 2015-10-28 at 9.35.53 > AM.png, Screen Shot 2015-10-29 at 9.56.34 AM.png > > > Adopt new look and feel for all screens as shown here: > http://mprhost.com/hw/atlas/rahul/atlashtml/search.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-211) UI: UI Facelift
[ https://issues.apache.org/jira/browse/ATLAS-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayub Khan updated ATLAS-211: Attachment: Apache-Atlas-Tag-Creation-Dumps-Json.png > UI: UI Facelift > --- > > Key: ATLAS-211 > URL: https://issues.apache.org/jira/browse/ATLAS-211 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Anilsg > Labels: patch-available > Fix For: 0.6-incubating > > Attachments: ATLAS-211-ATLAS-224_v0.patch, > ATLAS-211-ATLAS-224_v1.patch, Apache-Atlas-Same-Request-Twice.png, > Apache-Atlas-Tag-Creation-Dumps-Json.png, Apache-Atlas-long-trait-name.png, > Screen Shot 2015-10-26 at 11.29.19 PM.png, Screen Shot 2015-10-26 at 11.34.57 > PM.png, Screen Shot 2015-10-28 at 9.35.53 AM.png, Screen Shot 2015-10-29 at > 9.56.34 AM.png > > > Adopt new look and feel for all screens as shown here: > http://mprhost.com/hw/atlas/rahul/atlashtml/search.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-232) Fix the API incompatibility introduced in ATLAS-58
[ https://issues.apache.org/jira/browse/ATLAS-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980391#comment-14980391 ] Tom Beerbower commented on ATLAS-232: - [~shwethags], It looks like the methods were moved back to the EntityResource class from EntitiesResource class but the Path annotation in EntityResource prior to ATLAS-58 was... {code}@Path("entities"){code} and is now ... {code}@Path("entity"){code} So, the API to create entities that was in 0.5 ... {code}POST http://c6401.ambari.apache.org:21000/api/atlas/entities{code} is now ... {code}POST http://c6401.ambari.apache.org:21000/api/atlas/entity{code} Same is true for all of the entity resource APIs. To be compatible with the APIs in 0.5 shouldn't we revert the change to the Path annotation introduced in ATLAS-58? > Fix the API incompatibility introduced in ATLAS-58 > -- > > Key: ATLAS-232 > URL: https://issues.apache.org/jira/browse/ATLAS-232 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S > Fix For: 0.6-incubating, trunk > > Attachments: ATLAS-232.patch > > > 1. Entity create should handle with single entity json or jsonarray > 2. Move the APIs from entities/entity -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-136) Add trait API to org.apache.atlas.AtlasClient
[ https://issues.apache.org/jira/browse/ATLAS-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980471#comment-14980471 ] Vladimir Antonevich` commented on ATLAS-136: I cannot merge this pull request, somebody please... > Add trait API to org.apache.atlas.AtlasClient > - > > Key: ATLAS-136 > URL: https://issues.apache.org/jira/browse/ATLAS-136 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Vladimir Antonevich` >Assignee: Rishabh Bhardwaj > Fix For: 0.6-incubating > > Attachments: ATLAS-136.patch, atlas.client.patch > > > API to manipulate entity traits must be added to > org.apache.atlas.AtlasClient. These should include methods to add/remove a > trait POST/DELETE to /api/atlas/entities/{guid}/traits[/traitName], as > supported by exposed entities resource -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-208) Remove "\n" characters in the REST API json response
[ https://issues.apache.org/jira/browse/ATLAS-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980577#comment-14980577 ] Satya Narayan commented on ATLAS-208: - added fix for submit api also, kindly review the changes > Remove "\n" characters in the REST API json response > > > Key: ATLAS-208 > URL: https://issues.apache.org/jira/browse/ATLAS-208 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Ayub Khan >Assignee: Satya Narayan >Priority: Minor > Fix For: 0.6-incubating > > Attachments: ATLAS-208.txt > > > "\n" characters are seen in REST API response, which is not needed and can be > removed.. > curl -k -s --negotiate -u : > http://localhost:21000/api/atlas/types/traitWithSuperTypefxgy2bhnev | python > -m json.tool > { > "definition": "{\n \"enumTypes\":[\n\n ],\n \"structTypes\":[\n > \n ],\n \"traitTypes\":[\n{\n \"superTypes\":[\n > \"traitSuperType1fxgy2bhnev\",\n\"traitSuperType2fxgy2bhnev\"\n > ],\n > \"hierarchicalMetaTypeName\":\"org.apache.atlas.typesystem.types.TraitType\",\n > \"typeName\":\"traitWithSuperTypefxgy2bhnev\",\n > \"attributeDefinitions\":[\n{\n \"name\":\"string\",\n >\"dataTypeName\":\"string\",\n \"multiplicity\":\"optional\",\n >\"isComposite\":false,\n \"isUnique\":false,\n > \"isIndexable\":true,\n \"reverseAttributeName\":null\n}\n >]\n}\n ],\n \"classTypes\":[\n\n ]\n}", > "requestId": "1146437560@qtp-1778535015-267 - > d982526c-f6b6-4fe5-a4ed-722cbc29eb38", > "typeName": "traitWithSuperTypefxgy2bhnev" > } -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-208) Remove "\n" characters in the REST API json response
[ https://issues.apache.org/jira/browse/ATLAS-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Satya Narayan updated ATLAS-208: Attachment: ATLAS-208.txt > Remove "\n" characters in the REST API json response > > > Key: ATLAS-208 > URL: https://issues.apache.org/jira/browse/ATLAS-208 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Ayub Khan >Assignee: Satya Narayan >Priority: Minor > Fix For: 0.6-incubating > > Attachments: ATLAS-208.txt, ATLAS-208.txt > > > "\n" characters are seen in REST API response, which is not needed and can be > removed.. > curl -k -s --negotiate -u : > http://localhost:21000/api/atlas/types/traitWithSuperTypefxgy2bhnev | python > -m json.tool > { > "definition": "{\n \"enumTypes\":[\n\n ],\n \"structTypes\":[\n > \n ],\n \"traitTypes\":[\n{\n \"superTypes\":[\n > \"traitSuperType1fxgy2bhnev\",\n\"traitSuperType2fxgy2bhnev\"\n > ],\n > \"hierarchicalMetaTypeName\":\"org.apache.atlas.typesystem.types.TraitType\",\n > \"typeName\":\"traitWithSuperTypefxgy2bhnev\",\n > \"attributeDefinitions\":[\n{\n \"name\":\"string\",\n >\"dataTypeName\":\"string\",\n \"multiplicity\":\"optional\",\n >\"isComposite\":false,\n \"isUnique\":false,\n > \"isIndexable\":true,\n \"reverseAttributeName\":null\n}\n >]\n}\n ],\n \"classTypes\":[\n\n ]\n}", > "requestId": "1146437560@qtp-1778535015-267 - > d982526c-f6b6-4fe5-a4ed-722cbc29eb38", > "typeName": "traitWithSuperTypefxgy2bhnev" > } -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-208) Remove "\n" characters in the REST API json response
[ https://issues.apache.org/jira/browse/ATLAS-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Satya Narayan updated ATLAS-208: Attachment: (was: ATLAS-208.txt) > Remove "\n" characters in the REST API json response > > > Key: ATLAS-208 > URL: https://issues.apache.org/jira/browse/ATLAS-208 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Ayub Khan >Assignee: Satya Narayan >Priority: Minor > Fix For: 0.6-incubating > > Attachments: ATLAS-208.txt > > > "\n" characters are seen in REST API response, which is not needed and can be > removed.. > curl -k -s --negotiate -u : > http://localhost:21000/api/atlas/types/traitWithSuperTypefxgy2bhnev | python > -m json.tool > { > "definition": "{\n \"enumTypes\":[\n\n ],\n \"structTypes\":[\n > \n ],\n \"traitTypes\":[\n{\n \"superTypes\":[\n > \"traitSuperType1fxgy2bhnev\",\n\"traitSuperType2fxgy2bhnev\"\n > ],\n > \"hierarchicalMetaTypeName\":\"org.apache.atlas.typesystem.types.TraitType\",\n > \"typeName\":\"traitWithSuperTypefxgy2bhnev\",\n > \"attributeDefinitions\":[\n{\n \"name\":\"string\",\n >\"dataTypeName\":\"string\",\n \"multiplicity\":\"optional\",\n >\"isComposite\":false,\n \"isUnique\":false,\n > \"isIndexable\":true,\n \"reverseAttributeName\":null\n}\n >]\n}\n ],\n \"classTypes\":[\n\n ]\n}", > "requestId": "1146437560@qtp-1778535015-267 - > d982526c-f6b6-4fe5-a4ed-722cbc29eb38", > "typeName": "traitWithSuperTypefxgy2bhnev" > } -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-261) If we have "/" in the search query(example: "abc/", UI fires the same request twice. verified the same using network trace as well.
[ https://issues.apache.org/jira/browse/ATLAS-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Patel reassigned ATLAS-261: -- Assignee: Sanjay Patel (was: Darshan Kumar) > If we have "/" in the search query(example: "abc/", UI fires the same request > twice. verified the same using network trace as well. > --- > > Key: ATLAS-261 > URL: https://issues.apache.org/jira/browse/ATLAS-261 > Project: Atlas > Issue Type: Bug >Reporter: Darshan Kumar >Assignee: Sanjay Patel > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-228) UI: JSON response for the successful tag addition can be hidden from the end user
[ https://issues.apache.org/jira/browse/ATLAS-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar reassigned ATLAS-228: --- Assignee: Darshan Kumar (was: Anilsg) > UI: JSON response for the successful tag addition can be hidden from the end > user > - > > Key: ATLAS-228 > URL: https://issues.apache.org/jira/browse/ATLAS-228 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Ayub Khan >Assignee: Darshan Kumar > Labels: ATLAS-UI-BUGS > Attachments: Adding_tag_response.png > > > Currently, upon successful completion of tag addition, Atlas displays JSOn > response in the UI. From an end user's perspective, JSON response is not > required and can be hidden. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-229) UI: Lengthy trait names can be handled properly
[ https://issues.apache.org/jira/browse/ATLAS-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg reassigned ATLAS-229: Assignee: Anilsg > UI: Lengthy trait names can be handled properly > --- > > Key: ATLAS-229 > URL: https://issues.apache.org/jira/browse/ATLAS-229 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Ayub Khan >Assignee: Anilsg >Priority: Minor > Labels: ATLAS-UI-BUGS > Attachments: Lengthy traitnames.png > > > When a tag with length more than 36 characters is added, it spans over the > entire page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-229) UI: Lengthy trait names can be handled properly
[ https://issues.apache.org/jira/browse/ATLAS-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg resolved ATLAS-229. -- Resolution: Fixed > UI: Lengthy trait names can be handled properly > --- > > Key: ATLAS-229 > URL: https://issues.apache.org/jira/browse/ATLAS-229 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Ayub Khan >Priority: Minor > Labels: ATLAS-UI-BUGS > Attachments: Lengthy traitnames.png > > > When a tag with length more than 36 characters is added, it spans over the > entire page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-262) UI: Entities displayed after attaching long tags can be handled properly
[ https://issues.apache.org/jira/browse/ATLAS-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilsg resolved ATLAS-262. -- Resolution: Fixed Corrected > UI: Entities displayed after attaching long tags can be handled properly > > > Key: ATLAS-262 > URL: https://issues.apache.org/jira/browse/ATLAS-262 > Project: Atlas > Issue Type: Bug >Reporter: Ayub Khan >Assignee: Anilsg > Attachments: Apache-Atlas-Entities-with-long-tags.png > > > UI: Entities displayed after attaching long tags cab be handled properly > Attaching the snsphot for reference. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-229) UI: Lengthy trait names can be handled properly
[ https://issues.apache.org/jira/browse/ATLAS-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14981041#comment-14981041 ] Anilsg commented on ATLAS-229: -- Patch send along with ATLAS-211 > UI: Lengthy trait names can be handled properly > --- > > Key: ATLAS-229 > URL: https://issues.apache.org/jira/browse/ATLAS-229 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Ayub Khan >Assignee: Anilsg >Priority: Minor > Labels: ATLAS-UI-BUGS > Attachments: Lengthy traitnames.png > > > When a tag with length more than 36 characters is added, it spans over the > entire page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-211) UI: UI Facelift
[ https://issues.apache.org/jira/browse/ATLAS-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar updated ATLAS-211: Attachment: ATLAS-211_ATLAS-262_ATLAS-268_v2.patch > UI: UI Facelift > --- > > Key: ATLAS-211 > URL: https://issues.apache.org/jira/browse/ATLAS-211 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Anilsg > Labels: patch-available > Fix For: 0.6-incubating > > Attachments: ATLAS-211-ATLAS-224_v0.patch, > ATLAS-211-ATLAS-224_v1.patch, ATLAS-211_ATLAS-262_ATLAS-268_v2.patch, > Apache-Atlas-Same-Request-Twice.png, > Apache-Atlas-Tag-Creation-Dumps-Json.png, Apache-Atlas-long-trait-name.png, > Screen Shot 2015-10-26 at 11.29.19 PM.png, Screen Shot 2015-10-26 at 11.34.57 > PM.png, Screen Shot 2015-10-28 at 9.35.53 AM.png, Screen Shot 2015-10-29 at > 9.56.34 AM.png > > > Adopt new look and feel for all screens as shown here: > http://mprhost.com/hw/atlas/rahul/atlashtml/search.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-211) UI: UI Facelift
[ https://issues.apache.org/jira/browse/ATLAS-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14981072#comment-14981072 ] Darshan Kumar edited comment on ATLAS-211 at 10/29/15 7:07 PM: --- New patch attached along with 9,10 comments resolved. ATLAS-262,ATLAS-228 issue resolved in the same patch. -- ATLAS211_ATLAS262_ATLAS-268_v2.patch. Please apply. Thanks [~suma.shivaprasad] [~ayubkhan] was (Author: darshankumar89): New patch attached along with 9,10 comments resolved. ATLAS-262,ATLAS-228 issue resolved in the same patch. -- ATLAS-211_ATLAS-262_ATLAS-268_v2.patch. Please apply. Thanks [~suma.shivaprasad] [~ayubkhan] > UI: UI Facelift > --- > > Key: ATLAS-211 > URL: https://issues.apache.org/jira/browse/ATLAS-211 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Anilsg > Labels: patch-available > Fix For: 0.6-incubating > > Attachments: ATLAS-211-ATLAS-224_v0.patch, > ATLAS-211-ATLAS-224_v1.patch, ATLAS-211_ATLAS-262_ATLAS-268_v2.patch, > Apache-Atlas-Same-Request-Twice.png, > Apache-Atlas-Tag-Creation-Dumps-Json.png, Apache-Atlas-long-trait-name.png, > Screen Shot 2015-10-26 at 11.29.19 PM.png, Screen Shot 2015-10-26 at 11.34.57 > PM.png, Screen Shot 2015-10-28 at 9.35.53 AM.png, Screen Shot 2015-10-29 at > 9.56.34 AM.png > > > Adopt new look and feel for all screens as shown here: > http://mprhost.com/hw/atlas/rahul/atlashtml/search.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-211) UI: UI Facelift
[ https://issues.apache.org/jira/browse/ATLAS-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14981072#comment-14981072 ] Darshan Kumar commented on ATLAS-211: - New patch attached along with 9,10 comments resolved. ATLAS-262,ATLAS-228 issue resolved in the same patch. -- ATLAS-211_ATLAS-262_ATLAS-268_v2.patch. Please apply. Thanks [~suma.shivaprasad] [~ayubkhan] > UI: UI Facelift > --- > > Key: ATLAS-211 > URL: https://issues.apache.org/jira/browse/ATLAS-211 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Anilsg > Labels: patch-available > Fix For: 0.6-incubating > > Attachments: ATLAS-211-ATLAS-224_v0.patch, > ATLAS-211-ATLAS-224_v1.patch, ATLAS-211_ATLAS-262_ATLAS-268_v2.patch, > Apache-Atlas-Same-Request-Twice.png, > Apache-Atlas-Tag-Creation-Dumps-Json.png, Apache-Atlas-long-trait-name.png, > Screen Shot 2015-10-26 at 11.29.19 PM.png, Screen Shot 2015-10-26 at 11.34.57 > PM.png, Screen Shot 2015-10-28 at 9.35.53 AM.png, Screen Shot 2015-10-29 at > 9.56.34 AM.png > > > Adopt new look and feel for all screens as shown here: > http://mprhost.com/hw/atlas/rahul/atlashtml/search.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-228) UI: JSON response for the successful tag addition can be hidden from the end user
[ https://issues.apache.org/jira/browse/ATLAS-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar resolved ATLAS-228. - Resolution: Fixed > UI: JSON response for the successful tag addition can be hidden from the end > user > - > > Key: ATLAS-228 > URL: https://issues.apache.org/jira/browse/ATLAS-228 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Ayub Khan >Assignee: Darshan Kumar > Labels: ATLAS-UI-BUGS > Attachments: Adding_tag_response.png > > > Currently, upon successful completion of tag addition, Atlas displays JSOn > response in the UI. From an end user's perspective, JSON response is not > required and can be hidden. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-228) UI: JSON response for the successful tag addition can be hidden from the end user
[ https://issues.apache.org/jira/browse/ATLAS-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14981085#comment-14981085 ] Darshan Kumar commented on ATLAS-228: - Corrected and resolved in patch, available in ATLAS-211 > UI: JSON response for the successful tag addition can be hidden from the end > user > - > > Key: ATLAS-228 > URL: https://issues.apache.org/jira/browse/ATLAS-228 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Ayub Khan >Assignee: Darshan Kumar > Labels: ATLAS-UI-BUGS > Attachments: Adding_tag_response.png > > > Currently, upon successful completion of tag addition, Atlas displays JSOn > response in the UI. From an end user's perspective, JSON response is not > required and can be hidden. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-238) atlas_start.py- the Atlas server won’t restart after improper shutdown
[ https://issues.apache.org/jira/browse/ATLAS-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naima Djouhri updated ATLAS-238: Summary: atlas_start.py- the Atlas server won’t restart after improper shutdown (was: atlas_start.py- the Atlas server won’t restart after umproper shutdown) > atlas_start.py- the Atlas server won’t restart after improper shutdown > -- > > Key: ATLAS-238 > URL: https://issues.apache.org/jira/browse/ATLAS-238 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Naima Djouhri >Assignee: Naima Djouhri >Priority: Minor > > Steps to reproduce > 1.Open a Windows/terminal/shell and start the Atlas server with > “atlas_start.py” script > 2.Log in to your Atlas server http://localhost:21000/ to make sure that > you can connect > 3. Close the Windows/terminal/shell where the Atlas server process > started –step1 > Or just kill the process - the process id can be found in a file called > “atlas.pid” in the logs directory (this file is created by the > “atlas_start.py” script > 4.Try to login to your Atlas server again and a “Unable to connect” > message will pop up > 5.From a command prompt Windows/ Terminal/Shell start the server > (atlas_start.py) > 6.A message “atlas.pid already exists, exiting” will pop up in the screen > and the server will not start > Expected Result > The server should start since it has been shut down >Actual: > The server can not start > If the server is stopped using “atlas_stop.py” , the server restart after > running "atlas_start.py" with no issue. > Since the server has not been stopped with “atlas_stop.py” that kill the > process, and delete the “atlas.pid” file, the script “atlas_start.py” will > not start the server. > The turnaround is to delete the “atlas.pid” file in the logs directory but it > is not always obvious, and user friendly!! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-261) If we have "/" in the search query(example: "abc/", UI fires the same request twice. verified the same using network trace as well.
[ https://issues.apache.org/jira/browse/ATLAS-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Patel updated ATLAS-261: --- Attachment: ATLAS-261_v1.patch > If we have "/" in the search query(example: "abc/", UI fires the same request > twice. verified the same using network trace as well. > --- > > Key: ATLAS-261 > URL: https://issues.apache.org/jira/browse/ATLAS-261 > Project: Atlas > Issue Type: Bug >Reporter: Darshan Kumar >Assignee: Sanjay Patel > Attachments: ATLAS-261_v1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-238) atlas_start.py- the Atlas server won’t restart after improper shutdown
[ https://issues.apache.org/jira/browse/ATLAS-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naima Djouhri updated ATLAS-238: Attachment: ATLAS-238_V0.patch > atlas_start.py- the Atlas server won’t restart after improper shutdown > -- > > Key: ATLAS-238 > URL: https://issues.apache.org/jira/browse/ATLAS-238 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Naima Djouhri >Assignee: Naima Djouhri >Priority: Minor > Labels: patch-available > Fix For: 0.6-incubating > > Attachments: ATLAS-238_V0.patch > > > Steps to reproduce > 1.Open a Windows/terminal/shell and start the Atlas server with > “atlas_start.py” script > 2.Log in to your Atlas server http://localhost:21000/ to make sure that > you can connect > 3. Close the Windows/terminal/shell where the Atlas server process > started –step1 > Or just kill the process - the process id can be found in a file called > “atlas.pid” in the logs directory (this file is created by the > “atlas_start.py” script > 4.Try to login to your Atlas server again and a “Unable to connect” > message will pop up > 5.From a command prompt Windows/ Terminal/Shell start the server > (atlas_start.py) > 6.A message “atlas.pid already exists, exiting” will pop up in the screen > and the server will not start > Expected Result > The server should start since it has been shut down >Actual: > The server can not start > If the server is stopped using “atlas_stop.py” , the server restart after > running "atlas_start.py" with no issue. > Since the server has not been stopped with “atlas_stop.py” that kill the > process, and delete the “atlas.pid” file, the script “atlas_start.py” will > not start the server. > The turnaround is to delete the “atlas.pid” file in the logs directory but it > is not always obvious, and user friendly!! -- This message was sent by Atlassian JIRA (v6.3.4#6332)