[jira] [Commented] (ATLAS-219) UI: Add ability to detach trait from the entity
[
https://issues.apache.org/jira/browse/ATLAS-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14985717#comment-14985717
]
Anilsg commented on ATLAS-219:
--
In details page add 'X' to every tag's , on click the 'X' tag's will be removed
on confirmation
Patch sent as part of ATLAS-211
Tested on http://162.212.133.190:3172/#!/search
> UI: Add ability to detach trait from the entity
> ---
>
> Key: ATLAS-219
> URL: https://issues.apache.org/jira/browse/ATLAS-219
> Project: Atlas
> Issue Type: Improvement
>Reporter: Ayub Khan
>Assignee: Anilsg
>Priority: Blocker
>
> Currently we are able to detach trait from the entity using REST API.
> Similar support can be provided via ATLAS-UI.
> {code}
> curl -X DELETE -v
> 'http://localhost:21000/api/atlas/entity/9646d28d-bbea-4cc5-9d84-0d37f0ca536c/traits/PII'
> * Trying ::1...
> * Connected to localhost (::1) port 21000 (#0)
> > DELETE /api/atlas/entity/9646d28d-bbea-4cc5-9d84-0d37f0ca536c/traits/PII
> > HTTP/1.1
> > Host: localhost:21000
> > User-Agent: curl/7.43.0
> > Accept: */*
> >
> < HTTP/1.1 200 OK
> < Date: Mon, 12 Oct 2015 15:34:15 GMT
> < Content-Type: application/json; charset=UTF-8
> < Transfer-Encoding: chunked
> < Server: Jetty(9.2.12.v20150709)
> <
> * Connection #0 to host localhost left intact
> {"requestId":"qtp468469-162 -
> 387b46eb-4fca-4547-aef7-f53590b9c069","GUID":"9646d28d-bbea-4cc5-9d84-0d37f0ca536c","traitName":"PII"}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (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 ] Darshan Kumar reassigned ATLAS-214: --- Assignee: Darshan Kumar (was: Anilsg) > 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] [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-219-ATLAS-214_v9.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-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-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:comment-tabpanel=14985743#comment-14985743 ] Anilsg commented on ATLAS-214: -- implemented as expected Tested on http://162.212.133.190:3172/#!/search?query=Table Patch is sent as part of ATLAS-211 > 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=14985744#comment-14985744 ] Darshan Kumar commented on ATLAS-211: - Please find the updated patch [ATLAS-211-ATLAS-219-ATLAS-214_v9.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-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] [Assigned] (ATLAS-219) UI: Add ability to detach trait from the entity
[
https://issues.apache.org/jira/browse/ATLAS-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anilsg reassigned ATLAS-219:
Assignee: Anilsg (was: Rohit)
> UI: Add ability to detach trait from the entity
> ---
>
> Key: ATLAS-219
> URL: https://issues.apache.org/jira/browse/ATLAS-219
> Project: Atlas
> Issue Type: Improvement
>Reporter: Ayub Khan
>Assignee: Anilsg
>Priority: Blocker
>
> Currently we are able to detach trait from the entity using REST API.
> Similar support can be provided via ATLAS-UI.
> {code}
> curl -X DELETE -v
> 'http://localhost:21000/api/atlas/entity/9646d28d-bbea-4cc5-9d84-0d37f0ca536c/traits/PII'
> * Trying ::1...
> * Connected to localhost (::1) port 21000 (#0)
> > DELETE /api/atlas/entity/9646d28d-bbea-4cc5-9d84-0d37f0ca536c/traits/PII
> > HTTP/1.1
> > Host: localhost:21000
> > User-Agent: curl/7.43.0
> > Accept: */*
> >
> < HTTP/1.1 200 OK
> < Date: Mon, 12 Oct 2015 15:34:15 GMT
> < Content-Type: application/json; charset=UTF-8
> < Transfer-Encoding: chunked
> < Server: Jetty(9.2.12.v20150709)
> <
> * Connection #0 to host localhost left intact
> {"requestId":"qtp468469-162 -
> 387b46eb-4fca-4547-aef7-f53590b9c069","GUID":"9646d28d-bbea-4cc5-9d84-0d37f0ca536c","traitName":"PII"}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (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 ] Anilsg reassigned ATLAS-214: Assignee: Anilsg (was: Rohit) > 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: Anilsg >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] [Resolved] (ATLAS-219) UI: Add ability to detach trait from the entity
[
https://issues.apache.org/jira/browse/ATLAS-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anilsg resolved ATLAS-219.
--
Resolution: Fixed
> UI: Add ability to detach trait from the entity
> ---
>
> Key: ATLAS-219
> URL: https://issues.apache.org/jira/browse/ATLAS-219
> Project: Atlas
> Issue Type: Improvement
>Reporter: Ayub Khan
>Assignee: Anilsg
>Priority: Blocker
>
> Currently we are able to detach trait from the entity using REST API.
> Similar support can be provided via ATLAS-UI.
> {code}
> curl -X DELETE -v
> 'http://localhost:21000/api/atlas/entity/9646d28d-bbea-4cc5-9d84-0d37f0ca536c/traits/PII'
> * Trying ::1...
> * Connected to localhost (::1) port 21000 (#0)
> > DELETE /api/atlas/entity/9646d28d-bbea-4cc5-9d84-0d37f0ca536c/traits/PII
> > HTTP/1.1
> > Host: localhost:21000
> > User-Agent: curl/7.43.0
> > Accept: */*
> >
> < HTTP/1.1 200 OK
> < Date: Mon, 12 Oct 2015 15:34:15 GMT
> < Content-Type: application/json; charset=UTF-8
> < Transfer-Encoding: chunked
> < Server: Jetty(9.2.12.v20150709)
> <
> * Connection #0 to host localhost left intact
> {"requestId":"qtp468469-162 -
> 387b46eb-4fca-4547-aef7-f53590b9c069","GUID":"9646d28d-bbea-4cc5-9d84-0d37f0ca536c","traitName":"PII"}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (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 ] Anilsg resolved ATLAS-214. -- Resolution: Fixed > 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] [Updated] (ATLAS-275) Improve error message when creating a trait and not specifying all required trait attributes
[ https://issues.apache.org/jira/browse/ATLAS-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Speidel updated ATLAS-275: --- Attachment: ATLAS-275.patch > Improve error message when creating a trait and not specifying all required > trait attributes > > > Key: ATLAS-275 > URL: https://issues.apache.org/jira/browse/ATLAS-275 > Project: Atlas > Issue Type: Task >Reporter: John Speidel >Assignee: John Speidel > Attachments: ATLAS-275.patch > > > When an attempt is made to add a trait to an entity where not all of the > trait attributes are provided, the error msg returned to the user is: > "Error deserializing trait instance" > The user than needs to dig through the provided stack trace to see what the > actual problem is. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-275) Improve error message when creating a trait and not specifying all required trait attributes
John Speidel created ATLAS-275: -- Summary: Improve error message when creating a trait and not specifying all required trait attributes Key: ATLAS-275 URL: https://issues.apache.org/jira/browse/ATLAS-275 Project: Atlas Issue Type: Task Reporter: John Speidel Assignee: John Speidel When an attempt is made to add a trait to an entity where not all of the trait attributes are provided, the error msg returned to the user is: "Error deserializing trait instance" The user than need to dig through the provided stack trace to see what the actual problem is. -- 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=14985990#comment-14985990
]
Tom Beerbower commented on ATLAS-208:
-
[~shwethags]
I like the change to the API response but doesn't it break existing 0.5 users?
I think that anyone making a GET entity or GET type API call now is expecting
the description attribute in the response to be a String, not JSON. Is that a
problem?
> 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: trunk
>
> 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] [Comment Edited] (ATLAS-275) Improve error message when creating a trait and not specifying all required trait attributes
[
https://issues.apache.org/jira/browse/ATLAS-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14985901#comment-14985901
]
John Speidel edited comment on ATLAS-275 at 11/2/15 7:55 PM:
-
Attached patch provides better error message when a required trait attribute is
missing:
{code}
error: "Invalid Trait specified. Field 'expiry_date' can't be null:
AttributeInfo{name='expiry_date',
dataType=org.apache.atlas.typesystem.types.DataTypes$DateType@70cfbe37,
multiplicity=Multiplicity{lower=1, upper=1, isUnique=false}, isComposite=false,
isUnique=false, isIndexable=true, reverseAttributeName='null'}"
{code}
was (Author: jspeidel):
Attached patch provides better error message when a required trait attribute is
missing:
error: "Invalid Trait specified. Field 'expiry_date' can't be null:
AttributeInfo{name='expiry_date',
dataType=org.apache.atlas.typesystem.types.DataTypes$DateType@70cfbe37,
multiplicity=Multiplicity{lower=1, upper=1, isUnique=false}, isComposite=false,
isUnique=false, isIndexable=true, reverseAttributeName='null'}"
> Improve error message when creating a trait and not specifying all required
> trait attributes
>
>
> Key: ATLAS-275
> URL: https://issues.apache.org/jira/browse/ATLAS-275
> Project: Atlas
> Issue Type: Task
>Reporter: John Speidel
>Assignee: John Speidel
> Attachments: ATLAS-275.patch
>
>
> When an attempt is made to add a trait to an entity where not all of the
> trait attributes are provided, the error msg returned to the user is:
> "Error deserializing trait instance"
> The user than needs to dig through the provided stack trace to see what the
> actual problem is.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-275) Improve error message when creating a trait and not specifying all required trait attributes
[ https://issues.apache.org/jira/browse/ATLAS-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Speidel updated ATLAS-275: --- Description: When an attempt is made to add a trait to an entity where not all of the trait attributes are provided, the error msg returned to the user is: "Error deserializing trait instance" The user than needs to dig through the provided stack trace to see what the actual problem is. was: When an attempt is made to add a trait to an entity where not all of the trait attributes are provided, the error msg returned to the user is: "Error deserializing trait instance" The user than need to dig through the provided stack trace to see what the actual problem is. > Improve error message when creating a trait and not specifying all required > trait attributes > > > Key: ATLAS-275 > URL: https://issues.apache.org/jira/browse/ATLAS-275 > Project: Atlas > Issue Type: Task >Reporter: John Speidel >Assignee: John Speidel > > When an attempt is made to add a trait to an entity where not all of the > trait attributes are provided, the error msg returned to the user is: > "Error deserializing trait instance" > The user than needs to dig through the provided stack trace to see what the > actual problem is. -- 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=14984874#comment-14984874 ] Darshan Kumar commented on ATLAS-211: - The UI changes are made and Patch is updated.[ATLAS-211-ATLAS-255-ATLAS-264_v8.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-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] [Created] (ATLAS-274) No lineage is recorded for creating a table using LIKE
Ayub Khan created ATLAS-274:
---
Summary: No lineage is recorded for creating a table using LIKE
Key: ATLAS-274
URL: https://issues.apache.org/jira/browse/ATLAS-274
Project: Atlas
Issue Type: Bug
Affects Versions: 0.6-incubating
Reporter: Ayub Khan
Seems like no lineage is recorded for creating a table using LIKE
example:
create table table_1242 LIKE table_1240
Input graph query
{noformat}
curl
'http://localhost:21000/api/atlas/lineage/hive/table/primary.default.table_1242/inputs/graph'
-H 'Accept-Encoding: gzip, deflate, sdch' -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' -H
'Accept: application/json, text/plain, */*' -H 'Referer:
http://localhost:21000/' -H 'Cookie: JSESSIONID=15b7c1abmgzpsv2gax1e68sor' -H
'Connection: keep-alive' --compressed | python -m json.tool
{
"requestId": "qtp983814036-14184 - f97fb1cb-be0b-4eaa-8338-5c1543803438",
"results": {
"jsonClass":
"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
"typeName": "__tempQueryResultStruct267",
"values": {
"edges": {},
"vertices": {}
}
},
"tableName": "primary.default.table_1242"
}
{noformat}
Output graph query
{noformat}
curl
'http://localhost:21000/api/atlas/lineage/hive/table/primary.default.table_1242/outputs/graph'
-H 'Accept-Encoding: gzip, deflate, sdch' -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' -H
'Accept: application/json, text/plain, */*' -H 'Referer:
http://localhost:21000/' -H 'Cookie: JSESSIONID=15b7c1abmgzpsv2gax1e68sor' -H
'Connection: keep-alive' --compressed | python -m json.tool
{
"requestId": "qtp983814036-14184 - 14e8cbc2-c2df-42b5-b506-51649fe2705b",
"results": {
"jsonClass":
"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
"typeName": "__tempQueryResultStruct261",
"values": {
"edges": {},
"vertices": {}
}
},
"tableName": "primary.default.table_1242"
}
{noformat}
--
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=14984921#comment-14984921
]
David Kaspar commented on ATLAS-242:
[~shwethags]: Thanks for help - it works properly when using this table format.
Please, feel free to close the issue as Invalid. Would it be possible to add
this note to the API documentation?
> 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-271) Hive data model import fails if there exists any type of name "hive_process"
[
https://issues.apache.org/jira/browse/ATLAS-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14984918#comment-14984918
]
Ayub Khan commented on ATLAS-271:
-
This should be documented in the release notes as this has very high chances of
production occurrence.
> Hive data model import fails if there exists any type of name "hive_process"
>
>
> Key: ATLAS-271
> URL: https://issues.apache.org/jira/browse/ATLAS-271
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.6-incubating
>Reporter: Ayub Khan
>
> Hive data model import fails if there exists a type of name "hive_process"
> 1. Create a trait with typename as hive_process.
> For example:
> {noformat}
> curl 'http://localhost:21000/api/atlas/types' -H 'Origin:
> http://localhost:21000' -H 'Content-Type: application/json;charset=UTF-8'
> --data-binary
> '{"enumTypes":[],"traitTypes":[{"superTypes":[],"typeName":"hive_process","attributeDefinitions":[],"hierarchicalMetaTypeName":"org.apache.atlas.typesystem.types.TraitType"}],"structTypes":[],"classTypes":[]}'
> --compressed
> {noformat}
> 2. Now run import_hive.sh
> Import hive data model fails because atlas thinks that hive data model is
> already registered.
> This issue is quite possible when the user/admin(mostly unaware of hive data
> model and its types) is creating tags while bringing atlas.
> hive data model is just an example, this issue can happen with any data model.
> One solution might be to restrict creating types with reserved keywords.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-274) No lineage is recorded for creating a table using LIKE
[
https://issues.apache.org/jira/browse/ATLAS-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan updated ATLAS-274:
Attachment: application.log
Attaching application log for reference.
> No lineage is recorded for creating a table using LIKE
> --
>
> Key: ATLAS-274
> URL: https://issues.apache.org/jira/browse/ATLAS-274
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.6-incubating
>Reporter: Ayub Khan
> Attachments: application.log
>
>
> Seems like no lineage is recorded for creating a table using LIKE
> example:
> create table table_1242 LIKE table_1240
> Input graph query
> {noformat}
> curl
> 'http://localhost:21000/api/atlas/lineage/hive/table/primary.default.table_1242/inputs/graph'
> -H 'Accept-Encoding: gzip, deflate, sdch' -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' -H 'Accept: application/json, text/plain, */*' -H 'Referer:
> http://localhost:21000/' -H 'Cookie: JSESSIONID=15b7c1abmgzpsv2gax1e68sor' -H
> 'Connection: keep-alive' --compressed | python -m json.tool
> {
> "requestId": "qtp983814036-14184 - f97fb1cb-be0b-4eaa-8338-5c1543803438",
> "results": {
> "jsonClass":
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
> "typeName": "__tempQueryResultStruct267",
> "values": {
> "edges": {},
> "vertices": {}
> }
> },
> "tableName": "primary.default.table_1242"
> }
> {noformat}
> Output graph query
> {noformat}
> curl
> 'http://localhost:21000/api/atlas/lineage/hive/table/primary.default.table_1242/outputs/graph'
> -H 'Accept-Encoding: gzip, deflate, sdch' -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' -H 'Accept: application/json, text/plain, */*' -H 'Referer:
> http://localhost:21000/' -H 'Cookie: JSESSIONID=15b7c1abmgzpsv2gax1e68sor' -H
> 'Connection: keep-alive' --compressed | python -m json.tool
> {
> "requestId": "qtp983814036-14184 - 14e8cbc2-c2df-42b5-b506-51649fe2705b",
> "results": {
> "jsonClass":
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
> "typeName": "__tempQueryResultStruct261",
> "values": {
> "edges": {},
> "vertices": {}
> }
> },
> "tableName": "primary.default.table_1242"
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ATLAS-271) Hive data model import fails if there exists any type of name "hive_process"
[
https://issues.apache.org/jira/browse/ATLAS-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14984907#comment-14984907
]
Shwetha G S commented on ATLAS-271:
---
The way to address it is by using namespaces for types. It can't be fixed
without namespaces
> Hive data model import fails if there exists any type of name "hive_process"
>
>
> Key: ATLAS-271
> URL: https://issues.apache.org/jira/browse/ATLAS-271
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.6-incubating
>Reporter: Ayub Khan
>
> Hive data model import fails if there exists a type of name "hive_process"
> 1. Create a trait with typename as hive_process.
> For example:
> {noformat}
> curl 'http://localhost:21000/api/atlas/types' -H 'Origin:
> http://localhost:21000' -H 'Content-Type: application/json;charset=UTF-8'
> --data-binary
> '{"enumTypes":[],"traitTypes":[{"superTypes":[],"typeName":"hive_process","attributeDefinitions":[],"hierarchicalMetaTypeName":"org.apache.atlas.typesystem.types.TraitType"}],"structTypes":[],"classTypes":[]}'
> --compressed
> {noformat}
> 2. Now run import_hive.sh
> Import hive data model fails because atlas thinks that hive data model is
> already registered.
> This issue is quite possible when the user/admin(mostly unaware of hive data
> model and its types) is creating tags while bringing atlas.
> hive data model is just an example, this issue can happen with any data model.
> One solution might be to restrict creating types with reserved keywords.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (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:all-tabpanel
]
David Kaspar updated ATLAS-242:
---
Comment: was deleted
(was: 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] [Assigned] (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:all-tabpanel
]
Shwetha G S reassigned ATLAS-242:
-
Assignee: Shwetha G S
> 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
>Assignee: Shwetha G S
>
> 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-271) Hive data model import fails if there exists any type of name "hive_process"
[
https://issues.apache.org/jira/browse/ATLAS-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Bergenholtz updated ATLAS-271:
---
Assignee: Erik Bergenholtz
> Hive data model import fails if there exists any type of name "hive_process"
>
>
> Key: ATLAS-271
> URL: https://issues.apache.org/jira/browse/ATLAS-271
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.6-incubating
>Reporter: Ayub Khan
>Assignee: Erik Bergenholtz
>
> Hive data model import fails if there exists a type of name "hive_process"
> 1. Create a trait with typename as hive_process.
> For example:
> {noformat}
> curl 'http://localhost:21000/api/atlas/types' -H 'Origin:
> http://localhost:21000' -H 'Content-Type: application/json;charset=UTF-8'
> --data-binary
> '{"enumTypes":[],"traitTypes":[{"superTypes":[],"typeName":"hive_process","attributeDefinitions":[],"hierarchicalMetaTypeName":"org.apache.atlas.typesystem.types.TraitType"}],"structTypes":[],"classTypes":[]}'
> --compressed
> {noformat}
> 2. Now run import_hive.sh
> Import hive data model fails because atlas thinks that hive data model is
> already registered.
> This issue is quite possible when the user/admin(mostly unaware of hive data
> model and its types) is creating tags while bringing atlas.
> hive data model is just an example, this issue can happen with any data model.
> One solution might be to restrict creating types with reserved keywords.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-271) Hive data model import fails if there exists any type of name "hive_process"
[
https://issues.apache.org/jira/browse/ATLAS-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Bergenholtz updated ATLAS-271:
---
Affects Version/s: (was: 0.6-incubating)
0.5-incubating
> Hive data model import fails if there exists any type of name "hive_process"
>
>
> Key: ATLAS-271
> URL: https://issues.apache.org/jira/browse/ATLAS-271
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.5-incubating
>Reporter: Ayub Khan
>Assignee: Erik Bergenholtz
>
> Hive data model import fails if there exists a type of name "hive_process"
> 1. Create a trait with typename as hive_process.
> For example:
> {noformat}
> curl 'http://localhost:21000/api/atlas/types' -H 'Origin:
> http://localhost:21000' -H 'Content-Type: application/json;charset=UTF-8'
> --data-binary
> '{"enumTypes":[],"traitTypes":[{"superTypes":[],"typeName":"hive_process","attributeDefinitions":[],"hierarchicalMetaTypeName":"org.apache.atlas.typesystem.types.TraitType"}],"structTypes":[],"classTypes":[]}'
> --compressed
> {noformat}
> 2. Now run import_hive.sh
> Import hive data model fails because atlas thinks that hive data model is
> already registered.
> This issue is quite possible when the user/admin(mostly unaware of hive data
> model and its types) is creating tags while bringing atlas.
> hive data model is just an example, this issue can happen with any data model.
> One solution might be to restrict creating types with reserved keywords.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ATLAS-271) Hive data model import fails if there exists any type of name "hive_process"
[
https://issues.apache.org/jira/browse/ATLAS-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14985103#comment-14985103
]
Erik Bergenholtz commented on ATLAS-271:
if a type definition already exists and a user wants to remove the definition,
is it possible to do this today in 0.5?
IOW, what would the work around be?
> Hive data model import fails if there exists any type of name "hive_process"
>
>
> Key: ATLAS-271
> URL: https://issues.apache.org/jira/browse/ATLAS-271
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.5-incubating
>Reporter: Ayub Khan
>Assignee: Erik Bergenholtz
>
> Hive data model import fails if there exists a type of name "hive_process"
> 1. Create a trait with typename as hive_process.
> For example:
> {noformat}
> curl 'http://localhost:21000/api/atlas/types' -H 'Origin:
> http://localhost:21000' -H 'Content-Type: application/json;charset=UTF-8'
> --data-binary
> '{"enumTypes":[],"traitTypes":[{"superTypes":[],"typeName":"hive_process","attributeDefinitions":[],"hierarchicalMetaTypeName":"org.apache.atlas.typesystem.types.TraitType"}],"structTypes":[],"classTypes":[]}'
> --compressed
> {noformat}
> 2. Now run import_hive.sh
> Import hive data model fails because atlas thinks that hive data model is
> already registered.
> This issue is quite possible when the user/admin(mostly unaware of hive data
> model and its types) is creating tags while bringing atlas.
> hive data model is just an example, this issue can happen with any data model.
> One solution might be to restrict creating types with reserved keywords.
--
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-219-ATLAS-214_v9.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-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-277) i want to take help migration issue with myfaces 1.1.5 which moves from weblogic server 10.3 to weblogic server 12 c
[
https://issues.apache.org/jira/browse/ATLAS-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14986655#comment-14986655
]
Vivekanand Raghuwanshi commented on ATLAS-277:
--
ERROR [[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default
(self-tuning)'] PhaseListenerManager:77 - Exception in PhaseListener
APPLY_REQUEST_VALUES(2) beforePhase.
javax.faces.el.EvaluationException: //opt/.(PATH OF HTML
COMPONENT)XYZ.xhtml @39,77 actionListener="#{ABC.saveActionListener}":
java.lang.NullPointerException
at
com.sun.facelets.el.LegacyMethodBinding.invoke(LegacyMethodBinding.java:73)
at javax.faces.component.UICommand.broadcast(UICommand.java:89)
at
javax.faces.component.UIViewRoot._broadcastForPhase(UIViewRoot.java:97)
at
javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:171)
at
com.jdsu.faces.ajax.AjaxPhaseListener.partialInvokeApplication(AjaxPhaseListener.java:289)
at
com.jdsu.faces.ajax.AjaxPhaseListener.beforePhase(AjaxPhaseListener.java:125)
at
org.apache.myfaces.lifecycle.PhaseListenerManager.informPhaseListenersBefore(PhaseListenerManager.java:73)
at
org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:85)
at
org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:70)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:139)
at
weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:280)
at
weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:254)
at
weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:136)
at
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:341)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:25)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at
org.apache.shale.faces.ShaleApplicationFilter.doFilter(ShaleApplicationFilter.java:275)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at
org.springframework.orm.hibernate3.support.OpenSessionInViewFilter.doFilterInternal(OpenSessionInViewFilter.java:198)
at
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at
org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:147)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at
org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:378)
at
org.springframework.security.intercept.web.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:109)
at
org.springframework.security.intercept.web.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:83)
at
org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390)
at
org.springframework.security.ui.ExceptionTranslationFilter.doFilterHttp(ExceptionTranslationFilter.java:101)
at
org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53)
at
org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390)
at
com.jdsu.security.web.JdsuDaoClientCSPFilter.doFilter(JdsuDaoClientCSPFilter.java:191)
at
org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390)
at
org.springframework.security.context.HttpSessionContextIntegrationFilter.doFilterHttp(HttpSessionContextIntegrationFilter.java:235)
at
org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53)
at
org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390)
at
org.springframework.security.util.FilterChainProxy.doFilter(FilterChainProxy.java:175)
at
org.springframework.security.util.FilterToBeanProxy.doFilter(FilterToBeanProxy.java:99)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at
com.att.security.web.servlet.filters.CSPCookieFilter.doFilter(CSPCookieFilter.java:641)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at
weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3367)
at
[jira] [Commented] (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:comment-tabpanel=1498#comment-1498 ] Ayub Khan commented on ATLAS-214: - [~Anilg] I can't see any hive table on the staging server mentioned above. http://162.212.133.190:3172/#!/search?query=hive_table > 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] [Comment Edited] (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:comment-tabpanel=1498#comment-1498 ] Ayub Khan edited comment on ATLAS-214 at 11/3/15 4:32 AM: -- [~Anilg] I can't see any hive table on the staging server mentioned above. http://162.212.133.190:3172/#!/search?query=hive_table This issue is specific to hive_tables, not generic tables. was (Author: ayubkhan): [~Anilg] I can't see any hive table on the staging server mentioned above. http://162.212.133.190:3172/#!/search?query=hive_table > 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-277) i want to take help migration issue with myfaces 1.1.5 which moves from weblogic server 10.3 to weblogic server 12 c
[ https://issues.apache.org/jira/browse/ATLAS-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14986680#comment-14986680 ] Vivekanand Raghuwanshi commented on ATLAS-277: -- Erik Bergenholtz please share link where to post my issue > i want to take help migration issue with myfaces 1.1.5 which moves from > weblogic server 10.3 to weblogic server 12 c > > > Key: ATLAS-277 > URL: https://issues.apache.org/jira/browse/ATLAS-277 > Project: Atlas > Issue Type: Bug >Reporter: Vivekanand Raghuwanshi > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Build Failing
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/target/node_tmp/node.tar.gz': EOFException -> [Help 1] Can anyone suggest workaroud for this ? Thanks, Rishabh.
[jira] [Commented] (ATLAS-277) i want to take help migration issue with myfaces 1.1.5 which moves from weblogic server 10.3 to weblogic server 12 c
[ https://issues.apache.org/jira/browse/ATLAS-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14986603#comment-14986603 ] Erik Bergenholtz commented on ATLAS-277: This appears to be filed under the wrong project. Closing as invalid. Please file Jira with the correct Apache component. > i want to take help migration issue with myfaces 1.1.5 which moves from > weblogic server 10.3 to weblogic server 12 c > > > Key: ATLAS-277 > URL: https://issues.apache.org/jira/browse/ATLAS-277 > Project: Atlas > Issue Type: Bug >Reporter: Vivekanand Raghuwanshi > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-277) i want to take help migration issue with myfaces 1.1.5 which moves from weblogic server 10.3 to weblogic server 12 c
[ https://issues.apache.org/jira/browse/ATLAS-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik Bergenholtz resolved ATLAS-277. Resolution: Invalid > i want to take help migration issue with myfaces 1.1.5 which moves from > weblogic server 10.3 to weblogic server 12 c > > > Key: ATLAS-277 > URL: https://issues.apache.org/jira/browse/ATLAS-277 > Project: Atlas > Issue Type: Bug >Reporter: Vivekanand Raghuwanshi > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
