[jira] [Created] (ATLAS-282) Atlas UI: Entity Details UI is broken after the changes in ATLAS-58
Chethana created ATLAS-282: -- Summary: Atlas UI: Entity Details UI is broken after the changes in ATLAS-58 Key: ATLAS-282 URL: https://issues.apache.org/jira/browse/ATLAS-282 Project: Atlas Issue Type: Bug Affects Versions: 0.6-incubating Environment: Sandbox Reporter: Chethana Priority: Critical Fix For: 0.6-incubating Entity details and the lineage map are not showing up after the changes introduced for ATLAS-58 commit. The api call - http://localhost:21000/api/atlas/entity/{GUID} now returns a 404 UI needs to update the call to http://localhost:21000/api/atlas/entities/{GUID} so details come back. Attaching screen shot . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-282) Atlas UI: Entity Details UI is broken after the changes in ATLAS-58
[ https://issues.apache.org/jira/browse/ATLAS-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayub Khan updated ATLAS-282: Assignee: Anilsg > Atlas UI: Entity Details UI is broken after the changes in ATLAS-58 > --- > > Key: ATLAS-282 > URL: https://issues.apache.org/jira/browse/ATLAS-282 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating > Environment: Sandbox >Reporter: Chethana >Assignee: Anilsg >Priority: Critical > Fix For: 0.6-incubating > > > Entity details and the lineage map are not showing up after the changes > introduced for ATLAS-58 commit. > The api call - http://localhost:21000/api/atlas/entity/{GUID} now returns a > 404 > UI needs to update the call to > http://localhost:21000/api/atlas/entities/{GUID} so details come back. > Attaching screen shot . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-282) Atlas UI: Entity Details UI is broken after the changes in ATLAS-58
[ https://issues.apache.org/jira/browse/ATLAS-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chethana updated ATLAS-282: --- Attachment: Screen Shot 2015-11-05 at 1.56.45 PM.png > Atlas UI: Entity Details UI is broken after the changes in ATLAS-58 > --- > > Key: ATLAS-282 > URL: https://issues.apache.org/jira/browse/ATLAS-282 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating > Environment: Sandbox >Reporter: Chethana >Assignee: Anilsg >Priority: Critical > Fix For: 0.6-incubating > > Attachments: Screen Shot 2015-11-05 at 1.56.45 PM.png > > > Entity details and the lineage map are not showing up after the changes > introduced for ATLAS-58 commit. > The api call - http://localhost:21000/api/atlas/entity/{GUID} now returns a > 404 > UI needs to update the call to > http://localhost:21000/api/atlas/entities/{GUID} so details come back. > Attaching screen shot . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (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 ] Suma Shivaprasad reopened ATLAS-214: This is not fixed . Hence reopening > 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 >Assignee: Darshan Kumar >Priority: Blocker > 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] [Commented] (ATLAS-211) UI: UI Facelift
[ https://issues.apache.org/jira/browse/ATLAS-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14991410#comment-14991410 ] Suma Shivaprasad commented on ATLAS-211: +1 > 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-219-ATLAS-214-Atlas-261_v10.patch, > ATLAS-211-ATLAS-219-ATLAS-214_v9.patch, ATLAS-211-ATLAS-224_v0.patch, > ATLAS-211-ATLAS-224_v1.patch, ATLAS-211-ATLAS-224_v4.patch, > ATLAS-211-ATLAS-255-ATLAS-264_v6.patch, > ATLAS-211-ATLAS-255-ATLAS-264_v7.patch, > ATLAS-211-ATLAS-255-ATLAS-264_v8.patch, ATLAS-211-Comments-Fixed-V5.patch, > ATLAS-211_ATLAS-262_ATLAS-268_v2.patch, Apache-ATlas-lenghtly-trait.png, > Apache-Atlas-Avoid-Extra-Get-For-Trait-Creation.png, > Apache-Atlas-Same-Request-Twice.png, > Apache-Atlas-Tag-Creation-Dumps-Json.png, Apache-Atlas-long-trait-name.png, > Atlas-Tag-Drop-Down-Listing-only-First-30-entries.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, > Search.png, tags.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=14991416#comment-14991416 ] Suma Shivaprasad commented on ATLAS-211: [~Anilg] [~darshankumar1989] Can you pls confirm the final patch version? > 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-219-ATLAS-214-Atlas-261_v10.patch, > ATLAS-211-ATLAS-219-ATLAS-214_v9.patch, ATLAS-211-ATLAS-224_v0.patch, > ATLAS-211-ATLAS-224_v1.patch, ATLAS-211-ATLAS-224_v4.patch, > ATLAS-211-ATLAS-255-ATLAS-264_v6.patch, > ATLAS-211-ATLAS-255-ATLAS-264_v7.patch, > ATLAS-211-ATLAS-255-ATLAS-264_v8.patch, ATLAS-211-Comments-Fixed-V5.patch, > ATLAS-211_ATLAS-262_ATLAS-268_v2.patch, Apache-ATlas-lenghtly-trait.png, > Apache-Atlas-Avoid-Extra-Get-For-Trait-Creation.png, > Apache-Atlas-Same-Request-Twice.png, > Apache-Atlas-Tag-Creation-Dumps-Json.png, Apache-Atlas-long-trait-name.png, > Atlas-Tag-Drop-Down-Listing-only-First-30-entries.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, > Search.png, tags.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)
Re: Build Failing
Hi again, The build was working properly for me but suddenly it starts throwing this error now, [ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:0.0.23:install-node-and-npm (install node and npm) on project atlas-dashboard: Could not extract the Node archive: Could not extract archive: '/Users/admin/Documents/office/atlas/myRepo/incubator-atlas/dashboard/target/node_tmp/node.tar.gz': EOFException -> [Help 1] Can someone help? I have tried building many times but every time getting the same error ? On Tue, Nov 3, 2015 at 9:10 AM, Rishabh Bhardwaj wrote: > Thanks Shwetha.It works. > I was doing > 1. 'mvn -DskipTests=true clean install' (Failing) > But, > 1. 'mvn clean' > 2. 'mvn -DskipTests=true Install' > This works. > > I guess this is some intermittent error. > > On Mon, Nov 2, 2015 at 7:40 PM, Shwetha Shivalingamurthy < > sshivalingamur...@hortonworks.com> wrote: > >> Doesn't 'mvn clean' help? >> >> Regards, >> Shwetha >> >> >> >> >> >> >> On 02/11/15 6:01 pm, "Rishabh Bhardwaj" wrote: >> >> >Hi, >> >My build fails with this error, >> >[ERROR] Failed to execute goal >> >com.github.eirslett:frontend-maven-plugin:0.0.23:install-node-and-npm >> >(install node and npm) on project atlas-dashboard: Could not extract the >> >Node archive: Could not extract archive: >> >> >'/Users/admin/Documents/office/atlas/myRepo/incubator-atlas/dashboard/targ >> >et/node_tmp/node.tar.gz': >> >EOFException -> [Help 1] >> > >> >Can anyone suggest workaroud for this ? >> > >> >Thanks, >> >Rishabh. >> >> >
Re: Build Failing
Doesn¹t Œmvn clean¹ on the whole project help this time as well? Else, you can try fresh checkout Regards, Shwetha On 05/11/15 3:28 pm, "Rishabh Bhardwaj" wrote: >Hi again, > >The build was working properly for me but suddenly it starts throwing this >error now, > >[ERROR] Failed to execute goal >com.github.eirslett:frontend-maven-plugin:0.0.23:install-node-and-npm >(install node and npm) on project atlas-dashboard: Could not extract the >Node archive: Could not extract archive: >'/Users/admin/Documents/office/atlas/myRepo/incubator-atlas/dashboard/targ >et/node_tmp/node.tar.gz': >EOFException -> [Help 1] > >Can someone help? I have tried building many times but every time getting >the same error ? > >On Tue, Nov 3, 2015 at 9:10 AM, Rishabh Bhardwaj >wrote: > >> Thanks Shwetha.It works. >> I was doing >> 1. 'mvn -DskipTests=true clean install' (Failing) >> But, >> 1. 'mvn clean' >> 2. 'mvn -DskipTests=true Install' >> This works. >> >> I guess this is some intermittent error. >> >> On Mon, Nov 2, 2015 at 7:40 PM, Shwetha Shivalingamurthy < >> sshivalingamur...@hortonworks.com> wrote: >> >>> Doesn't 'mvn clean' help? >>> >>> Regards, >>> Shwetha >>> >>> >>> >>> >>> >>> >>> On 02/11/15 6:01 pm, "Rishabh Bhardwaj" wrote: >>> >>> >Hi, >>> >My build fails with this error, >>> >[ERROR] Failed to execute goal >>> >com.github.eirslett:frontend-maven-plugin:0.0.23:install-node-and-npm >>> >(install node and npm) on project atlas-dashboard: Could not extract >>>the >>> >Node archive: Could not extract archive: >>> >>> '/Users/admin/Documents/office/atlas/myRepo/incubator-atlas/dashboard/t arg >>> >et/node_tmp/node.tar.gz': >>> >EOFException -> [Help 1] >>> > >>> >Can anyone suggest workaroud for this ? >>> > >>> >Thanks, >>> >Rishabh. >>> >>> >>
[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=14991483#comment-14991483 ] Darshan Kumar commented on ATLAS-211: - Please Find the Patch V10 : ATLAS-211-ATLAS-219-ATLAS-214-Atlas-261_v10.patch Thanks > 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-219-ATLAS-214-Atlas-261_v10.patch, > ATLAS-211-ATLAS-219-ATLAS-214_v9.patch, ATLAS-211-ATLAS-224_v0.patch, > ATLAS-211-ATLAS-224_v1.patch, ATLAS-211-ATLAS-224_v4.patch, > ATLAS-211-ATLAS-255-ATLAS-264_v6.patch, > ATLAS-211-ATLAS-255-ATLAS-264_v7.patch, > ATLAS-211-ATLAS-255-ATLAS-264_v8.patch, ATLAS-211-Comments-Fixed-V5.patch, > ATLAS-211_ATLAS-262_ATLAS-268_v2.patch, Apache-ATlas-lenghtly-trait.png, > Apache-Atlas-Avoid-Extra-Get-For-Trait-Creation.png, > Apache-Atlas-Same-Request-Twice.png, > Apache-Atlas-Tag-Creation-Dumps-Json.png, Apache-Atlas-long-trait-name.png, > Atlas-Tag-Drop-Down-Listing-only-First-30-entries.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, > Search.png, tags.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)
Re: Build Failing
mvn clean does not help. Will try fresh checkout. Thanks for the response. On Thu, Nov 5, 2015 at 3:52 PM, Shwetha Shivalingamurthy < sshivalingamur...@hortonworks.com> wrote: > Doesn¹t Œmvn clean¹ on the whole project help this time as well? Else, you > can try fresh checkout > > Regards, > Shwetha > > > > > > > On 05/11/15 3:28 pm, "Rishabh Bhardwaj" wrote: > > >Hi again, > > > >The build was working properly for me but suddenly it starts throwing this > >error now, > > > >[ERROR] Failed to execute goal > >com.github.eirslett:frontend-maven-plugin:0.0.23:install-node-and-npm > >(install node and npm) on project atlas-dashboard: Could not extract the > >Node archive: Could not extract archive: > >'/Users/admin/Documents/office/atlas/myRepo/incubator-atlas/dashboard/targ > >et/node_tmp/node.tar.gz': > >EOFException -> [Help 1] > > > >Can someone help? I have tried building many times but every time getting > >the same error ? > > > >On Tue, Nov 3, 2015 at 9:10 AM, Rishabh Bhardwaj > >wrote: > > > >> Thanks Shwetha.It works. > >> I was doing > >> 1. 'mvn -DskipTests=true clean install' (Failing) > >> But, > >> 1. 'mvn clean' > >> 2. 'mvn -DskipTests=true Install' > >> This works. > >> > >> I guess this is some intermittent error. > >> > >> On Mon, Nov 2, 2015 at 7:40 PM, Shwetha Shivalingamurthy < > >> sshivalingamur...@hortonworks.com> wrote: > >> > >>> Doesn't 'mvn clean' help? > >>> > >>> Regards, > >>> Shwetha > >>> > >>> > >>> > >>> > >>> > >>> > >>> On 02/11/15 6:01 pm, "Rishabh Bhardwaj" wrote: > >>> > >>> >Hi, > >>> >My build fails with this error, > >>> >[ERROR] Failed to execute goal > >>> >com.github.eirslett:frontend-maven-plugin:0.0.23:install-node-and-npm > >>> >(install node and npm) on project atlas-dashboard: Could not extract > >>>the > >>> >Node archive: Could not extract archive: > >>> > >>> > '/Users/admin/Documents/office/atlas/myRepo/incubator-atlas/dashboard/t > arg > >>> >et/node_tmp/node.tar.gz': > >>> >EOFException -> [Help 1] > >>> > > >>> >Can anyone suggest workaroud for this ? > >>> > > >>> >Thanks, > >>> >Rishabh. > >>> > >>> > >> > >
[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.v2.patch I have made the changes as suggested by [~suma.shivaprasad]. Kindly Review the changes. Also,the getEntity method was breaking because the API call which should be made to /entity was going to /entites. I have made that change also with this patch. If it is required to create a separate JIRA for that issue,we can do that. Kindly review that change also. I have tested all the new trait methods added to AtlasClient and they were working fine for me. Thanks. > 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-136.v2.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)
Regarding Ranger Integration
Hi all, We have seen in README.txt that Atlas have a Ranger Integration. Is there any example code or something related in the codebase? Can someone give some pointer on this? TIA. Regards, Rishabh.
[jira] [Assigned] (ATLAS-106) Store createTimestamp and modified timestamp separately for an entity
[ https://issues.apache.org/jira/browse/ATLAS-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Kantor reassigned ATLAS-106: -- Assignee: David Kantor > Store createTimestamp and modified timestamp separately for an entity > - > > Key: ATLAS-106 > URL: https://issues.apache.org/jira/browse/ATLAS-106 > Project: Atlas > Issue Type: Improvement >Reporter: Suma Shivaprasad >Assignee: David Kantor > > Currently we store only the Create timestamp in atlas. Would be better to > separate to track create and modified time separately , in cases where we > want to support search queries give all entities which have been modified in > the past 1 day etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-158) Provide Atlas Entity Change Notification
[ https://issues.apache.org/jira/browse/ATLAS-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14991724#comment-14991724 ] Tom Beerbower commented on ATLAS-158: - [~shwethags], Okay thanks. So if I understand, you must do a clean between runs and you can not run an individual integration test. If I run 'mvn clean package' from the top level followed by 'mvn install' from webapp, it will run all of the tests and show the single failure in NotificationHookConsumerIT. If I skip the clean build then I see other failures. I guess that is expected since the data directory is not cleaned up. If I try to run just the NotificationHookConsumerIT test (-Dtest=NotificationHookConsumerIT) then it runs the test but Atlas is not started so it fails. I'll look into the failure. Thanks again! > Provide Atlas Entity Change Notification > > > Key: ATLAS-158 > URL: https://issues.apache.org/jira/browse/ATLAS-158 > Project: Atlas > Issue Type: Task >Reporter: Tom Beerbower >Assignee: Tom Beerbower > Fix For: 0.6-incubating > > Attachments: ATLAS-158.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-283) UI :After clicking Add tag - Error: [$parse:syntax] Syntax Error Token 'b' is an unexpected
Darshan Kumar created ATLAS-283: --- Summary: UI :After clicking Add tag - Error: [$parse:syntax] Syntax Error Token 'b' is an unexpected Key: ATLAS-283 URL: https://issues.apache.org/jira/browse/ATLAS-283 Project: Atlas Issue Type: Bug Reporter: Darshan Kumar Assignee: Darshan Kumar Error: [$parse:syntax] Syntax Error: Token 'b' is an unexpected token at column 3 of the expression [a b c] starting at [b c]. http://errors.angularjs.org/1.2.29/$parse/syntax?p0=b&p1=is%20an%20unexpected%20token&p2=3&p3=a%20b&p4=b%c at http://162.212.133.190:3173/lib/angular/angular.js:78:12 at Parser.throwError (http://162.212.133.190:3173/lib/angular/angular.js:10641:11) at Parser.parse (http://162.212.133.190:3173/lib/angular/angular.js:10594:12) at http://162.212.133.190:3173/lib/angular/angular.js:11447:37 at compileToFn (http://162.212.133.190:3173/lib/angular/angular.js:13173:16) at Scope.$watch (http://162.212.133.190:3173/lib/angular/angular.js:12370:19) at ngValueLink (http://162.212.133.190:3173/lib/angular/angular.js:18301:17) at nodeLinkFn (http://162.212.133.190:3173/lib/angular/angular.js:6768:13) at compositeLinkFn (http://162.212.133.190:3173/lib/angular/angular.js:6155:13) at publicLinkFn (http://162.212.133.190:3173/lib/angular/angular.js:6051:30) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-282) Atlas UI: Entity Details UI is broken after the changes in ATLAS-58
[ https://issues.apache.org/jira/browse/ATLAS-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayub Khan reassigned ATLAS-282: --- Assignee: Ayub Khan (was: Anilsg) > Atlas UI: Entity Details UI is broken after the changes in ATLAS-58 > --- > > Key: ATLAS-282 > URL: https://issues.apache.org/jira/browse/ATLAS-282 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating > Environment: Sandbox >Reporter: Chethana >Assignee: Ayub Khan >Priority: Critical > Fix For: 0.6-incubating > > Attachments: Screen Shot 2015-11-05 at 1.56.45 PM.png > > > Entity details and the lineage map are not showing up after the changes > introduced for ATLAS-58 commit. > The api call - http://localhost:21000/api/atlas/entity/{GUID} now returns a > 404 > UI needs to update the call to > http://localhost:21000/api/atlas/entities/{GUID} so details come back. > Attaching screen shot . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-282) Atlas UI: Entity Details UI is broken after the changes in ATLAS-58
[ https://issues.apache.org/jira/browse/ATLAS-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayub Khan updated ATLAS-282: Attachment: ATLAS-282-v0.patch > Atlas UI: Entity Details UI is broken after the changes in ATLAS-58 > --- > > Key: ATLAS-282 > URL: https://issues.apache.org/jira/browse/ATLAS-282 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating > Environment: Sandbox >Reporter: Chethana >Assignee: Ayub Khan >Priority: Critical > Fix For: 0.6-incubating > > Attachments: ATLAS-282-v0.patch, Screen Shot 2015-11-05 at 1.56.45 > PM.png > > > Entity details and the lineage map are not showing up after the changes > introduced for ATLAS-58 commit. > The api call - http://localhost:21000/api/atlas/entity/{GUID} now returns a > 404 > UI needs to update the call to > http://localhost:21000/api/atlas/entities/{GUID} so details come back. > Attaching screen shot . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-283) UI :After clicking Add tag - Error: [$parse:syntax] Syntax Error Token 'b' is an unexpected
[ https://issues.apache.org/jira/browse/ATLAS-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar updated ATLAS-283: Attachment: ATLAS-283_v0.patch Please apply the patch after ATLAS-211 is applied > UI :After clicking Add tag - Error: [$parse:syntax] Syntax Error Token 'b' > is an unexpected > > > Key: ATLAS-283 > URL: https://issues.apache.org/jira/browse/ATLAS-283 > Project: Atlas > Issue Type: Bug >Reporter: Darshan Kumar >Assignee: Darshan Kumar > Attachments: ATLAS-283_v0.patch > > > Error: [$parse:syntax] Syntax Error: Token 'b' is an unexpected token at > column 3 of the expression [a b c] starting at [b c]. > http://errors.angularjs.org/1.2.29/$parse/syntax?p0=b&p1=is%20an%20unexpected%20token&p2=3&p3=a%20b&p4=b%c > at http://162.212.133.190:3173/lib/angular/angular.js:78:12 > at Parser.throwError > (http://162.212.133.190:3173/lib/angular/angular.js:10641:11) > at Parser.parse (http://162.212.133.190:3173/lib/angular/angular.js:10594:12) > at http://162.212.133.190:3173/lib/angular/angular.js:11447:37 > at compileToFn (http://162.212.133.190:3173/lib/angular/angular.js:13173:16) > at Scope.$watch (http://162.212.133.190:3173/lib/angular/angular.js:12370:19) > at ngValueLink (http://162.212.133.190:3173/lib/angular/angular.js:18301:17) > at nodeLinkFn (http://162.212.133.190:3173/lib/angular/angular.js:6768:13) > at compositeLinkFn > (http://162.212.133.190:3173/lib/angular/angular.js:6155:13) > at publicLinkFn (http://162.212.133.190:3173/lib/angular/angular.js:6051:30) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-283) UI :After clicking Add tag - Parsing Error
[ https://issues.apache.org/jira/browse/ATLAS-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar updated ATLAS-283: Summary: UI :After clicking Add tag - Parsing Error (was: UI :After clicking Add tag - Error: [$parse:syntax] Syntax Error Token 'b' is an unexpected) > UI :After clicking Add tag - Parsing Error > -- > > Key: ATLAS-283 > URL: https://issues.apache.org/jira/browse/ATLAS-283 > Project: Atlas > Issue Type: Bug >Reporter: Darshan Kumar >Assignee: Darshan Kumar > Labels: patch-available > Attachments: ATLAS-283_v0.patch > > > Error: [$parse:syntax] Syntax Error: Token 'b' is an unexpected token at > column 3 of the expression [a b c] starting at [b c]. > http://errors.angularjs.org/1.2.29/$parse/syntax?p0=b&p1=is%20an%20unexpected%20token&p2=3&p3=a%20b&p4=b%c > at http://162.212.133.190:3173/lib/angular/angular.js:78:12 > at Parser.throwError > (http://162.212.133.190:3173/lib/angular/angular.js:10641:11) > at Parser.parse (http://162.212.133.190:3173/lib/angular/angular.js:10594:12) > at http://162.212.133.190:3173/lib/angular/angular.js:11447:37 > at compileToFn (http://162.212.133.190:3173/lib/angular/angular.js:13173:16) > at Scope.$watch (http://162.212.133.190:3173/lib/angular/angular.js:12370:19) > at ngValueLink (http://162.212.133.190:3173/lib/angular/angular.js:18301:17) > at nodeLinkFn (http://162.212.133.190:3173/lib/angular/angular.js:6768:13) > at compositeLinkFn > (http://162.212.133.190:3173/lib/angular/angular.js:6155:13) > at publicLinkFn (http://162.212.133.190:3173/lib/angular/angular.js:6051:30) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-284) UI not displaying the lineage for complex hive table (CTAS)
Ayub Khan created ATLAS-284: --- Summary: UI not displaying the lineage for complex hive table (CTAS) Key: ATLAS-284 URL: https://issues.apache.org/jira/browse/ATLAS-284 Project: Atlas Issue Type: Bug Affects Versions: 0.6-incubating Reporter: Ayub Khan Assignee: Erik Bergenholtz UI not displaying the lineage for complex hive table (CTAS). 1. On hive cli, create a hive table using CTAS just like below.. Use this query: create table table_1251 as select employee.salary as salary, t2.temp as integer, t1.temp as number, nested.propertyid as string, nested.propertyName as propname, table_1243.number as num, table_1250.number as prism, temp_batting.col_value as temp1 from employee, t2, t1, nested, table_1243, table_1250, temp_batting; 2. Now try to view the graph on ATLAS UI for the above table. - No Graph is displayed where as the backend API request is successful. {noformat} curl 'http://localhost:21000/api/atlas/lineage/hive/table/primary.default.table_1261/inputs/graph' -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive' -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer: http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed | python -m json.tool % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 38250 38250 0 3813 0 --:--:-- 0:00:01 --:--:-- 3813 { "requestId": "qtp1610708593-415 - fb672eb4-2ce2-4485-8350-ba1f919ece02", "results": { "jsonClass": "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", "typeName": "__tempQueryResultStruct65", "values": { "edges": { "5a3ecb0e-adc9-40c9-8296-9132d7ad1838": [ "ebde1571-2ced-46d6-b65c-558835224764" ], "ebde1571-2ced-46d6-b65c-558835224764": [ "364d6dc1-fdcc-4d03-8df7-cf1d835730af", "6b52aa8f-134d-4ab7-9389-4568fac87533", "7c1af593-b7b1-4838-815b-872b8a163a40", "ce01cbb6-ffd5-42c8-8c15-3f72bcef45c1", "b040d1e4-dd96-4729-8f55-4da4c958ff8f", "f82337ea-1e0c-4c28-a491-4916be594b49", "0f8b8f57-5aa4-4c30-be0a-c89eeedc2012" ] }, "vertices": { "0f8b8f57-5aa4-4c30-be0a-c89eeedc2012": { "jsonClass": "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", "typeName": "__tempQueryResultStruct64", "values": { "name": "primary.default.employee", "vertexId": { "jsonClass": "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", "typeName": "__IdType", "values": { "guid": "0f8b8f57-5aa4-4c30-be0a-c89eeedc2012", "typeName": "hive_table" } } } }, "364d6dc1-fdcc-4d03-8df7-cf1d835730af": { "jsonClass": "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", "typeName": "__tempQueryResultStruct64", "values": { "name": "primary.default.t1", "vertexId": { "jsonClass": "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", "typeName": "__IdType", "values": { "guid": "364d6dc1-fdcc-4d03-8df7-cf1d835730af", "typeName": "hive_table" } } } }, "5a3ecb0e-adc9-40c9-8296-9132d7ad1838": { "jsonClass": "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", "typeName": "__tempQueryResultStruct64", "values": { "name": "primary.default.table_1261", "vertexId": { "jsonClass": "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", "typeName": "__IdType", "values": { "guid": "5a3ecb0e-adc9-40c9-8296-9132d7ad1838", "typeName": "hive_table" } }
[jira] [Updated] (ATLAS-284) UI not displaying the lineage for complex hive table (CTAS)
[ https://issues.apache.org/jira/browse/ATLAS-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayub Khan updated ATLAS-284: Attachment: graph_not_shown_application.log Attachng application log for reference. > UI not displaying the lineage for complex hive table (CTAS) > --- > > Key: ATLAS-284 > URL: https://issues.apache.org/jira/browse/ATLAS-284 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Ayub Khan >Assignee: Erik Bergenholtz > Attachments: graph_not_shown_application.log > > > UI not displaying the lineage for complex hive table (CTAS). > 1. On hive cli, create a hive table using CTAS just like below.. > Use this query: > create table table_1251 as select employee.salary as salary, t2.temp as > integer, t1.temp as number, nested.propertyid as > string, nested.propertyName as propname, table_1243.number as num, > table_1250.number as prism, temp_batting.col_value as > temp1 from employee, t2, t1, nested, table_1243, table_1250, temp_batting; > 2. Now try to view the graph on ATLAS UI for the above table. - No Graph is > displayed where as the backend API request is successful. > {noformat} > curl > 'http://localhost:21000/api/atlas/lineage/hive/table/primary.default.table_1261/inputs/graph' > -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive' > -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer: > http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent: > Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, > like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed | python -m > json.tool > % Total% Received % Xferd Average Speed TimeTime Time > Current > Dload Upload Total SpentLeft Speed > 100 38250 38250 0 3813 0 --:--:-- 0:00:01 --:--:-- 3813 > { > "requestId": "qtp1610708593-415 - fb672eb4-2ce2-4485-8350-ba1f919ece02", > "results": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__tempQueryResultStruct65", > "values": { > "edges": { > "5a3ecb0e-adc9-40c9-8296-9132d7ad1838": [ > "ebde1571-2ced-46d6-b65c-558835224764" > ], > "ebde1571-2ced-46d6-b65c-558835224764": [ > "364d6dc1-fdcc-4d03-8df7-cf1d835730af", > "6b52aa8f-134d-4ab7-9389-4568fac87533", > "7c1af593-b7b1-4838-815b-872b8a163a40", > "ce01cbb6-ffd5-42c8-8c15-3f72bcef45c1", > "b040d1e4-dd96-4729-8f55-4da4c958ff8f", > "f82337ea-1e0c-4c28-a491-4916be594b49", > "0f8b8f57-5aa4-4c30-be0a-c89eeedc2012" > ] > }, > "vertices": { > "0f8b8f57-5aa4-4c30-be0a-c89eeedc2012": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__tempQueryResultStruct64", > "values": { > "name": "primary.default.employee", > "vertexId": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__IdType", > "values": { > "guid": > "0f8b8f57-5aa4-4c30-be0a-c89eeedc2012", > "typeName": "hive_table" > } > } > } > }, > "364d6dc1-fdcc-4d03-8df7-cf1d835730af": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__tempQueryResultStruct64", > "values": { > "name": "primary.default.t1", > "vertexId": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__IdType", > "values": { > "guid": > "364d6dc1-fdcc-4d03-8df7-cf1d835730af", > "typeName": "hive_table" > } > } > } > }, > "5a3ecb0e-adc9-40c9-8296-9132d7ad1838": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__tempQueryResultStruct64", > "values": { >
[jira] [Updated] (ATLAS-284) UI not displaying the lineage for complex hive table (CTAS)
[ https://issues.apache.org/jira/browse/ATLAS-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik Bergenholtz updated ATLAS-284: --- Fix Version/s: 0.6-incubating > UI not displaying the lineage for complex hive table (CTAS) > --- > > Key: ATLAS-284 > URL: https://issues.apache.org/jira/browse/ATLAS-284 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Ayub Khan >Assignee: Erik Bergenholtz > Fix For: 0.6-incubating > > Attachments: graph_not_shown_application.log > > > UI not displaying the lineage for complex hive table (CTAS). > 1. On hive cli, create a hive table using CTAS just like below.. > Use this query: > create table table_1251 as select employee.salary as salary, t2.temp as > integer, t1.temp as number, nested.propertyid as > string, nested.propertyName as propname, table_1243.number as num, > table_1250.number as prism, temp_batting.col_value as > temp1 from employee, t2, t1, nested, table_1243, table_1250, temp_batting; > 2. Now try to view the graph on ATLAS UI for the above table. - No Graph is > displayed where as the backend API request is successful. > {noformat} > curl > 'http://localhost:21000/api/atlas/lineage/hive/table/primary.default.table_1261/inputs/graph' > -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive' > -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer: > http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent: > Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, > like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed | python -m > json.tool > % Total% Received % Xferd Average Speed TimeTime Time > Current > Dload Upload Total SpentLeft Speed > 100 38250 38250 0 3813 0 --:--:-- 0:00:01 --:--:-- 3813 > { > "requestId": "qtp1610708593-415 - fb672eb4-2ce2-4485-8350-ba1f919ece02", > "results": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__tempQueryResultStruct65", > "values": { > "edges": { > "5a3ecb0e-adc9-40c9-8296-9132d7ad1838": [ > "ebde1571-2ced-46d6-b65c-558835224764" > ], > "ebde1571-2ced-46d6-b65c-558835224764": [ > "364d6dc1-fdcc-4d03-8df7-cf1d835730af", > "6b52aa8f-134d-4ab7-9389-4568fac87533", > "7c1af593-b7b1-4838-815b-872b8a163a40", > "ce01cbb6-ffd5-42c8-8c15-3f72bcef45c1", > "b040d1e4-dd96-4729-8f55-4da4c958ff8f", > "f82337ea-1e0c-4c28-a491-4916be594b49", > "0f8b8f57-5aa4-4c30-be0a-c89eeedc2012" > ] > }, > "vertices": { > "0f8b8f57-5aa4-4c30-be0a-c89eeedc2012": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__tempQueryResultStruct64", > "values": { > "name": "primary.default.employee", > "vertexId": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__IdType", > "values": { > "guid": > "0f8b8f57-5aa4-4c30-be0a-c89eeedc2012", > "typeName": "hive_table" > } > } > } > }, > "364d6dc1-fdcc-4d03-8df7-cf1d835730af": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__tempQueryResultStruct64", > "values": { > "name": "primary.default.t1", > "vertexId": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__IdType", > "values": { > "guid": > "364d6dc1-fdcc-4d03-8df7-cf1d835730af", > "typeName": "hive_table" > } > } > } > }, > "5a3ecb0e-adc9-40c9-8296-9132d7ad1838": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__tempQueryResultStruct64", > "values": { >
[jira] [Updated] (ATLAS-284) UI not displaying the lineage for complex hive table (CTAS)
[ https://issues.apache.org/jira/browse/ATLAS-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik Bergenholtz updated ATLAS-284: --- Assignee: Rohit (was: Erik Bergenholtz) > UI not displaying the lineage for complex hive table (CTAS) > --- > > Key: ATLAS-284 > URL: https://issues.apache.org/jira/browse/ATLAS-284 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Ayub Khan >Assignee: Rohit > Fix For: 0.6-incubating > > Attachments: graph_not_shown_application.log > > > UI not displaying the lineage for complex hive table (CTAS). > 1. On hive cli, create a hive table using CTAS just like below.. > Use this query: > create table table_1251 as select employee.salary as salary, t2.temp as > integer, t1.temp as number, nested.propertyid as > string, nested.propertyName as propname, table_1243.number as num, > table_1250.number as prism, temp_batting.col_value as > temp1 from employee, t2, t1, nested, table_1243, table_1250, temp_batting; > 2. Now try to view the graph on ATLAS UI for the above table. - No Graph is > displayed where as the backend API request is successful. > {noformat} > curl > 'http://localhost:21000/api/atlas/lineage/hive/table/primary.default.table_1261/inputs/graph' > -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive' > -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer: > http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent: > Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, > like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed | python -m > json.tool > % Total% Received % Xferd Average Speed TimeTime Time > Current > Dload Upload Total SpentLeft Speed > 100 38250 38250 0 3813 0 --:--:-- 0:00:01 --:--:-- 3813 > { > "requestId": "qtp1610708593-415 - fb672eb4-2ce2-4485-8350-ba1f919ece02", > "results": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__tempQueryResultStruct65", > "values": { > "edges": { > "5a3ecb0e-adc9-40c9-8296-9132d7ad1838": [ > "ebde1571-2ced-46d6-b65c-558835224764" > ], > "ebde1571-2ced-46d6-b65c-558835224764": [ > "364d6dc1-fdcc-4d03-8df7-cf1d835730af", > "6b52aa8f-134d-4ab7-9389-4568fac87533", > "7c1af593-b7b1-4838-815b-872b8a163a40", > "ce01cbb6-ffd5-42c8-8c15-3f72bcef45c1", > "b040d1e4-dd96-4729-8f55-4da4c958ff8f", > "f82337ea-1e0c-4c28-a491-4916be594b49", > "0f8b8f57-5aa4-4c30-be0a-c89eeedc2012" > ] > }, > "vertices": { > "0f8b8f57-5aa4-4c30-be0a-c89eeedc2012": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__tempQueryResultStruct64", > "values": { > "name": "primary.default.employee", > "vertexId": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__IdType", > "values": { > "guid": > "0f8b8f57-5aa4-4c30-be0a-c89eeedc2012", > "typeName": "hive_table" > } > } > } > }, > "364d6dc1-fdcc-4d03-8df7-cf1d835730af": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__tempQueryResultStruct64", > "values": { > "name": "primary.default.t1", > "vertexId": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__IdType", > "values": { > "guid": > "364d6dc1-fdcc-4d03-8df7-cf1d835730af", > "typeName": "hive_table" > } > } > } > }, > "5a3ecb0e-adc9-40c9-8296-9132d7ad1838": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__tempQueryResultStruct64", > "values": { >
[jira] [Commented] (ATLAS-284) UI not displaying the lineage for complex hive table (CTAS)
[ https://issues.apache.org/jira/browse/ATLAS-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14992316#comment-14992316 ] Erik Bergenholtz commented on ATLAS-284: [~ayubkhan] - do we see the same behavior with Beeline? [~shwethags] - does the atlas post execution hive hook fire through the hive cli? For some reason I recall some specific problem with this. > UI not displaying the lineage for complex hive table (CTAS) > --- > > Key: ATLAS-284 > URL: https://issues.apache.org/jira/browse/ATLAS-284 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Ayub Khan >Assignee: Rohit > Fix For: 0.6-incubating > > Attachments: graph_not_shown_application.log > > > UI not displaying the lineage for complex hive table (CTAS). > 1. On hive cli, create a hive table using CTAS just like below.. > Use this query: > create table table_1251 as select employee.salary as salary, t2.temp as > integer, t1.temp as number, nested.propertyid as > string, nested.propertyName as propname, table_1243.number as num, > table_1250.number as prism, temp_batting.col_value as > temp1 from employee, t2, t1, nested, table_1243, table_1250, temp_batting; > 2. Now try to view the graph on ATLAS UI for the above table. - No Graph is > displayed where as the backend API request is successful. > {noformat} > curl > 'http://localhost:21000/api/atlas/lineage/hive/table/primary.default.table_1261/inputs/graph' > -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive' > -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer: > http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent: > Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, > like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed | python -m > json.tool > % Total% Received % Xferd Average Speed TimeTime Time > Current > Dload Upload Total SpentLeft Speed > 100 38250 38250 0 3813 0 --:--:-- 0:00:01 --:--:-- 3813 > { > "requestId": "qtp1610708593-415 - fb672eb4-2ce2-4485-8350-ba1f919ece02", > "results": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__tempQueryResultStruct65", > "values": { > "edges": { > "5a3ecb0e-adc9-40c9-8296-9132d7ad1838": [ > "ebde1571-2ced-46d6-b65c-558835224764" > ], > "ebde1571-2ced-46d6-b65c-558835224764": [ > "364d6dc1-fdcc-4d03-8df7-cf1d835730af", > "6b52aa8f-134d-4ab7-9389-4568fac87533", > "7c1af593-b7b1-4838-815b-872b8a163a40", > "ce01cbb6-ffd5-42c8-8c15-3f72bcef45c1", > "b040d1e4-dd96-4729-8f55-4da4c958ff8f", > "f82337ea-1e0c-4c28-a491-4916be594b49", > "0f8b8f57-5aa4-4c30-be0a-c89eeedc2012" > ] > }, > "vertices": { > "0f8b8f57-5aa4-4c30-be0a-c89eeedc2012": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__tempQueryResultStruct64", > "values": { > "name": "primary.default.employee", > "vertexId": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__IdType", > "values": { > "guid": > "0f8b8f57-5aa4-4c30-be0a-c89eeedc2012", > "typeName": "hive_table" > } > } > } > }, > "364d6dc1-fdcc-4d03-8df7-cf1d835730af": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__tempQueryResultStruct64", > "values": { > "name": "primary.default.t1", > "vertexId": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__IdType", > "values": { > "guid": > "364d6dc1-fdcc-4d03-8df7-cf1d835730af", > "typeName": "hive_table" > } > } > } > }, > "5a3ecb0e-adc9-40c9-8296-9132d7ad1838": { >
[jira] [Created] (ATLAS-285) Hive process lineage graph API request is broken, it always returns 404.
Ayub Khan created ATLAS-285: --- Summary: Hive process lineage graph API request is broken, it always returns 404. Key: ATLAS-285 URL: https://issues.apache.org/jira/browse/ATLAS-285 Project: Atlas Issue Type: Bug Affects Versions: 0.5-incubating Reporter: Ayub Khan Assignee: Erik Bergenholtz Hive process lineage graph API request is broken, it always returns 404. 1. Hive: create table as select create table table_1265 as select employee.salary as salary from employee 2. Check the table is created in ATLAS {noformat} curl 'http://localhost:21000/api/atlas/entities/ff0d1738-d672-4906-a761-4ea419f58518' -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive' -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer: http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed | python -m json.tool % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 13990 13990 0 35155 0 --:--:-- --:--:-- --:--:-- 35871 { "GUID": "ff0d1738-d672-4906-a761-4ea419f58518", "definition": { "id": { "id": "ff0d1738-d672-4906-a761-4ea419f58518", "jsonClass": "org.apache.atlas.typesystem.json.InstanceSerialization$_Id", "typeName": "hive_table", "version": 0 }, "jsonClass": "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference", "traitNames": [], "traits": {}, "typeName": "hive_table", "values": { "columns": [ { "id": { "id": "823df549-29ae-4926-bb46-4f4c73c4657a", "jsonClass": "org.apache.atlas.typesystem.json.InstanceSerialization$_Id", "typeName": "hive_column", "version": 0 }, "jsonClass": "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference", "traitNames": [], "traits": {}, "typeName": "hive_column", "values": { "comment": null, "name": "salary", "type": "string" } } ], "comment": null, "createTime": 1446751132, "db": { "id": "37199c37-919e-499c-b7df-d14aad02a67f", "jsonClass": "org.apache.atlas.typesystem.json.InstanceSerialization$_Id", "typeName": "hive_db", "version": 0 }, "description": null, "lastAccessTime": 0, "name": "primary.default.table_1265", "owner": "apathan", "parameters": { "COLUMN_STATS_ACCURATE": "true", "numFiles": "1", "numRows": "0", "rawDataSize": "0", "totalSize": "0", "transient_lastDdlTime": "1446751132" }, "partitionKeys": null, "retention": 0, "sd": null, "tableName": "table_1265", "tableType": "MANAGED_TABLE", "temporary": false, "viewExpandedText": null, "viewOriginalText": null } }, "requestId": "qtp1610708593-14 - 65774a18-33e9-4195-8ad4-914e20dd59f8" } {noformat} 3. Now query for the corresponding hive process graph, it always returns 404.. {noformat} curl -v 'http://localhost:21000/api/atlas/lineage/hive/table/create%20table%20table_1265%20as%20select%20employee.salary%20as%20salary%20from%20employee/outputs/graph' -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive' -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer: http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed * Trying ::1... * Connected to localhost (::1) port 21000 (#0) > GET > /api/atlas/lineage/hive/table/create%20table%20table_1265%20as%20select%20employee.salary%20as%20salary%20from%20employee/outputs/graph > HTTP/1.1 > Host: localhost:21000 > Accept: application/json, text/plain, */* > Connection: keep-alive > Accept-Encoding: gzip, deflate, sdch > Referer: http://localhost:21000/ > Accept-Language: en-US,en;q=0.8 > User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) > AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36 > < HTTP/1.1 404 Not Found < Date: Thu, 05 Nov 2015 19:35
[jira] [Updated] (ATLAS-285) Hive process lineage graph API request is broken, it always returns 404.
[ https://issues.apache.org/jira/browse/ATLAS-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayub Khan updated ATLAS-285: Attachment: application.log.attach Attaching application log. > Hive process lineage graph API request is broken, it always returns 404. > > > Key: ATLAS-285 > URL: https://issues.apache.org/jira/browse/ATLAS-285 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.5-incubating >Reporter: Ayub Khan >Assignee: Erik Bergenholtz > Attachments: application.log.attach > > > Hive process lineage graph API request is broken, it always returns 404. > 1. Hive: create table as select > create table table_1265 as select employee.salary as salary from employee > 2. Check the table is created in ATLAS > {noformat} > curl > 'http://localhost:21000/api/atlas/entities/ff0d1738-d672-4906-a761-4ea419f58518' > -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive' > -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer: > http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent: > Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, > like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed | python -m > json.tool > % Total% Received % Xferd Average Speed TimeTime Time > Current > Dload Upload Total SpentLeft Speed > 100 13990 13990 0 35155 0 --:--:-- --:--:-- --:--:-- 35871 > { > "GUID": "ff0d1738-d672-4906-a761-4ea419f58518", > "definition": { > "id": { > "id": "ff0d1738-d672-4906-a761-4ea419f58518", > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Id", > "typeName": "hive_table", > "version": 0 > }, > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference", > "traitNames": [], > "traits": {}, > "typeName": "hive_table", > "values": { > "columns": [ > { > "id": { > "id": "823df549-29ae-4926-bb46-4f4c73c4657a", > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Id", > "typeName": "hive_column", > "version": 0 > }, > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference", > "traitNames": [], > "traits": {}, > "typeName": "hive_column", > "values": { > "comment": null, > "name": "salary", > "type": "string" > } > } > ], > "comment": null, > "createTime": 1446751132, > "db": { > "id": "37199c37-919e-499c-b7df-d14aad02a67f", > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Id", > "typeName": "hive_db", > "version": 0 > }, > "description": null, > "lastAccessTime": 0, > "name": "primary.default.table_1265", > "owner": "apathan", > "parameters": { > "COLUMN_STATS_ACCURATE": "true", > "numFiles": "1", > "numRows": "0", > "rawDataSize": "0", > "totalSize": "0", > "transient_lastDdlTime": "1446751132" > }, > "partitionKeys": null, > "retention": 0, > "sd": null, > "tableName": "table_1265", > "tableType": "MANAGED_TABLE", > "temporary": false, > "viewExpandedText": null, > "viewOriginalText": null > } > }, > "requestId": "qtp1610708593-14 - 65774a18-33e9-4195-8ad4-914e20dd59f8" > } > {noformat} > 3. Now query for the corresponding hive process graph, it always returns 404.. > {noformat} > curl -v > 'http://localhost:21000/api/atlas/lineage/hive/table/create%20table%20table_1265%20as%20select%20employee.salary%20as%20salary%20from%20employee/outputs/graph' > -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive' > -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer: > http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent: > Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, > like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed > * Trying ::1... > * Connected to localhost (::1) port 21000 (#0) > > GET > > /api/atlas/lineage/hive/table/create%20tabl
[jira] [Commented] (ATLAS-284) UI not displaying the lineage for complex hive table (CTAS)
[ https://issues.apache.org/jira/browse/ATLAS-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14992340#comment-14992340 ] Ayub Khan commented on ATLAS-284: - [~bergenholtz] Yes, it can be seen with beeline as well. UI snapshot link:https://monosnap.com/file/fIOtvrfD0WPEgrrvI4bGwcqZCQ0Bxj > UI not displaying the lineage for complex hive table (CTAS) > --- > > Key: ATLAS-284 > URL: https://issues.apache.org/jira/browse/ATLAS-284 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Ayub Khan >Assignee: Rohit > Fix For: 0.6-incubating > > Attachments: graph_not_shown_application.log > > > UI not displaying the lineage for complex hive table (CTAS). > 1. On hive cli, create a hive table using CTAS just like below.. > Use this query: > create table table_1251 as select employee.salary as salary, t2.temp as > integer, t1.temp as number, nested.propertyid as > string, nested.propertyName as propname, table_1243.number as num, > table_1250.number as prism, temp_batting.col_value as > temp1 from employee, t2, t1, nested, table_1243, table_1250, temp_batting; > 2. Now try to view the graph on ATLAS UI for the above table. - No Graph is > displayed where as the backend API request is successful. > {noformat} > curl > 'http://localhost:21000/api/atlas/lineage/hive/table/primary.default.table_1261/inputs/graph' > -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive' > -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer: > http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent: > Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, > like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed | python -m > json.tool > % Total% Received % Xferd Average Speed TimeTime Time > Current > Dload Upload Total SpentLeft Speed > 100 38250 38250 0 3813 0 --:--:-- 0:00:01 --:--:-- 3813 > { > "requestId": "qtp1610708593-415 - fb672eb4-2ce2-4485-8350-ba1f919ece02", > "results": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__tempQueryResultStruct65", > "values": { > "edges": { > "5a3ecb0e-adc9-40c9-8296-9132d7ad1838": [ > "ebde1571-2ced-46d6-b65c-558835224764" > ], > "ebde1571-2ced-46d6-b65c-558835224764": [ > "364d6dc1-fdcc-4d03-8df7-cf1d835730af", > "6b52aa8f-134d-4ab7-9389-4568fac87533", > "7c1af593-b7b1-4838-815b-872b8a163a40", > "ce01cbb6-ffd5-42c8-8c15-3f72bcef45c1", > "b040d1e4-dd96-4729-8f55-4da4c958ff8f", > "f82337ea-1e0c-4c28-a491-4916be594b49", > "0f8b8f57-5aa4-4c30-be0a-c89eeedc2012" > ] > }, > "vertices": { > "0f8b8f57-5aa4-4c30-be0a-c89eeedc2012": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__tempQueryResultStruct64", > "values": { > "name": "primary.default.employee", > "vertexId": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__IdType", > "values": { > "guid": > "0f8b8f57-5aa4-4c30-be0a-c89eeedc2012", > "typeName": "hive_table" > } > } > } > }, > "364d6dc1-fdcc-4d03-8df7-cf1d835730af": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__tempQueryResultStruct64", > "values": { > "name": "primary.default.t1", > "vertexId": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__IdType", > "values": { > "guid": > "364d6dc1-fdcc-4d03-8df7-cf1d835730af", > "typeName": "hive_table" > } > } > } > }, > "5a3ecb0e-adc9-40c9-8296-9132d7ad1838": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerial
[jira] [Comment Edited] (ATLAS-284) UI not displaying the lineage for complex hive table (CTAS)
[ https://issues.apache.org/jira/browse/ATLAS-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14992340#comment-14992340 ] Ayub Khan edited comment on ATLAS-284 at 11/5/15 7:50 PM: -- [~bergenholtz] Yes, this behavior can be seen with beeline as well. UI snapshot link:https://monosnap.com/file/fIOtvrfD0WPEgrrvI4bGwcqZCQ0Bxj was (Author: ayubkhan): [~bergenholtz] Yes, it can be seen with beeline as well. UI snapshot link:https://monosnap.com/file/fIOtvrfD0WPEgrrvI4bGwcqZCQ0Bxj > UI not displaying the lineage for complex hive table (CTAS) > --- > > Key: ATLAS-284 > URL: https://issues.apache.org/jira/browse/ATLAS-284 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Ayub Khan >Assignee: Rohit > Fix For: 0.6-incubating > > Attachments: graph_not_shown_application.log > > > UI not displaying the lineage for complex hive table (CTAS). > 1. On hive cli, create a hive table using CTAS just like below.. > Use this query: > create table table_1251 as select employee.salary as salary, t2.temp as > integer, t1.temp as number, nested.propertyid as > string, nested.propertyName as propname, table_1243.number as num, > table_1250.number as prism, temp_batting.col_value as > temp1 from employee, t2, t1, nested, table_1243, table_1250, temp_batting; > 2. Now try to view the graph on ATLAS UI for the above table. - No Graph is > displayed where as the backend API request is successful. > {noformat} > curl > 'http://localhost:21000/api/atlas/lineage/hive/table/primary.default.table_1261/inputs/graph' > -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive' > -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer: > http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent: > Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, > like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed | python -m > json.tool > % Total% Received % Xferd Average Speed TimeTime Time > Current > Dload Upload Total SpentLeft Speed > 100 38250 38250 0 3813 0 --:--:-- 0:00:01 --:--:-- 3813 > { > "requestId": "qtp1610708593-415 - fb672eb4-2ce2-4485-8350-ba1f919ece02", > "results": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__tempQueryResultStruct65", > "values": { > "edges": { > "5a3ecb0e-adc9-40c9-8296-9132d7ad1838": [ > "ebde1571-2ced-46d6-b65c-558835224764" > ], > "ebde1571-2ced-46d6-b65c-558835224764": [ > "364d6dc1-fdcc-4d03-8df7-cf1d835730af", > "6b52aa8f-134d-4ab7-9389-4568fac87533", > "7c1af593-b7b1-4838-815b-872b8a163a40", > "ce01cbb6-ffd5-42c8-8c15-3f72bcef45c1", > "b040d1e4-dd96-4729-8f55-4da4c958ff8f", > "f82337ea-1e0c-4c28-a491-4916be594b49", > "0f8b8f57-5aa4-4c30-be0a-c89eeedc2012" > ] > }, > "vertices": { > "0f8b8f57-5aa4-4c30-be0a-c89eeedc2012": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__tempQueryResultStruct64", > "values": { > "name": "primary.default.employee", > "vertexId": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__IdType", > "values": { > "guid": > "0f8b8f57-5aa4-4c30-be0a-c89eeedc2012", > "typeName": "hive_table" > } > } > } > }, > "364d6dc1-fdcc-4d03-8df7-cf1d835730af": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__tempQueryResultStruct64", > "values": { > "name": "primary.default.t1", > "vertexId": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__IdType", > "values": { > "guid": > "364d6dc1-fdcc-4d03-8df7-cf1d835730af", > "typeName": "hive_table" > } >
[jira] [Commented] (ATLAS-278) dashboard overlay is added in webapp/overlays
[ https://issues.apache.org/jira/browse/ATLAS-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14992980#comment-14992980 ] Sanjay Patel commented on ATLAS-278: [~shwethags] Thanks for the details. For overlays as per https://maven.apache.org/plugins/maven-war-plugin/overlays.html default target path is webapp root structure [webapp/src/main/webapp]. Now when maven war plugin was getting executed than overlays were combined in {project.build.directory} as default outputDirectory for war plugin is {project.build.directory} . I did not see any generated files in webapp/src/main/webapp. > dashboard overlay is added in webapp/overlays > - > > Key: ATLAS-278 > URL: https://issues.apache.org/jira/browse/ATLAS-278 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Sanjay Patel > > dashboard overlay is added in webapp/overlays. This should be in target again -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-278) dashboard overlay is added in webapp/overlays
[ https://issues.apache.org/jira/browse/ATLAS-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14992980#comment-14992980 ] Sanjay Patel edited comment on ATLAS-278 at 11/6/15 2:56 AM: - [~shwethags] Thanks for the details. For overlays as per https://maven.apache.org/plugins/maven-war-plugin/overlays.html default target path is webapp root structure [webapp/src/main/webapp]. Now when maven war plugin was getting executed than overlays were combined in {project.build.directory} as default outputDirectory for war plugin is {project.build.directory} .I did not see any generated files in webapp/src/main/webapp. So there were no generated files in webapp/overlays. All the files were in webapp/target. Let me know your thoughts. was (Author: sanjayp): [~shwethags] Thanks for the details. For overlays as per https://maven.apache.org/plugins/maven-war-plugin/overlays.html default target path is webapp root structure [webapp/src/main/webapp]. Now when maven war plugin was getting executed than overlays were combined in {project.build.directory} as default outputDirectory for war plugin is {project.build.directory} . I did not see any generated files in webapp/src/main/webapp. So there were no generated files in webapp/overlays. All the files in webapp/target. Let me know your thoughts > dashboard overlay is added in webapp/overlays > - > > Key: ATLAS-278 > URL: https://issues.apache.org/jira/browse/ATLAS-278 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Sanjay Patel > > dashboard overlay is added in webapp/overlays. This should be in target again -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-278) dashboard overlay is added in webapp/overlays
[ https://issues.apache.org/jira/browse/ATLAS-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14992980#comment-14992980 ] Sanjay Patel edited comment on ATLAS-278 at 11/6/15 2:55 AM: - [~shwethags] Thanks for the details. For overlays as per https://maven.apache.org/plugins/maven-war-plugin/overlays.html default target path is webapp root structure [webapp/src/main/webapp]. Now when maven war plugin was getting executed than overlays were combined in {project.build.directory} as default outputDirectory for war plugin is {project.build.directory} . I did not see any generated files in webapp/src/main/webapp. So there were no generated files in webapp/overlays. All the files in webapp/target. Let me know your thoughts was (Author: sanjayp): [~shwethags] Thanks for the details. For overlays as per https://maven.apache.org/plugins/maven-war-plugin/overlays.html default target path is webapp root structure [webapp/src/main/webapp]. Now when maven war plugin was getting executed than overlays were combined in {project.build.directory} as default outputDirectory for war plugin is {project.build.directory} . I did not see any generated files in webapp/src/main/webapp. > dashboard overlay is added in webapp/overlays > - > > Key: ATLAS-278 > URL: https://issues.apache.org/jira/browse/ATLAS-278 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Sanjay Patel > > dashboard overlay is added in webapp/overlays. This should be in target again -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-278) dashboard overlay is added in webapp/overlays
[ https://issues.apache.org/jira/browse/ATLAS-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14992980#comment-14992980 ] Sanjay Patel edited comment on ATLAS-278 at 11/6/15 2:57 AM: - [~shwethags] Thanks for the details. For overlays as per https://maven.apache.org/plugins/maven-war-plugin/overlays.html default target path is webapp root structure [webapp/src/main/webapp]. Now when maven war plugin was getting executed than overlays were combined in {project.build.directory} as default outputDirectory for war plugin is {project.build.directory}. I can not able to see any generated files in webapp/src/main/webapp. So there were no generated files in webapp/overlays. All the files were in webapp/target. Let me know your thoughts. was (Author: sanjayp): [~shwethags] Thanks for the details. For overlays as per https://maven.apache.org/plugins/maven-war-plugin/overlays.html default target path is webapp root structure [webapp/src/main/webapp]. Now when maven war plugin was getting executed than overlays were combined in {project.build.directory} as default outputDirectory for war plugin is {project.build.directory} .I did not see any generated files in webapp/src/main/webapp. So there were no generated files in webapp/overlays. All the files were in webapp/target. Let me know your thoughts. > dashboard overlay is added in webapp/overlays > - > > Key: ATLAS-278 > URL: https://issues.apache.org/jira/browse/ATLAS-278 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Sanjay Patel > > dashboard overlay is added in webapp/overlays. This should be in target again -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-278) dashboard overlay is added in webapp/overlays
[ https://issues.apache.org/jira/browse/ATLAS-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14992980#comment-14992980 ] Sanjay Patel edited comment on ATLAS-278 at 11/6/15 3:02 AM: - [~shwethags] Thanks for the details. For overlays as per https://maven.apache.org/plugins/maven-war-plugin/overlays.html default target path is webapp root structure *[webapp/src/main/webapp]*. Now when maven war plugin was getting executed than overlays were combined in *{project.build.directory}* as default outputDirectory for war plugin is *{project.build.directory}*.I can not able to see any generated files in *webapp/src/main/webapp*. So there were no generated files in webapp/overlays, all the files were in *webapp/target*. Let me know your thoughts. was (Author: sanjayp): [~shwethags] Thanks for the details. For overlays as per https://maven.apache.org/plugins/maven-war-plugin/overlays.html default target path is webapp root structure [webapp/src/main/webapp]. Now when maven war plugin was getting executed than overlays were combined in {project.build.directory} as default outputDirectory for war plugin is {project.build.directory}. I can not able to see any generated files in webapp/src/main/webapp. So there were no generated files in webapp/overlays. All the files were in webapp/target. Let me know your thoughts. > dashboard overlay is added in webapp/overlays > - > > Key: ATLAS-278 > URL: https://issues.apache.org/jira/browse/ATLAS-278 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Sanjay Patel > > dashboard overlay is added in webapp/overlays. This should be in target again -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-278) dashboard overlay is added in webapp/overlays
[ https://issues.apache.org/jira/browse/ATLAS-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14992980#comment-14992980 ] Sanjay Patel edited comment on ATLAS-278 at 11/6/15 3:02 AM: - [~shwethags] Thanks for the details. For overlays as per https://maven.apache.org/plugins/maven-war-plugin/overlays.html default target path is webapp root structure *[webapp/src/main/webapp]*. Now when maven war plugin was getting executed than overlays were combined in *{project.build.directory}* as default outputDirectory for war plugin is *{project.build.directory}*. I can not able to see any generated files in *webapp/src/main/webapp*. So there were no generated files in webapp/overlays, all the files were in *webapp/target*. Let me know your thoughts. was (Author: sanjayp): [~shwethags] Thanks for the details. For overlays as per https://maven.apache.org/plugins/maven-war-plugin/overlays.html default target path is webapp root structure *[webapp/src/main/webapp]*. Now when maven war plugin was getting executed than overlays were combined in *{project.build.directory}* as default outputDirectory for war plugin is *{project.build.directory}*.I can not able to see any generated files in *webapp/src/main/webapp*. So there were no generated files in webapp/overlays, all the files were in *webapp/target*. Let me know your thoughts. > dashboard overlay is added in webapp/overlays > - > > Key: ATLAS-278 > URL: https://issues.apache.org/jira/browse/ATLAS-278 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Sanjay Patel > > dashboard overlay is added in webapp/overlays. This should be in target again -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-278) dashboard overlay is added in webapp/overlays
[ https://issues.apache.org/jira/browse/ATLAS-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14992980#comment-14992980 ] Sanjay Patel edited comment on ATLAS-278 at 11/6/15 3:04 AM: - [~shwethags] Thanks for the details. For overlays as per https://maven.apache.org/plugins/maven-war-plugin/overlays.html default target path is webapp root structure *[webapp/src/main/webapp]*. Now when maven war plugin was getting executed than overlays were combined in *{project.build.directory}* as default outputDirectory for war plugin is {project.build.directory}. I can not able to see any generated files in *webapp/src/main/webapp*, there were no generated files in webapp/overlays, all the files were in *webapp/target*. Let me know your thoughts. was (Author: sanjayp): [~shwethags] Thanks for the details. For overlays as per https://maven.apache.org/plugins/maven-war-plugin/overlays.html default target path is webapp root structure *[webapp/src/main/webapp]*. Now when maven war plugin was getting executed than overlays were combined in *{project.build.directory}* as default outputDirectory for war plugin is *{project.build.directory}*. I can not able to see any generated files in *webapp/src/main/webapp*, there were no generated files in webapp/overlays, all the files were in *webapp/target*. Let me know your thoughts. > dashboard overlay is added in webapp/overlays > - > > Key: ATLAS-278 > URL: https://issues.apache.org/jira/browse/ATLAS-278 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Sanjay Patel > > dashboard overlay is added in webapp/overlays. This should be in target again -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-278) dashboard overlay is added in webapp/overlays
[ https://issues.apache.org/jira/browse/ATLAS-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14992980#comment-14992980 ] Sanjay Patel edited comment on ATLAS-278 at 11/6/15 3:03 AM: - [~shwethags] Thanks for the details. For overlays as per https://maven.apache.org/plugins/maven-war-plugin/overlays.html default target path is webapp root structure *[webapp/src/main/webapp]*. Now when maven war plugin was getting executed than overlays were combined in *{project.build.directory}* as default outputDirectory for war plugin is *{project.build.directory}*. I can not able to see any generated files in *webapp/src/main/webapp*, there were no generated files in webapp/overlays, all the files were in *webapp/target*. Let me know your thoughts. was (Author: sanjayp): [~shwethags] Thanks for the details. For overlays as per https://maven.apache.org/plugins/maven-war-plugin/overlays.html default target path is webapp root structure *[webapp/src/main/webapp]*. Now when maven war plugin was getting executed than overlays were combined in *{project.build.directory}* as default outputDirectory for war plugin is *{project.build.directory}*. I can not able to see any generated files in *webapp/src/main/webapp*. So there were no generated files in webapp/overlays, all the files were in *webapp/target*. Let me know your thoughts. > dashboard overlay is added in webapp/overlays > - > > Key: ATLAS-278 > URL: https://issues.apache.org/jira/browse/ATLAS-278 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Sanjay Patel > > dashboard overlay is added in webapp/overlays. This should be in target again -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Regarding Ranger Integration
This is a feature that will be available in the next release of both Atlas and Ranger. Ranger implements ABAC based on traits in Atlas. On Thu, Nov 5, 2015 at 4:41 AM Rishabh Bhardwaj wrote: > Hi all, > > We have seen in README.txt that Atlas have a Ranger Integration. > Is there any example code or something related in the codebase? > > Can someone give some pointer on this? > TIA. > > Regards, > Rishabh. >
[jira] [Commented] (ATLAS-284) UI not displaying the lineage for complex hive table (CTAS)
[ https://issues.apache.org/jira/browse/ATLAS-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993145#comment-14993145 ] Shwetha G S commented on ATLAS-284: --- Yes, hive hook is fired even through hive CLI > UI not displaying the lineage for complex hive table (CTAS) > --- > > Key: ATLAS-284 > URL: https://issues.apache.org/jira/browse/ATLAS-284 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Ayub Khan >Assignee: Rohit > Fix For: 0.6-incubating > > Attachments: graph_not_shown_application.log > > > UI not displaying the lineage for complex hive table (CTAS). > 1. On hive cli, create a hive table using CTAS just like below.. > Use this query: > create table table_1251 as select employee.salary as salary, t2.temp as > integer, t1.temp as number, nested.propertyid as > string, nested.propertyName as propname, table_1243.number as num, > table_1250.number as prism, temp_batting.col_value as > temp1 from employee, t2, t1, nested, table_1243, table_1250, temp_batting; > 2. Now try to view the graph on ATLAS UI for the above table. - No Graph is > displayed where as the backend API request is successful. > {noformat} > curl > 'http://localhost:21000/api/atlas/lineage/hive/table/primary.default.table_1261/inputs/graph' > -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive' > -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer: > http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent: > Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, > like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed | python -m > json.tool > % Total% Received % Xferd Average Speed TimeTime Time > Current > Dload Upload Total SpentLeft Speed > 100 38250 38250 0 3813 0 --:--:-- 0:00:01 --:--:-- 3813 > { > "requestId": "qtp1610708593-415 - fb672eb4-2ce2-4485-8350-ba1f919ece02", > "results": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__tempQueryResultStruct65", > "values": { > "edges": { > "5a3ecb0e-adc9-40c9-8296-9132d7ad1838": [ > "ebde1571-2ced-46d6-b65c-558835224764" > ], > "ebde1571-2ced-46d6-b65c-558835224764": [ > "364d6dc1-fdcc-4d03-8df7-cf1d835730af", > "6b52aa8f-134d-4ab7-9389-4568fac87533", > "7c1af593-b7b1-4838-815b-872b8a163a40", > "ce01cbb6-ffd5-42c8-8c15-3f72bcef45c1", > "b040d1e4-dd96-4729-8f55-4da4c958ff8f", > "f82337ea-1e0c-4c28-a491-4916be594b49", > "0f8b8f57-5aa4-4c30-be0a-c89eeedc2012" > ] > }, > "vertices": { > "0f8b8f57-5aa4-4c30-be0a-c89eeedc2012": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__tempQueryResultStruct64", > "values": { > "name": "primary.default.employee", > "vertexId": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__IdType", > "values": { > "guid": > "0f8b8f57-5aa4-4c30-be0a-c89eeedc2012", > "typeName": "hive_table" > } > } > } > }, > "364d6dc1-fdcc-4d03-8df7-cf1d835730af": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__tempQueryResultStruct64", > "values": { > "name": "primary.default.t1", > "vertexId": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__IdType", > "values": { > "guid": > "364d6dc1-fdcc-4d03-8df7-cf1d835730af", > "typeName": "hive_table" > } > } > } > }, > "5a3ecb0e-adc9-40c9-8296-9132d7ad1838": { > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", > "typeName": "__tempQueryResultStruct64", >
[jira] [Commented] (ATLAS-285) Hive process lineage graph API request is broken, it always returns 404.
[ https://issues.apache.org/jira/browse/ATLAS-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993160#comment-14993160 ] Shwetha G S commented on ATLAS-285: --- {noformat} curl -v 'http://localhost:21000/api/atlas/lineage/hive/table/create%20table%20table_1265%20as%20select%20employee.salary%20as%20salary%20from%20employee/outputs/graph {noformat} The table name in the path above should be tablename. Why is it CTAS query? Is this on trunk? > Hive process lineage graph API request is broken, it always returns 404. > > > Key: ATLAS-285 > URL: https://issues.apache.org/jira/browse/ATLAS-285 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.5-incubating >Reporter: Ayub Khan >Assignee: Erik Bergenholtz > Attachments: application.log.attach > > > Hive process lineage graph API request is broken, it always returns 404. > 1. Hive: create table as select > create table table_1265 as select employee.salary as salary from employee > 2. Check the table is created in ATLAS > {noformat} > curl > 'http://localhost:21000/api/atlas/entities/ff0d1738-d672-4906-a761-4ea419f58518' > -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive' > -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer: > http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent: > Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, > like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed | python -m > json.tool > % Total% Received % Xferd Average Speed TimeTime Time > Current > Dload Upload Total SpentLeft Speed > 100 13990 13990 0 35155 0 --:--:-- --:--:-- --:--:-- 35871 > { > "GUID": "ff0d1738-d672-4906-a761-4ea419f58518", > "definition": { > "id": { > "id": "ff0d1738-d672-4906-a761-4ea419f58518", > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Id", > "typeName": "hive_table", > "version": 0 > }, > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference", > "traitNames": [], > "traits": {}, > "typeName": "hive_table", > "values": { > "columns": [ > { > "id": { > "id": "823df549-29ae-4926-bb46-4f4c73c4657a", > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Id", > "typeName": "hive_column", > "version": 0 > }, > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference", > "traitNames": [], > "traits": {}, > "typeName": "hive_column", > "values": { > "comment": null, > "name": "salary", > "type": "string" > } > } > ], > "comment": null, > "createTime": 1446751132, > "db": { > "id": "37199c37-919e-499c-b7df-d14aad02a67f", > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Id", > "typeName": "hive_db", > "version": 0 > }, > "description": null, > "lastAccessTime": 0, > "name": "primary.default.table_1265", > "owner": "apathan", > "parameters": { > "COLUMN_STATS_ACCURATE": "true", > "numFiles": "1", > "numRows": "0", > "rawDataSize": "0", > "totalSize": "0", > "transient_lastDdlTime": "1446751132" > }, > "partitionKeys": null, > "retention": 0, > "sd": null, > "tableName": "table_1265", > "tableType": "MANAGED_TABLE", > "temporary": false, > "viewExpandedText": null, > "viewOriginalText": null > } > }, > "requestId": "qtp1610708593-14 - 65774a18-33e9-4195-8ad4-914e20dd59f8" > } > {noformat} > 3. Now query for the corresponding hive process graph, it always returns 404.. > {noformat} > curl -v > 'http://localhost:21000/api/atlas/lineage/hive/table/create%20table%20table_1265%20as%20select%20employee.salary%20as%20salary%20from%20employee/outputs/graph' > -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive' > -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer: > http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H
[jira] [Resolved] (ATLAS-278) dashboard overlay is added in webapp/overlays
[ https://issues.apache.org/jira/browse/ATLAS-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S resolved ATLAS-278. --- Resolution: Invalid I don't see webapp/overlay anymore. Probably some intermediate code. Will re-open if I see again. Thanks > dashboard overlay is added in webapp/overlays > - > > Key: ATLAS-278 > URL: https://issues.apache.org/jira/browse/ATLAS-278 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Sanjay Patel > > dashboard overlay is added in webapp/overlays. This should be in target again -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-285) Hive process lineage graph API request is broken, it always returns 404.
[ https://issues.apache.org/jira/browse/ATLAS-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993186#comment-14993186 ] Ayub Khan commented on ATLAS-285: - Yes, this is on trunk.. Hive process query returns name as CTAS {noformat} curl 'http://localhost:21000/api/atlas/entities/16ac8f61-d618-40e6-8c45-98afc11069e2' -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive' -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer: http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed | python -m json.tool % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 39200 39200 0 218k 0 --:--:-- --:--:-- --:--:-- 225k { "GUID": "16ac8f61-d618-40e6-8c45-98afc11069e2", "definition": { "id": { "id": "16ac8f61-d618-40e6-8c45-98afc11069e2", "jsonClass": "org.apache.atlas.typesystem.json.InstanceSerialization$_Id", "typeName": "hive_process", "version": 0 }, "jsonClass": "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference", "traitNames": [], "traits": {}, "typeName": "hive_process", "values": { "description": null, "endTime": 1446788566440, "inputs": [ { "id": "266edf90-6c75-495e-a15a-4e23aeb24833", "jsonClass": "org.apache.atlas.typesystem.json.InstanceSerialization$_Id", "typeName": "DataSet", "version": 0 } ], "name": "create table table_1266 as select employee.salary as salary from employee", "outputs": [ { "id": "d2a54980-ac8a-408e-895b-d646d937a978", "jsonClass": "org.apache.atlas.typesystem.json.InstanceSerialization$_Id", "typeName": "DataSet", "version": 0 } ], "queryGraph": "queryGraph", "queryId": "apathan_20151106111240_2cd0013f-62b2-4796-9f36-68ce418df593", "queryPlan": "{\"STAGE DEPENDENCIES\":{\"Stage-7\":{\"DEPENDENT STAGES\":\"Stage-1\",\"CONDITIONAL CHILD TASKS\":\"Stage-4, Stage-3, Stage-5\"},\"Stage-8\":{\"DEPENDENT STAGES\":\"Stage-0\"},\"Stage-5\":{},\"Stage-6\":{},\"Stage-3\":{},\"Stage-4\":{\"DEPENDENT STAGES\":\"Stage-1\"},\"Stage-1\":{\"ROOT STAGE\":\"TRUE\"},\"Stage-2\":{\"DEPENDENT STAGES\":\"Stage-8\"},\"Stage-0\":{\"DEPENDENT STAGES\":\"Stage-4\"}},\"STAGE PLANS\":{\"Stage-7\":{\"Conditional Operator\":{}},\"Stage-8\":{\"Create Table Operator:\":{\"Create Table\":{\"serde name:\":\"org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe\",\"name:\":\"default.table_1266\",\"input format:\":\"org.apache.hadoop.mapred.TextInputFormat\",\"output format:\":\"org.apache.hadoop.hive.ql.io.IgnoreKeyTextOutputFormat\",\"columns:\":[\"salary string\"]}}},\"Stage-5\":{\"Map Reduce\":{\"Map Operator Tree:\":[{\"TableScan\":{\"children\":{\"File Output Operator\":{\"compressed:\":\"false\",\"table:\":{\"name:\":\"default.table_1266\",\"input format:\":\"org.apache.hadoop.mapred.TextInputFormat\",\"output format:\":\"org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat\",\"serde:\":\"org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe\"}]}},\"Stage-6\":{\"Move Operator\":{\"files:\":{\"hdfs directory:\":\"true\",\"destination:\":\"hdfs://localhost:9000/user/hive/warehouse/.hive-staging_hive_2015-11-06_11-12-40_235_2405139051056370584-1/-ext-10001\"}}},\"Stage-3\":{\"Map Reduce\":{\"Map Operator Tree:\":[{\"TableScan\":{\"children\":{\"File Output Operator\":{\"compressed:\":\"false\",\"table:\":{\"name:\":\"default.table_1266\",\"input format:\":\"org.apache.hadoop.mapred.TextInputFormat\",\"output format:\":\"org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat\",\"serde:\":\"org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe\"}]}},\"Stage-4\":{\"Move Operator\":{\"files:\":{\"hdfs directory:\":\"true\",\"destination:\":\"hdfs://localhost:9000/user/hive/warehouse/.hive-staging_hive_2015-11-06_11-12-40_235_2405139051056370584-1/-ext-10001\"}}},\"Stage-1\":{\"Map Reduce\":{\"Map Operator Tree:\":[{\"TableScan\":{\"alias:\":\"employee\",\"children\":{\"Select Operator\":{\"children\":{\"File Output Operator\":{\"compressed:\":\"false\",\"table:\":{\"name:\":\"default.table_1266\",\"input format:\":\"org.apache.hadoop.mapred.TextInputFormat\",\"output format:\":\"org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat\",\"serde:\":\"org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe\"}}},\"outputColumnNam
[jira] [Commented] (ATLAS-285) Hive process lineage graph API request is broken, it always returns 404.
[ https://issues.apache.org/jira/browse/ATLAS-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993189#comment-14993189 ] Shwetha G S commented on ATLAS-285: --- The lineage API is on data set which is hive_table in this case. Its not on process. So, the argument should be hive table name of format clustername.dbname.tablename. Its documented in https://github.com/apache/incubator-atlas/blob/master/docs/src/site/twiki/Bridge-Hive.twiki > Hive process lineage graph API request is broken, it always returns 404. > > > Key: ATLAS-285 > URL: https://issues.apache.org/jira/browse/ATLAS-285 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.5-incubating >Reporter: Ayub Khan >Assignee: Erik Bergenholtz > Attachments: application.log.attach > > > Hive process lineage graph API request is broken, it always returns 404. > 1. Hive: create table as select > create table table_1265 as select employee.salary as salary from employee > 2. Check the table is created in ATLAS > {noformat} > curl > 'http://localhost:21000/api/atlas/entities/ff0d1738-d672-4906-a761-4ea419f58518' > -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive' > -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer: > http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent: > Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, > like Gecko) Chrome/46.0.2490.80 Safari/537.36' --compressed | python -m > json.tool > % Total% Received % Xferd Average Speed TimeTime Time > Current > Dload Upload Total SpentLeft Speed > 100 13990 13990 0 35155 0 --:--:-- --:--:-- --:--:-- 35871 > { > "GUID": "ff0d1738-d672-4906-a761-4ea419f58518", > "definition": { > "id": { > "id": "ff0d1738-d672-4906-a761-4ea419f58518", > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Id", > "typeName": "hive_table", > "version": 0 > }, > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference", > "traitNames": [], > "traits": {}, > "typeName": "hive_table", > "values": { > "columns": [ > { > "id": { > "id": "823df549-29ae-4926-bb46-4f4c73c4657a", > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Id", > "typeName": "hive_column", > "version": 0 > }, > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference", > "traitNames": [], > "traits": {}, > "typeName": "hive_column", > "values": { > "comment": null, > "name": "salary", > "type": "string" > } > } > ], > "comment": null, > "createTime": 1446751132, > "db": { > "id": "37199c37-919e-499c-b7df-d14aad02a67f", > "jsonClass": > "org.apache.atlas.typesystem.json.InstanceSerialization$_Id", > "typeName": "hive_db", > "version": 0 > }, > "description": null, > "lastAccessTime": 0, > "name": "primary.default.table_1265", > "owner": "apathan", > "parameters": { > "COLUMN_STATS_ACCURATE": "true", > "numFiles": "1", > "numRows": "0", > "rawDataSize": "0", > "totalSize": "0", > "transient_lastDdlTime": "1446751132" > }, > "partitionKeys": null, > "retention": 0, > "sd": null, > "tableName": "table_1265", > "tableType": "MANAGED_TABLE", > "temporary": false, > "viewExpandedText": null, > "viewOriginalText": null > } > }, > "requestId": "qtp1610708593-14 - 65774a18-33e9-4195-8ad4-914e20dd59f8" > } > {noformat} > 3. Now query for the corresponding hive process graph, it always returns 404.. > {noformat} > curl -v > 'http://localhost:21000/api/atlas/lineage/hive/table/create%20table%20table_1265%20as%20select%20employee.salary%20as%20salary%20from%20employee/outputs/graph' > -H 'Accept: application/json, text/plain, */*' -H 'Connection: keep-alive' > -H 'Accept-Encoding: gzip, deflate, sdch' -H 'Referer: > http://localhost:21000/' -H 'Accept-Language: en-US,en;q=0.8' -H 'Us