[jira] [Updated] (ATLAS-1876) Import/Export : AtlasSchemaViolationException during Import of entity associated to a tag with tag attribute value of datatype float
[
https://issues.apache.org/jira/browse/ATLAS-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharmadha Sainath updated ATLAS-1876:
-
Description:
1.In cluster1, created a tag float_tag with attribute float_max of datatype
float.
2. In the same cluster , created table table1 and associated the tag float_tag
to table1 , with attribute value for float_max as 3.4028235e+38 (maximum value
for float).
3.Creation and tag association are successful.
4.Created table1.zip by using Export API
5. Using Import API , tried to import table1.zip to cluster2. Import failed
with
{code}
{"errorCode":"ATLAS-500-00-001","errorMessage":"org.apache.atlas.exception.AtlasBaseException:
org.apache.atlas.repository.graphdb.AtlasSchemaViolationException:
com.thinkaurelius.titan.core.SchemaViolationException: Value [3.4028235E38] is
not an instance of the expected data type for property key
[float_tag.float_max] and cannot be converted. Expected: class java.lang.Float,
found: class java.lang.Double"}
{code}
Attached the error stack trace found in cluster2 application logs.
This exception is seen only when the value for float attribute is given as
3.4028235e+38 . Other values like 0 , 2.5 , 1.4e+10 etc., are accepted and
import is done successfully.
was:
1.In cluster1, created a tag float_tag with attribute float_max of datatype
float.
2. In the same cluster , created table table1 and associated the tag float_tag
to table1 , with attribute value for float_max as 3.4028235e+38 (maximum value
for float).
3.Creation and tag association are successful.
4.Created table1.zip by using Export API
5. Using Import API , tried to import table1.zip to cluster2. Import failed
with
{code}
{"errorCode":"ATLAS-500-00-001","errorMessage":"org.apache.atlas.exception.AtlasBaseException:
org.apache.atlas.repository.graphdb.AtlasSchemaViolationException:
com.thinkaurelius.titan.core.SchemaViolationException: Value [3.4028235E38] is
not an instance of the expected data type for property key
[float_tag.float_max] and cannot be converted. Expected: class java.lang.Float,
found: class java.lang.Double"}
{code}
Attached the error stack trace found in cluster2 application logs.
> Import/Export : AtlasSchemaViolationException during Import of entity
> associated to a tag with tag attribute value of datatype float
>
>
> Key: ATLAS-1876
> URL: https://issues.apache.org/jira/browse/ATLAS-1876
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
> Attachments: AtlasSchemaViolationException_ExportImport.txt
>
>
> 1.In cluster1, created a tag float_tag with attribute float_max of datatype
> float.
> 2. In the same cluster , created table table1 and associated the tag
> float_tag to table1 , with attribute value for float_max as 3.4028235e+38
> (maximum value for float).
> 3.Creation and tag association are successful.
> 4.Created table1.zip by using Export API
> 5. Using Import API , tried to import table1.zip to cluster2. Import failed
> with
> {code}
> {"errorCode":"ATLAS-500-00-001","errorMessage":"org.apache.atlas.exception.AtlasBaseException:
> org.apache.atlas.repository.graphdb.AtlasSchemaViolationException:
> com.thinkaurelius.titan.core.SchemaViolationException: Value [3.4028235E38]
> is not an instance of the expected data type for property key
> [float_tag.float_max] and cannot be converted. Expected: class
> java.lang.Float, found: class java.lang.Double"}
> {code}
> Attached the error stack trace found in cluster2 application logs.
> This exception is seen only when the value for float attribute is given as
> 3.4028235e+38 . Other values like 0 , 2.5 , 1.4e+10 etc., are accepted and
> import is done successfully.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (ATLAS-1876) Import/Export : AtlasSchemaViolationException during Import of entity associated to a tag with tag attribute value of datatype float
Sharmadha Sainath created ATLAS-1876:
Summary: Import/Export : AtlasSchemaViolationException during
Import of entity associated to a tag with tag attribute value of datatype float
Key: ATLAS-1876
URL: https://issues.apache.org/jira/browse/ATLAS-1876
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 0.9-incubating
Reporter: Sharmadha Sainath
Attachments: AtlasSchemaViolationException_ExportImport.txt
1.In cluster1, created a tag float_tag with attribute float_max of datatype
float.
2. In the same cluster , created table table1 and associated the tag float_tag
to table1 , with attribute value for float_max as 3.4028235e+38 (maximum value
for float).
3.Creation and tag association are successful.
4.Created table1.zip by using Export API
5. Using Import API , tried to import table1.zip to cluster2. Import failed
with
{code}
{"errorCode":"ATLAS-500-00-001","errorMessage":"org.apache.atlas.exception.AtlasBaseException:
org.apache.atlas.repository.graphdb.AtlasSchemaViolationException:
com.thinkaurelius.titan.core.SchemaViolationException: Value [3.4028235E38] is
not an instance of the expected data type for property key
[float_tag.float_max] and cannot be converted. Expected: class java.lang.Float,
found: class java.lang.Double"}
{code}
Attached the error stack trace found in cluster2 application logs.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (ATLAS-1826) UI Create Entity : Type doesn't list the inverseRef constrained attribute options when name length is less than 3.
Sharmadha Sainath created ATLAS-1826: Summary: UI Create Entity : Type doesn't list the inverseRef constrained attribute options when name length is less than 3. Key: ATLAS-1826 URL: https://issues.apache.org/jira/browse/ATLAS-1826 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 0.9-incubating Reporter: Sharmadha Sainath 1. Created a hbase_table h1. 2. Tried to create a hbase_column_family with hbase table as h1. Since "h1" has only 2 characters , the drop down didn't display "h1" but displayed "Please enter 1 or more characters". 3. When hbase_table name length is more than 2 , the drop down lists the name. Same happens when adding hbase_column_family with name "hf" to hbase_column. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1440) Inconsistency in DSL search of tag
[ https://issues.apache.org/jira/browse/ATLAS-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021074#comment-16021074 ] Sharmadha Sainath commented on ATLAS-1440: -- [~madhan.neethiraj] , This issue is not found in master. Associated an entity to parent tag and child tag . Both parent tag and child tag's UI and entity response are returned properly. > Inconsistency in DSL search of tag > -- > > Key: ATLAS-1440 > URL: https://issues.apache.org/jira/browse/ATLAS-1440 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-webui >Reporter: Sharmadha Sainath >Priority: Critical > Attachments: parent_tag_response.txt, parent_tag_UI.png > > > Created tags : > 1. parent_tag > 2. child_tag which has parent_tag has Parent tag > 1.Associated child_tag to the hive_table . DSL query of both child_tag and > parent tag listed entity but GET response of hive_table had only child_tag > This is reported in https://issues.apache.org/jira/browse/ATLAS-1439. > 2. Associated parent_tag also to hive_table. DSL query response of parent_tag > returns hive_table twice. But UI response is empty. > Attached the DSL query response of parent_tag and UI screenshot. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1819) V2 APIs : Entity Resource GET query with classification returns 500.
[
https://issues.apache.org/jira/browse/ATLAS-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharmadha Sainath updated ATLAS-1819:
-
Summary: V2 APIs : Entity Resource GET query with classification returns
500. (was: Entity Resource GET query with classification returns 500.)
> V2 APIs : Entity Resource GET query with classification returns 500.
>
>
> Key: ATLAS-1819
> URL: https://issues.apache.org/jira/browse/ATLAS-1819
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
> Attachments: ArrayOutOfBoundsException.txt
>
>
> 1. Created a tag tag1.
> 2. Created a table table1.
> 3. tag1 is *not associated* to table1
> The following query returns 500 Internal server error.
> {code}
> /api/atlas/v2/entity/guid//tag1
> {code}
> Exception thrown :
> java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
> Attached the complete exception trace thrown in application logs.
> 4. Now created another tag tag2 and associated table1 to tag2.
> 5. Now the same query /api/atlas/v2/entity/guid//tag1 returns
> expected error code 404.
> That is , when any tag is already associated to the entity, search for the
> unassociated tag throws 404 , else 500.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (ATLAS-1819) Entity Resource GET query with classification returns 500.
Sharmadha Sainath created ATLAS-1819:
Summary: Entity Resource GET query with classification returns 500.
Key: ATLAS-1819
URL: https://issues.apache.org/jira/browse/ATLAS-1819
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 0.9-incubating
Reporter: Sharmadha Sainath
Attachments: ArrayOutOfBoundsException.txt
1. Created a tag tag1.
2. Created a table table1.
3. tag1 is *not associated* to table1
The following query returns 500 Internal server error.
{code}
/api/atlas/v2/entity/guid//tag1
{code}
Exception thrown :
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
Attached the complete exception trace thrown in application logs.
4. Now created another tag tag2 and associated table1 to tag2.
5. Now the same query /api/atlas/v2/entity/guid//tag1 returns
expected error code 404.
That is , when any tag is already associated to the entity, search for the
unassociated tag throws 404 , else 500.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (ATLAS-1816) UI,excludeDeletedEntities : Next button in Basic query result view is not working if result query has DELETED entities
[ https://issues.apache.org/jira/browse/ATLAS-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016882#comment-16016882 ] Sharmadha Sainath commented on ATLAS-1816: -- [~sarath.ku...@gmail.com] , the bug you mentioned is tracked in [ATLAS-1817|https://issues.apache.org/jira/browse/ATLAS-1817] . > UI,excludeDeletedEntities : Next button in Basic query result view is not > working if result query has DELETED entities > -- > > Key: ATLAS-1816 > URL: https://issues.apache.org/jira/browse/ATLAS-1816 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating >Reporter: Sharmadha Sainath > > 1. Created 50 tables > 2. Deleted 5 tables which are shown in the first page of the basic query > search. > 3. Fired a basic query : type name = hive_table > 4. Page showed only 20 results. Because there were only 20 results , Next > button used to navigate to next page was disabled. > 5. Checked the "Include historical entities" check box. 25 results displayed > but still Next button was disabled. > 6. Hence even if one DELETED entity is returned in the basic query , > navigation to next table becomes impossible. > If all returned entities in the limit 25 are ACTIVE , Next button is enabled. > For example out of 150 entities , 5 entities are DELETED . Those DELETED > entities are found in 2nd page. Hence Navigation from 1st page to 2nd page is > possible . From there on , even though "Include Historical entities" is > checked and 25 results are returned for the page , next button is disabled. > [ATLAS-1815|https://issues.apache.org/jira/browse/ATLAS-1815] is one of the > reasons for this bug. > Advanced(DSL) query result window is not suffering from this issue probably > because excludeDeletedEntities parameter is not honored. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1817) UI : n+1 pages are created, even though only n*25 instances are retrieved.
Sharmadha Sainath created ATLAS-1817: Summary: UI : n+1 pages are created, even though only n*25 instances are retrieved. Key: ATLAS-1817 URL: https://issues.apache.org/jira/browse/ATLAS-1817 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: trunk, 0.9-incubating Reporter: Sharmadha Sainath 1.Created 50 tables. 2.First page showed 1-25 tables , second page 26 -50 tables . 3.Clicking Next button navigates to 3rd page with 26-50 as range with empty response. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1816) UI,excludeDeletedEntities : Next button in Basic query result view is not working if result query has DELETED entities
Sharmadha Sainath created ATLAS-1816: Summary: UI,excludeDeletedEntities : Next button in Basic query result view is not working if result query has DELETED entities Key: ATLAS-1816 URL: https://issues.apache.org/jira/browse/ATLAS-1816 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 0.9-incubating Reporter: Sharmadha Sainath 1. Created 50 tables 2. Deleted 5 tables which are shown in the first page of the basic query search. 3. Fired a basic query : type name = hive_table 4. Page showed only 20 results. Because there were only 20 results , Next button used to navigate to next page was disabled. 5. Checked the "Include historical entities" check box. 25 results displayed but still Next button was disabled. 6. Hence even if one DELETED entity is returned in the basic query , navigation to next table becomes impossible. If all returned entities in the limit 25 are ACTIVE , Next button is enabled. For example out of 150 entities , 5 entities are DELETED . Those DELETED entities are found in 2nd page. Hence Navigation from 1st page to 2nd page is possible . From there on , even though "Include Historical entities" is checked and 25 results are returned for the page , next button is disabled. [ATLAS-1815|https://issues.apache.org/jira/browse/ATLAS-1815] is one of the reasons for this bug. Advanced(DSL) query result window is not suffering from this issue probably because excludeDeletedEntities parameter is not honored. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1815) Exclude DELETED entities : Not all ACTIVE instances are returned when queried with limit 'n' even when more than 'n' ACTIVE instances are present.
Sharmadha Sainath created ATLAS-1815:
Summary: Exclude DELETED entities : Not all ACTIVE instances are
returned when queried with limit 'n' even when more than 'n' ACTIVE instances
are present.
Key: ATLAS-1815
URL: https://issues.apache.org/jira/browse/ATLAS-1815
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 0.9-incubating
Reporter: Sharmadha Sainath
Priority: Critical
"excludeDeletedEntities" filter is made after the response is returned, which
produces unexpected results when limit keyword is used like in the following
case :
1.Started fresh instance of Atlas and created 50 hive_tables
2. Made a basic search query , type name = hive_table which returned 50 tables
in 2 pages in UI.
Query fired :
{code}
/api/atlas/v2/search/basic?limit=25&excludeDeletedEntities=true&typeName=hive_table
{code}
3.Dropped the five tables which were shown as the first five results in the
first page of basic search query results.
4. Made the same basic query again (type name = hive_table) .
5.Expected that 25 ACTIVE results would come up in the first page of UI. But
only 20 results were displayed in the UI.
6. When "Include historical Entities" is checked , result table showed 20
ACTIVE tables and 5 DELETED tables.
This happens because , probably when
"limit=25&excludeDeletedEntities=true&typeName=hive_table" is fired ,
first 25 results are returned (irrespective of ACTIVE or DELETED) and
excludeDeletedEntities=true filter is applied which results in only 20 results.
User would expect 25 tables to be returned in the UI since there are 45 ACTIVE
tables but UI shows only 20 ACTIVE instances because of the
"excludeDeletedEntities=true" filter.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (ATLAS-1811) UI : Audit Events are not shown in sorted order based on time sometimes.
[ https://issues.apache.org/jira/browse/ATLAS-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharmadha Sainath updated ATLAS-1811: - Summary: UI : Audit Events are not shown in sorted order based on time sometimes. (was: UI : Audit Events are not shown in sorted based on time sometimes.) > UI : Audit Events are not shown in sorted order based on time sometimes. > > > Key: ATLAS-1811 > URL: https://issues.apache.org/jira/browse/ATLAS-1811 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: trunk, 0.9-incubating >Reporter: Sharmadha Sainath > Attachments: AuditDetailsUnordered.png > > > Created an entity and made did many tag association , dis-association and tag > update to that entity. All audit details are captured but not displayed in > sorted order based on timestamp value present in audit response. A few > entries are missing order. > Attached the screenshot . -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1811) UI : Audit Events are not shown in sorted based on time sometimes.
Sharmadha Sainath created ATLAS-1811: Summary: UI : Audit Events are not shown in sorted based on time sometimes. Key: ATLAS-1811 URL: https://issues.apache.org/jira/browse/ATLAS-1811 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: trunk, 0.9-incubating Reporter: Sharmadha Sainath Attachments: AuditDetailsUnordered.png Created an entity and made did many tag association , dis-association and tag update to that entity. All audit details are captured but not displayed in sorted order based on timestamp value present in audit response. A few entries are missing order. Attached the screenshot . -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1810) UI : Audit details of any tag event (Added,Updated) has only tag name and event.
Sharmadha Sainath created ATLAS-1810: Summary: UI : Audit details of any tag event (Added,Updated) has only tag name and event. Key: ATLAS-1810 URL: https://issues.apache.org/jira/browse/ATLAS-1810 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 0.9-incubating Reporter: Sharmadha Sainath Priority: Minor On clicking Details of Audit events like "Tag Added" , "Tag updated" in Audit tab , Details window shows only the Audit event and tag name. Tag attributes are not displayed. Since "Edit Attribute of Tag" feature is introduced, it would be good to display the attributes of tag like it does for Entities. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1809) UI : Update button in Edit tag attributes window should be enabled only when any update is done
Sharmadha Sainath created ATLAS-1809: Summary: UI : Update button in Edit tag attributes window should be enabled only when any update is done Key: ATLAS-1809 URL: https://issues.apache.org/jira/browse/ATLAS-1809 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 0.9-incubating Reporter: Sharmadha Sainath Priority: Minor Even though no update is made to any of the attributes of tag associated to entity, "Update" button is enabled in Edit Tag window . Audit is also generated with event 'Tag Updated'. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1808) UI : All selected entities are assigned to tag when Assign Tag corresponding to 1 entity is clicked.
[ https://issues.apache.org/jira/browse/ATLAS-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharmadha Sainath updated ATLAS-1808: - Description: Steps: 1. Searched for type hive_table which listed 10 results. 2. Selected all the entities (using check box). 3. Clicked on Assign tag button corresponding to the first result ex : table1 ( "+" sign button with class a.InputTagAdd.assignTag) 4. Selected the tag to be assigned ex:tag1 5. Expected tag1 would be assigned to only table1 though all the entities are selected. But all the entities are assigned to tag1. Note : Didn't click on Button with text " + Assign Tag" (class : a.inputAssignTag.multiSelectTag.assignTag.btnAssign) after selecting multiple entities. was: Steps: 1. Searched for type hive_table which listed 10 results. 2. Selected all the entities (using check box). 3. Clicked on Assign tag button corresponding to the first result ex : table1 ( "+" sign button with class a.InputTagAdd.assignTag) 4. Selected the tag to be assigned ex:tag1 5. Expected tag1 would be assigned to only table1 though all the entities are selected. But all the entities are assigned to tag1. Note : Didn't click on Button with text " + Assign Tag" (class : a.inputAssignTag multiSelectTag.assignTag.btnAssign) after selecting multiple entities. > UI : All selected entities are assigned to tag when Assign Tag corresponding > to 1 entity is clicked. > > > Key: ATLAS-1808 > URL: https://issues.apache.org/jira/browse/ATLAS-1808 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.8-incubating, 0.9-incubating >Reporter: Sharmadha Sainath > > Steps: > 1. Searched for type hive_table which listed 10 results. > 2. Selected all the entities (using check box). > 3. Clicked on Assign tag button corresponding to the first result ex : table1 > ( "+" sign button with class a.InputTagAdd.assignTag) > 4. Selected the tag to be assigned ex:tag1 > 5. Expected tag1 would be assigned to only table1 though all the entities are > selected. But all the entities are assigned to tag1. > Note : Didn't click on Button with text " + Assign Tag" (class : > a.inputAssignTag.multiSelectTag.assignTag.btnAssign) after selecting multiple > entities. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1808) UI : All selected entities are assigned to tag when Assign Tag corresponding to 1 entity is clicked.
Sharmadha Sainath created ATLAS-1808: Summary: UI : All selected entities are assigned to tag when Assign Tag corresponding to 1 entity is clicked. Key: ATLAS-1808 URL: https://issues.apache.org/jira/browse/ATLAS-1808 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 0.8-incubating, 0.9-incubating Reporter: Sharmadha Sainath Steps: 1. Searched for type hive_table which listed 10 results. 2. Selected all the entities (using check box). 3. Clicked on Assign tag button corresponding to the first result ex : table1 ( "+" sign button with class a.InputTagAdd.assignTag) 4. Selected the tag to be assigned ex:tag1 5. Expected tag1 would be assigned to only table1 though all the entities are selected. But all the entities are assigned to tag1. Note : Didn't click on Button with text " + Assign Tag" (class : a.inputAssignTag multiSelectTag.assignTag.btnAssign) after selecting multiple entities. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1788) UI : Wildcard search with "?" throws exception in basic search
[
https://issues.apache.org/jira/browse/ATLAS-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16010022#comment-16010022
]
Sharmadha Sainath commented on ATLAS-1788:
--
[~sarath.ku...@gmail.com] , Yes , the REST call works perfectly like mentioned
in the description . But query made through UI throws 500 internal server error.
> UI : Wildcard search with "?" throws exception in basic search
> --
>
> Key: ATLAS-1788
> URL: https://issues.apache.org/jira/browse/ATLAS-1788
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: trunk, 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Sarath Subramanian
> Attachments: wildcard_search.txt
>
>
> Wildcard search with "?" throws 500 internal error.
> Example :
> Basic search :
> type name : kafka_topic
> query : kakfa_topic_iAEz?
> throws 500 Internal server error .
> The corresponding query fired is
> {code}
> http://172.27.19.74:21000/api/atlas/v2/search?limit=25&query=kakfa_topic_iAEz
> {code}
> if query is "kafka_topic_?AEzb"
> corresponding query fired is :
> {code}
> http://172.27.19.74:21000/api/atlas/v2/search?limit=25&query=kafka_topic_
> {code}
> Note : content after "?" is ignored and query is not formed correctly (basic
> keyword is missed)
> The following curl command runs fine returns 200 Ok with correct results.
> {code}
> curl -u admin:admin -X GET
> "http://172.27.19.74:21000/api/atlas/v2/search/basic?limit=25&excludeDeletedEntities=true&query=kakfa_topic_iAEz?&typeName=kafka_topic";
> {code}
> Attached the WebApplication exception thrown while making the query.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (ATLAS-1788) UI : Wildcard search with "?" throws exception in basic search
Sharmadha Sainath created ATLAS-1788:
Summary: UI : Wildcard search with "?" throws exception in basic
search
Key: ATLAS-1788
URL: https://issues.apache.org/jira/browse/ATLAS-1788
Project: Atlas
Issue Type: Bug
Components: atlas-webui
Affects Versions: trunk, 0.9-incubating
Reporter: Sharmadha Sainath
Attachments: wildcard_search.txt
Wildcard search with "?" throws 500 internal error.
Example :
Basic search :
type name : kafka_topic
query : kakfa_topic_iAEz?
throws 500 Internal server error .
The corresponding query fired is
{code}
http://172.27.19.74:21000/api/atlas/v2/search?limit=25&query=kakfa_topic_iAEz
{code}
if query is "kafka_topic_?AEzb"
corresponding query fired is :
{code}
http://172.27.19.74:21000/api/atlas/v2/search?limit=25&query=kafka_topic_
{code}
Note : content after "?" is ignored and query is not formed correctly (basic
keyword is missed)
The following curl command runs fine returns 200 Ok with correct results.
{code}
curl -u admin:admin -X GET
"http://172.27.19.74:21000/api/atlas/v2/search/basic?limit=25&excludeDeletedEntities=true&query=kakfa_topic_iAEz?&typeName=kafka_topic";
{code}
Attached the WebApplication exception thrown while making the query.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (ATLAS-1778) Incorrect error code returned in V2 APIs when updating an entity with invalid values using PUT/POST
Sharmadha Sainath created ATLAS-1778:
Summary: Incorrect error code returned in V2 APIs when updating an
entity with invalid values using PUT/POST
Key: ATLAS-1778
URL: https://issues.apache.org/jira/browse/ATLAS-1778
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 0.8-incubating, 0.9-incubating
Reporter: Sharmadha Sainath
Entity Update using PUT /POST with wrong values for attributes throws 404 Not
Found exception . Expected is 400 Bad Request .
{code}
curl -v -u admin:admin -H "Content-Type: application/json" -d @entity.json -X
POST
"http://ctr-e133-1493418528701-6996-01-06.hwx.site:21000/api/atlas/v2/entity";
* Trying 172.27.14.75...
* Connected to ctr-e133-1493418528701-6996-01-06.hwx.site (172.27.14.75)
port 21000 (#0)
* Server auth using Basic with user 'admin'
> POST /api/atlas/v2/entity HTTP/1.1
> Host: ctr-e133-1493418528701-6996-01-06.hwx.site:21000
> Authorization: Basic YWRtaW46YWRtaW4=
> User-Agent: curl/7.43.0
> Accept: */*
> Content-Type: application/json
> Content-Length: 937
>
* upload completely sent off: 937 out of 937 bytes
< HTTP/1.1 404 Not Found
< Date: Fri, 05 May 2017 06:09:21 GMT
< Set-Cookie: ATLASSESSIONID=1e65za9f72n3n7dcxp6bsgf2o;Path=/;HttpOnly
< Expires: Thu, 01 Jan 1970 00:00:00 GMT
< X-Frame-Options: DENY
< Content-Type: application/json; charset=UTF-8
< Transfer-Encoding: chunked
< Server: Jetty(9.2.12.v20150709)
<
* Connection #0 to host ctr-e133-1493418528701-6996-01-06.hwx.site left
intact
{"errorCode":"ATLAS-404-00-007","errorMessage":"Invalid instance
creation/updation parameters passed : entity_type_VNsAA.type_date=str: invalid
value for type date"}
{code}
*V1 APIs return 400 Bad Request*
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (ATLAS-1777) UI : Include historical entities check box is not shown when searching a type with all DELETED entities, hence no entities are retrieved by search.
Sharmadha Sainath created ATLAS-1777: Summary: UI : Include historical entities check box is not shown when searching a type with all DELETED entities, hence no entities are retrieved by search. Key: ATLAS-1777 URL: https://issues.apache.org/jira/browse/ATLAS-1777 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 0.9-incubating Reporter: Sharmadha Sainath Attachments: all_DELETED_entities.png, one_ACTIVE_entity.png 1. Created a type and 10 entities of that type. 2. Deleted 9 entities out of 10 . 3. In basic search , searched for the type which listed only one ACTIVE entity. 4. Checked the "Include historical entities" check box. It listed the 9 DELETED entities and 1 ACTIVE entity. (Attached the screenshot) 5. Now , deleted the last one ACTIVE entity of the type.(all entities of the type are now DELETED) 6. Searched for the same type again. Results were empty since excludeDeletedEntities=True is set by default. 7. Since there were no results, "Include historical entities" check box is not shown at all.(Attached the screenshot) . Hence , there is now no way of retrieving entities of the type in Basic search. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1763) UI : Atlas lands in the page of Deleted tag (the only tag) on clicking TAGS tab
Sharmadha Sainath created ATLAS-1763: Summary: UI : Atlas lands in the page of Deleted tag (the only tag) on clicking TAGS tab Key: ATLAS-1763 URL: https://issues.apache.org/jira/browse/ATLAS-1763 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 0.9-incubating Reporter: Sharmadha Sainath Assignee: Keval Bhatt Priority: Trivial 1. Created tag tag1 2. Clicked on TAGS tab which landed in http://localhost:21000/index.html#!/tag/tagAttribute/tag1 3. Deleted the tag through REST. 4. Clicked on the TAGS tab. The TAGS tab listed tag1 . But on disabling cache , tag1 is removed. 5.But Atlas lands in http://localhost:21000/index.html#!/tag/tagAttribute/tag1 which throws 404 exception while clicking Tags tab . On opening Atlas in another incognito window , this issue is not seen . Atlas possibly caches tag1 which lands in /tag/tagAttribute/tag1 and causes issue. When there are 1 or more ACTIVE tags , this issue is not seen as it lands in /tag/tagAttribute/. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1747) Difference in result of POSTing Structs to V1 APIs and V2 APIs
[
https://issues.apache.org/jira/browse/ATLAS-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15981023#comment-15981023
]
Sharmadha Sainath commented on ATLAS-1747:
--
After POSTing faulty definition with no attributeDefs for a struct to V2 APIs,
type registration is not happening properly.
1.Created a correct type of category entity after Atlas accepted faulty
definition for struct.
2.The type got created successfully.
3.But while searching the type , Atlas throws 500 Internal server error .
Unable to create entity for the type also.
Whenever new type is registered , exception attached in
struct_V2_API_200_OK.txt is thrown.
Changing priority to critical.
> Difference in result of POSTing Structs to V1 APIs and V2 APIs
> --
>
> Key: ATLAS-1747
> URL: https://issues.apache.org/jira/browse/ATLAS-1747
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.8-incubating, 0.9-incubating
>Reporter: Sharmadha Sainath
> Attachments: struct_V1_API_400_Bad_Req.txt, struct_V2_API_200_OK.txt
>
>
> Created a struct without attribute definitions.
> 1. POSTing it to V1 APIs threw 400 Bad Request with exception
> {code}
> Caused by: java.lang.IllegalArgumentException: Collection Attribute
> definitions is empty
> {code}
> 2. POSTing it to V2 APIs throws the above exception but struct is created
> successfully.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (ATLAS-1747) Difference in result of POSTing Structs to V1 APIs and V2 APIs
[
https://issues.apache.org/jira/browse/ATLAS-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharmadha Sainath updated ATLAS-1747:
-
Priority: Critical (was: Major)
> Difference in result of POSTing Structs to V1 APIs and V2 APIs
> --
>
> Key: ATLAS-1747
> URL: https://issues.apache.org/jira/browse/ATLAS-1747
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.8-incubating, 0.9-incubating
>Reporter: Sharmadha Sainath
>Priority: Critical
> Attachments: struct_V1_API_400_Bad_Req.txt, struct_V2_API_200_OK.txt
>
>
> Created a struct without attribute definitions.
> 1. POSTing it to V1 APIs threw 400 Bad Request with exception
> {code}
> Caused by: java.lang.IllegalArgumentException: Collection Attribute
> definitions is empty
> {code}
> 2. POSTing it to V2 APIs throws the above exception but struct is created
> successfully.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (ATLAS-1747) Difference in result of POSTing Structs to V1 APIs and V2 APIs
[
https://issues.apache.org/jira/browse/ATLAS-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15980783#comment-15980783
]
Sharmadha Sainath commented on ATLAS-1747:
--
Struct definition POSTed to V1 APIs:
/api/atlas/types
{code}
{
"enumTypes":[
],
"structTypes":[
{
"typeName":"struct_v1_2",
"typeDescription":null,
"typeVersion":"1.0",
"attributeDefinitions":[ ]
}
],
"traitTypes":[
],
"classTypes":[
]
}
{code}
Struct definition POSTed to V2 APIs :
/api/atlas/v2/types/typedefs
{code}
{
"entityDefs":[
],
"structDefs":[
{
"description":"new desc",
"category":"STRUCT",
"name":"type_struct_3",
"updateTime":12345,
"guid":"bfoewbfoewfibjbjbdfdsfoef",
"typeVersion":"0.1",
"attributeDefs":[],
"createTime":12345
}
],
"classificationDefs":[
],
"enumDefs":[
]
}
{code}
> Difference in result of POSTing Structs to V1 APIs and V2 APIs
> --
>
> Key: ATLAS-1747
> URL: https://issues.apache.org/jira/browse/ATLAS-1747
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.8-incubating, 0.9-incubating
>Reporter: Sharmadha Sainath
> Attachments: struct_V1_API_400_Bad_Req.txt, struct_V2_API_200_OK.txt
>
>
> Created a struct without attribute definitions.
> 1. POSTing it to V1 APIs threw 400 Bad Request with exception
> {code}
> Caused by: java.lang.IllegalArgumentException: Collection Attribute
> definitions is empty
> {code}
> 2. POSTing it to V2 APIs throws the above exception but struct is created
> successfully.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (ATLAS-1747) Difference in result of POSTing Structs to V1 APIs and V2 APIs
Sharmadha Sainath created ATLAS-1747:
Summary: Difference in result of POSTing Structs to V1 APIs and V2
APIs
Key: ATLAS-1747
URL: https://issues.apache.org/jira/browse/ATLAS-1747
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 0.8-incubating, 0.9-incubating
Reporter: Sharmadha Sainath
Attachments: struct_V1_API_400_Bad_Req.txt, struct_V2_API_200_OK.txt
Created a struct without attribute definitions.
1. POSTing it to V1 APIs threw 400 Bad Request with exception
{code}
Caused by: java.lang.IllegalArgumentException: Collection Attribute definitions
is empty
{code}
2. POSTing it to V2 APIs throws the above exception but struct is created
successfully.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (ATLAS-1743) Issue with uniqueAttribute while creation of entities
[ https://issues.apache.org/jira/browse/ATLAS-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15978552#comment-15978552 ] Sharmadha Sainath edited comment on ATLAS-1743 at 4/21/17 11:35 AM: [~ayubkhan] , Uniqueness of an asset is identified through qualified name or GUID.The REST API to create an asset acts an UPDATE when the assets already exists in atlas and CREATE when it doesn't. This is true and as per documentation http://atlas.incubator.apache.org/api/v2/resource_EntityREST.html#resource_EntityREST_createOrUpdate_POST - "Create new entity or update existing entity in Atlas. Existing entity is matched using its unique guid if supplied or by its unique attributes eg: qualifiedName" and it is working as designed . But my thought is since we have a single POST call for both create and update , more vigilant check could be done like checking the GUID also. Like if entity with GUID exists , Atlas should do an update or create if GUID doesn't exist or it is negative (starts with "-") was (Author: ssainath): [~ayubkhan] , Uniqueness of an asset is identified through qualified name or GUID.The REST API to create an asset acts an UPDATE when the assets already exists in atlas and CREATE when it doesn't. This is true and as per documentation http://atlas.incubator.apache.org/api/v2/resource_EntityREST.html#resource_EntityREST_createOrUpdate_POST - "Create new entity or update existing entity in Atlas. Existing entity is matched using its unique guid if supplied or by its unique attributes eg: qualifiedName" and it is working as designed . But my thought is since we have a single POST call for both create and update , more vigilant check could be done like checking the GUID also. Like if entity with GUID exists , Atlas should do an update or create. > Issue with uniqueAttribute while creation of entities > - > > Key: ATLAS-1743 > URL: https://issues.apache.org/jira/browse/ATLAS-1743 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8-incubating, 0.9-incubating >Reporter: Sharmadha Sainath > > Atlas allows creation of entities with same value for unique attributes. > For example , > 1. Created an hdfs_path entity with > * name = dir1 > * qualifiedName = "userdir@cl1" > * path = /user/user1/dir > Entity is created successfully. > 2. Created another hdfs_path entity with > * name = dir2 > * qualifiedName = "userdir@cl1" > * path = /user/user2/dir > Qualified Name is uniqueAttribute and entity creation with same Qualified > Name is allowed. > Problem is when the 2nd hdfs_path entity is created , 1st entity is updated > with 2nd entity's values , hence 2nd entity creation is merely an update call > here instead of a create call because of same unique attribute. > There is no condition to check uniqueness of attributes while creation of > entities which is causing the problem. > If 1st hdfs_path entity is DELETED , then 2nd hdfs_path entity POST call > creates new entity. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1743) Issue with uniqueAttribute while creation of entities
[ https://issues.apache.org/jira/browse/ATLAS-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15978552#comment-15978552 ] Sharmadha Sainath commented on ATLAS-1743: -- [~ayubkhan] , Uniqueness of an asset is identified through qualified name or GUID.The REST API to create an asset acts an UPDATE when the assets already exists in atlas and CREATE when it doesn't. This is true and as per documentation http://atlas.incubator.apache.org/api/v2/resource_EntityREST.html#resource_EntityREST_createOrUpdate_POST - "Create new entity or update existing entity in Atlas. Existing entity is matched using its unique guid if supplied or by its unique attributes eg: qualifiedName" and it is working as designed . But my thought is since we have a single POST call for both create and update , more vigilant check could be done like checking the GUID also. Like if entity with GUID exists , Atlas should do an update or create. > Issue with uniqueAttribute while creation of entities > - > > Key: ATLAS-1743 > URL: https://issues.apache.org/jira/browse/ATLAS-1743 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8-incubating, 0.9-incubating >Reporter: Sharmadha Sainath > > Atlas allows creation of entities with same value for unique attributes. > For example , > 1. Created an hdfs_path entity with > * name = dir1 > * qualifiedName = "userdir@cl1" > * path = /user/user1/dir > Entity is created successfully. > 2. Created another hdfs_path entity with > * name = dir2 > * qualifiedName = "userdir@cl1" > * path = /user/user2/dir > Qualified Name is uniqueAttribute and entity creation with same Qualified > Name is allowed. > Problem is when the 2nd hdfs_path entity is created , 1st entity is updated > with 2nd entity's values , hence 2nd entity creation is merely an update call > here instead of a create call because of same unique attribute. > There is no condition to check uniqueness of attributes while creation of > entities which is causing the problem. > If 1st hdfs_path entity is DELETED , then 2nd hdfs_path entity POST call > creates new entity. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1744) Error when searching type with attribute name "order" , "limit" , "offset"
Sharmadha Sainath created ATLAS-1744:
Summary: Error when searching type with attribute name "order" ,
"limit" , "offset"
Key: ATLAS-1744
URL: https://issues.apache.org/jira/browse/ATLAS-1744
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 0.8-incubating, 0.9-incubating
Reporter: Sharmadha Sainath
Attachments: OrderSearchError.txt
1.Created a type with attributes "order", "limit", "offset"
2.Created an entity for the type.
3.Searched
type where order="random"
which threw 500 internal server error with error notification
{code}
Discovery query failed type_entity where order ="random"
{code}.
Same exception when searching type with name "limit" and "offset"
type where limit="upper"
type where offset="middle"
Attached the complete exception stack trace .
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (ATLAS-1743) Issue with uniqueAttribute while creation of entities
Sharmadha Sainath created ATLAS-1743: Summary: Issue with uniqueAttribute while creation of entities Key: ATLAS-1743 URL: https://issues.apache.org/jira/browse/ATLAS-1743 Project: Atlas Issue Type: Bug Components: atlas-core Affects Versions: 0.8-incubating, 0.9-incubating Reporter: Sharmadha Sainath Atlas allows creation of entities with same value for unique attributes. For example , 1. Created an hdfs_path entity with * name = dir1 * qualifiedName = "userdir@cl1" * path = /user/user1/dir Entity is created successfully. 2. Created another hdfs_path entity with * name = dir2 * qualifiedName = "userdir@cl1" * path = /user/user2/dir Qualified Name is uniqueAttribute and entity creation with same Qualified Name is allowed. Problem is when the 2nd hdfs_path entity is created , 1st entity is updated with 2nd entity's values , hence 2nd entity creation is merely an update call here instead of a create call because of same unique attribute. There is no condition to check uniqueness of attributes while creation of entities which is causing the problem. If 1st hdfs_path entity is DELETED , then 2nd hdfs_path entity POST call creates new entity. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1736) Type registration becomes inconsistent after creating a type with attribute name having special characters.
Sharmadha Sainath created ATLAS-1736: Summary: Type registration becomes inconsistent after creating a type with attribute name having special characters. Key: ATLAS-1736 URL: https://issues.apache.org/jira/browse/ATLAS-1736 Project: Atlas Issue Type: Bug Components: atlas-core Affects Versions: 0.8-incubating, 0.9-incubating Reporter: Sharmadha Sainath Priority: Critical Attachments: SplCharInAttrName.txt Created a type with attribute name as "attribute$" (with special character $). 1.Type creation succeeded with 200 OK 2.Null Pointer exception is seen in application logs 3.Searching the type throws 500 Internal server error though the drop down lists the type. 4. After creating such type , subsequent type creations are inconsistent. (i.e) Type creation succeeds but Null pointer exception is thrown and 500 Internal server error while searching the type. Attached the exception stack trace. This issue is similar to https://issues.apache.org/jira/browse/ATLAS-1681. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1731) Regression : 2 CTAS hive tables are created when issuing 1 CTAS create command.
Sharmadha Sainath created ATLAS-1731:
Summary: Regression : 2 CTAS hive tables are created when issuing
1 CTAS create command.
Key: ATLAS-1731
URL: https://issues.apache.org/jira/browse/ATLAS-1731
Project: Atlas
Issue Type: Bug
Components: atlas-intg
Affects Versions: 0.9-incubating
Reporter: Sharmadha Sainath
Priority: Critical
Attachments: ctas_table_exception.txt
1. Created table table1.
2. Created table table1ctas as select * from table1
3. 2 CTAS tables are created with same name and qualified name. One table has
lineage and other doesn't.
No exception is thrown while creating the tables. When clicking on the extra
CTAS table , i.e , while making /api/atlas/v2/entity/guid/{guid} call , Null
Pointer Exception is thrown. Attached the exception stack trace.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (ATLAS-1729) Atlas is not allowing deletion of type with no ACTIVE instances and no other types that refer this type.
[
https://issues.apache.org/jira/browse/ATLAS-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharmadha Sainath updated ATLAS-1729:
-
Description:
1. Created a type
2. Created entity for the type.
3. Tried to delete the type using
{code}
/api/atlas/v2/types/typedefs
{code}
which failed with 409 Conflict
{code}
{"errorCode":"ATLAS-409-00-002","errorMessage":"Given type testType has
references"}
{code}
4.Deleted the entity created for the type . status of the entity is DELETED.
5. Issued the same delete request for the type again . Even though there are no
ACTIVE instances for the type and no other type has reference to this type,
type deletion is failing with the same exception.
This might cause issues when user wants to delete the type and recreate type
with same name.
was:
1. Created a type
2. Created entity for the type.
3. Tried to delete the type using
{code}
/api/atlas/v2/types/typedefs
{code}
which failed with 409 Conflict
{code}
{"errorCode":"ATLAS-409-00-002","errorMessage":"Given type testType has
references"}
{code}
4.Deleted the entity created for the type . status of the entity is DELETED.
5. Issued the same delete request again . Even though there are no ACTIVE
instances for the type and no other type has reference to this type, type
deletion is failing with the same exception.
This might cause issues when user wants to delete the type and recreate type
with same name.
> Atlas is not allowing deletion of type with no ACTIVE instances and no other
> types that refer this type.
>
>
> Key: ATLAS-1729
> URL: https://issues.apache.org/jira/browse/ATLAS-1729
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.8-incubating, 0.9-incubating
>Reporter: Sharmadha Sainath
>
> 1. Created a type
> 2. Created entity for the type.
> 3. Tried to delete the type using
> {code}
> /api/atlas/v2/types/typedefs
> {code}
> which failed with 409 Conflict
> {code}
> {"errorCode":"ATLAS-409-00-002","errorMessage":"Given type testType has
> references"}
> {code}
> 4.Deleted the entity created for the type . status of the entity is DELETED.
> 5. Issued the same delete request for the type again . Even though there are
> no ACTIVE instances for the type and no other type has reference to this
> type, type deletion is failing with the same exception.
> This might cause issues when user wants to delete the type and recreate type
> with same name.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (ATLAS-1730) Error after updating attribute's data type of an Atlas type
Sharmadha Sainath created ATLAS-1730:
Summary: Error after updating attribute's data type of an Atlas
type
Key: ATLAS-1730
URL: https://issues.apache.org/jira/browse/ATLAS-1730
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 0.8-incubating, 0.9-incubating
Reporter: Sharmadha Sainath
1.Created a type with one of its attributes' type as date and POSTed the type
definition to
{code}
/api/atlas/v2/types/typedefs
{code}
2. Tried to update the attribute data type to string , hence modified the JSON
(changed "date" to "string") and PUT the JSON to the same API which succeeded.
3. Tried to create an entity of the type and provided "val1" as value for the
string attribute (which was updated from date).
4. Entity creation failed with
{code}
java.lang.ClassCastException: java.lang.Long cannot be cast to java.lang.String
{code}
This could be a rare one but this scenario might cause issues when user
initially gave data type as "date" by mistake and wants to update it as
"string".
Also , since attribute delete is not allowed as part of type update , attribute
with "date" type can't be deleted and recreated with string.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (ATLAS-1728) Type deletion is allowed even when instance of the type exists.
[
https://issues.apache.org/jira/browse/ATLAS-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharmadha Sainath resolved ATLAS-1728.
--
Resolution: Resolved
Resolved in the master as part of
https://issues.apache.org/jira/browse/ATLAS-1673.
> Type deletion is allowed even when instance of the type exists.
> ---
>
> Key: ATLAS-1728
> URL: https://issues.apache.org/jira/browse/ATLAS-1728
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.8-incubating, 0.9-incubating
>Reporter: Sharmadha Sainath
>
> 1.Created a type
> 2.Created instance of the type.
> 3.Deleted the type - Succeeded with 204
> 4.The instance still exists after deletion with ACTIVE status . The entity
> definition has only the attributes removed and able to search and find the
> entity using Basic search
> Entity def of entity of deleted type :
> {code}
> {
>referredEntities:{
>},
>entity:{
> typeName:"deltype",
> guid:"cfc08f54-6d4b-4e46-800b-2cecd0b68140",
> status:"ACTIVE",
> createdBy:"admin",
> updatedBy:"admin",
> createTime:1491816571151,
> updateTime:1491816571151,
> version:0,
> classifications:[
> ]
>}
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (ATLAS-1729) Atlas is not allowing deletion of type with no ACTIVE instances and no other types that refer this type.
Sharmadha Sainath created ATLAS-1729:
Summary: Atlas is not allowing deletion of type with no ACTIVE
instances and no other types that refer this type.
Key: ATLAS-1729
URL: https://issues.apache.org/jira/browse/ATLAS-1729
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 0.8-incubating, 0.9-incubating
Reporter: Sharmadha Sainath
1. Created a type
2. Created entity for the type.
3. Tried to delete the type using
{code}
/api/atlas/v2/types/typedefs
{code}
which failed with 409 Conflict
{code}
{"errorCode":"ATLAS-409-00-002","errorMessage":"Given type testType has
references"}
{code}
4.Deleted the entity created for the type . status of the entity is DELETED.
5. Issued the same delete request again . Even though there are no ACTIVE
instances for the type and no other type has reference to this type, type
deletion is failing with the same exception.
This might cause issues when user wants to delete the type and recreate type
with same name.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (ATLAS-1728) Type deletion is allowed even when instance of the type exists.
[
https://issues.apache.org/jira/browse/ATLAS-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15962673#comment-15962673
]
Sharmadha Sainath edited comment on ATLAS-1728 at 4/10/17 10:03 AM:
[~sababaig]
Created type by POSTing following JSON to api/atlas/v2/types/typedefs
{code}
{
"structDefs":[
],
"entityDefs":[
{
"description":"description",
"category":"ENTITY",
"name":"delete_type",
"updateTime":12345,
"typeVersion":"0.1",
"attributeDefs":[
{
"name":"name",
"isOptional":false,
"isUnique":true,
"isIndexable":false,
"typeName":"string",
"valuesMaxCount":1,
"cardinality":"SINGLE",
"valuesMinCount":0
}
],
"version":12345,
"guid":"0975fubdbiuudubnjbi89jbksi909jnd",
"createTime":12345
}
],
"classificationDefs":[
],
"enumDefs":[
]
}
{code}
Deleted the type by sending the same JSON to same API.
Reference :
http://atlas.incubator.apache.org/api/v2/resource_TypesREST.html#resource_TypesREST_deleteAtlasTypeDefs_DELETE
was (Author: ssainath):
[~sababaig]
Created type by POSTing following JSON to api/atlas/v2/types/typedefs
{code}
{
"structDefs":[
],
"entityDefs":[
{
"description":"description",
"category":"ENTITY",
"name":"delete_type",
"updateTime":12345,
"typeVersion":"0.1",
"attributeDefs":[
{
"name":"name",
"isOptional":false,
"isUnique":true,
"isIndexable":false,
"typeName":"string",
"valuesMaxCount":1,
"cardinality":"SINGLE",
"valuesMinCount":0
}
],
"version":12345,
"guid":"0975fubdbiuudubnjbi89jbksi909jnd",
"createTime":12345
}
],
"classificationDefs":[
],
"enumDefs":[
]
}
{code}
Deleted the type by POSTing the same JSON to same API.
Reference :
http://atlas.incubator.apache.org/api/v2/resource_TypesREST.html#resource_TypesREST_deleteAtlasTypeDefs_DELETE
> Type deletion is allowed even when instance of the type exists.
> ---
>
> Key: ATLAS-1728
> URL: https://issues.apache.org/jira/browse/ATLAS-1728
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.8-incubating, 0.9-incubating
>Reporter: Sharmadha Sainath
>
> 1.Created a type
> 2.Created instance of the type.
> 3.Deleted the type - Succeeded with 204
> 4.The instance still exists after deletion with ACTIVE status . The entity
> definition has only the attributes removed and able to search and find the
> entity using Basic search
> Entity def of entity of deleted type :
> {code}
> {
>referredEntities:{
>},
>entity:{
> typeName:"deltype",
> guid:"cfc08f54-6d4b-4e46-800b-2cecd0b68140",
> status:"ACTIVE",
> createdBy:"admin",
> updatedBy:"admin",
> createTime:1491816571151,
> updateTime:1491816571151,
> version:0,
> classifications:[
> ]
>}
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (ATLAS-1728) Type deletion is allowed even when instance of the type exists.
[
https://issues.apache.org/jira/browse/ATLAS-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15962673#comment-15962673
]
Sharmadha Sainath commented on ATLAS-1728:
--
[~sababaig]
Created type by POSTing following JSON to api/atlas/v2/types/typedefs
{code}
{
"structDefs":[
],
"entityDefs":[
{
"description":"description",
"category":"ENTITY",
"name":"delete_type",
"updateTime":12345,
"typeVersion":"0.1",
"attributeDefs":[
{
"name":"name",
"isOptional":false,
"isUnique":true,
"isIndexable":false,
"typeName":"string",
"valuesMaxCount":1,
"cardinality":"SINGLE",
"valuesMinCount":0
}
],
"version":12345,
"guid":"0975fubdbiuudubnjbi89jbksi909jnd",
"createTime":12345
}
],
"classificationDefs":[
],
"enumDefs":[
]
}
{code}
Deleted the type by POSTing the same JSON to same API.
Reference :
http://atlas.incubator.apache.org/api/v2/resource_TypesREST.html#resource_TypesREST_deleteAtlasTypeDefs_DELETE
> Type deletion is allowed even when instance of the type exists.
> ---
>
> Key: ATLAS-1728
> URL: https://issues.apache.org/jira/browse/ATLAS-1728
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.8-incubating, 0.9-incubating
>Reporter: Sharmadha Sainath
>
> 1.Created a type
> 2.Created instance of the type.
> 3.Deleted the type - Succeeded with 204
> 4.The instance still exists after deletion with ACTIVE status . The entity
> definition has only the attributes removed and able to search and find the
> entity using Basic search
> Entity def of entity of deleted type :
> {code}
> {
>referredEntities:{
>},
>entity:{
> typeName:"deltype",
> guid:"cfc08f54-6d4b-4e46-800b-2cecd0b68140",
> status:"ACTIVE",
> createdBy:"admin",
> updatedBy:"admin",
> createTime:1491816571151,
> updateTime:1491816571151,
> version:0,
> classifications:[
> ]
>}
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (ATLAS-1728) Type deletion is allowed even when instance of the type exists.
Sharmadha Sainath created ATLAS-1728:
Summary: Type deletion is allowed even when instance of the type
exists.
Key: ATLAS-1728
URL: https://issues.apache.org/jira/browse/ATLAS-1728
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 0.8-incubating, 0.9-incubating
Reporter: Sharmadha Sainath
1.Created a type
2.Created instance of the type.
3.Deleted the type - Succeeded with 204
4.The instance still exists after deletion with ACTIVE status . The entity
definition has only the attributes removed and able to search and find the
entity using Basic search
Entity def of entity of deleted type :
{code}
{
referredEntities:{
},
entity:{
typeName:"deltype",
guid:"cfc08f54-6d4b-4e46-800b-2cecd0b68140",
status:"ACTIVE",
createdBy:"admin",
updatedBy:"admin",
createTime:1491816571151,
updateTime:1491816571151,
version:0,
classifications:[
]
}
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (ATLAS-1726) Creating type name with space causes exceptions while doing DSL search
Sharmadha Sainath created ATLAS-1726:
Summary: Creating type name with space causes exceptions while
doing DSL search
Key: ATLAS-1726
URL: https://issues.apache.org/jira/browse/ATLAS-1726
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 0.8-incubating, 0.9-incubating
Reporter: Sharmadha Sainath
1.Created a type "type 1" successfully
2.Searched the type "type 1" in Basic search which worked fine.
3.Same type when selected in drop down list of types in DSL , failed with 500
internal server error with exception :
{code}
org.apache.atlas.query.Expressions$UnresolvedException: Unresolved datatype.
Can not resolve due to unresolved children, expression: type where 1
{code}
4. If typename is provided as `type 1` in "Search by Query" text box (with
backquotes) like mentioned in https://issues.apache.org/jira/browse/ATLAS-263 ,
it works fine.
User might perceive that the type is not registered properly due to the
exception.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (ATLAS-1714) UI : Properties tab doesn't load when an entity has attribute of type array of integers
[
https://issues.apache.org/jira/browse/ATLAS-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharmadha Sainath reassigned ATLAS-1714:
Assignee: Keval Bhatt
> UI : Properties tab doesn't load when an entity has attribute of type array
> of integers
>
>
> Key: ATLAS-1714
> URL: https://issues.apache.org/jira/browse/ATLAS-1714
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>
> Created a type with array of integers as on of its attributes :
> {code}
> {
>"name":"type_set_int",
>"isOptional":true,
>"isUnique":false,
>"isIndexable":false,
>"typeName":"array",
>"valuesMaxCount":1,
>"cardinality":"SET",
>"valuesMinCount":0
> }
> {code}
> Created an entity of the type with value for type_set_int as [1,2,3]. Entity
> is created with 200 OK.
> Following exception is thrown in console tab :
> {code}
> Uncaught TypeError: inputOutputField.indexOf is not a function
> at http://172.27.16.74:21000/js/utils/CommonViewFunction.js:148:46
> at Array.map (native)
> at Object.CommonViewFunction.propertyTable
> (http://172.27.16.74:21000/js/utils/CommonViewFunction.js:129:39)
> at n.entityTableGenerate
> (http://172.27.16.74:21000/js/views/entity/EntityDetailTableLayoutView.js:68:48)
> at n.onRender
> (http://172.27.16.74:21000/js/views/entity/EntityDetailTableLayoutView.js:56:22)
> at
> http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:7823
> at n.triggerMethod
> (http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:20703)
> at n.render
> (http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:21699)
> at n.render
> (http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:30148)
> at constructor.show
> (http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:11890)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (ATLAS-1714) UI : Properties tab doesn't load when an entity has attribute of type array of integers
Sharmadha Sainath created ATLAS-1714:
Summary: UI : Properties tab doesn't load when an entity has
attribute of type array of integers
Key: ATLAS-1714
URL: https://issues.apache.org/jira/browse/ATLAS-1714
Project: Atlas
Issue Type: Bug
Components: atlas-webui
Affects Versions: 0.9-incubating
Reporter: Sharmadha Sainath
Created a type with array of integers as on of its attributes :
{code}
{
"name":"type_set_int",
"isOptional":true,
"isUnique":false,
"isIndexable":false,
"typeName":"array",
"valuesMaxCount":1,
"cardinality":"SET",
"valuesMinCount":0
}
{code}
Created an entity of the type with value for type_set_int as [1,2,3]. Entity is
created with 200 OK.
Following exception is thrown in console tab :
{code}
Uncaught TypeError: inputOutputField.indexOf is not a function
at http://172.27.16.74:21000/js/utils/CommonViewFunction.js:148:46
at Array.map (native)
at Object.CommonViewFunction.propertyTable
(http://172.27.16.74:21000/js/utils/CommonViewFunction.js:129:39)
at n.entityTableGenerate
(http://172.27.16.74:21000/js/views/entity/EntityDetailTableLayoutView.js:68:48)
at n.onRender
(http://172.27.16.74:21000/js/views/entity/EntityDetailTableLayoutView.js:56:22)
at
http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:7823
at n.triggerMethod
(http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:20703)
at n.render
(http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:21699)
at n.render
(http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:30148)
at constructor.show
(http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:11890)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (ATLAS-1713) V2 API to delete a type requires type definition to given as body
[
https://issues.apache.org/jira/browse/ATLAS-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharmadha Sainath updated ATLAS-1713:
-
Priority: Minor (was: Major)
> V2 API to delete a type requires type definition to given as body
> --
>
> Key: ATLAS-1713
> URL: https://issues.apache.org/jira/browse/ATLAS-1713
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Priority: Minor
>
> V2 API
> {code}
> api/atlas/v2/types/typedefs
> {code}
> requires body data when doing a HTTP DELETE request .
> Since type has both name and guid , it could be given as path instead of
> sending the whole type definition as body.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (ATLAS-1713) V2 API to delete a type requires type definition to given as body
Sharmadha Sainath created ATLAS-1713:
Summary: V2 API to delete a type requires type definition to given
as body
Key: ATLAS-1713
URL: https://issues.apache.org/jira/browse/ATLAS-1713
Project: Atlas
Issue Type: Improvement
Components: atlas-core
Affects Versions: 0.9-incubating
Reporter: Sharmadha Sainath
V2 API
{code}
api/atlas/v2/types/typedefs
{code}
requires body data when doing a HTTP DELETE request .
Since type has both name and guid , it could be given as path instead of
sending the whole type definition as body.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (ATLAS-1708) Incorrect error code while querying an entity for tag for which tag association is removed.
[
https://issues.apache.org/jira/browse/ATLAS-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharmadha Sainath updated ATLAS-1708:
-
Description:
1. Associated a tag PII to an entity.
2. /api/atlas/v2/entity/guid/{guid}/classification/PII GET query returned 200
OK.
3. Removed the PII tag from the entity.
4. /api/atlas/v2/entity/guid/{guid}/classification/PII GET query returned 500
Internal Server error. It should return 404 ideally.
Attached the exception stack trace from application logs when GET query is
fired.
Note : When a tag is not associated to the entity at all, and when the same GET
request is made with that tag name , 404 is returned.
For example , Tag Personal is not associated to the entity and the same GET
request with tag Personal returns 404 . *Only when a tag is associated and
disassociated from an entity, GET request throws 500 internal server *
was:
1. Associated a tag PII to an entity.
2. /api/atlas/v2/entity/guid/{guid}/classification/PII GET query returned 200
OK.
3. Removed the PII tag from the entity.
4. /api/atlas/v2/entity/guid/{guid}/PII GET query returned 500 Internal Server
error. It should return 404 ideally.
Attached the exception stack trace from application logs when GET query is
fired.
Note : When a tag is not associated to the entity at all, and when the same GET
request is made with that tag name , 404 is returned.
For example , Tag Personal is not associated to the entity and the same GET
request with tag Personal returns 404 . *Only when a tag is associated and
disassociated from an entity, GET request throws 500 internal server *
> Incorrect error code while querying an entity for tag for which tag
> association is removed.
> ---
>
> Key: ATLAS-1708
> URL: https://issues.apache.org/jira/browse/ATLAS-1708
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: trunk, 0.9-incubating
>Reporter: Sharmadha Sainath
> Attachments: EntityTagException.txt
>
>
> 1. Associated a tag PII to an entity.
> 2. /api/atlas/v2/entity/guid/{guid}/classification/PII GET query returned 200
> OK.
> 3. Removed the PII tag from the entity.
> 4. /api/atlas/v2/entity/guid/{guid}/classification/PII GET query returned 500
> Internal Server error. It should return 404 ideally.
> Attached the exception stack trace from application logs when GET query is
> fired.
> Note : When a tag is not associated to the entity at all, and when the same
> GET request is made with that tag name , 404 is returned.
> For example , Tag Personal is not associated to the entity and the same GET
> request with tag Personal returns 404 . *Only when a tag is associated and
> disassociated from an entity, GET request throws 500 internal server *
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (ATLAS-1708) Incorrect error code while querying an entity for tag for which tag association is removed.
[
https://issues.apache.org/jira/browse/ATLAS-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharmadha Sainath updated ATLAS-1708:
-
Description:
1. Associated a tag PII to an entity.
2. /api/atlas/v2/entity/guid/{guid}/classification/PII GET query returned 200
OK.
3. Removed the PII tag from the entity.
4. /api/atlas/v2/entity/guid/{guid}/PII GET query returned 500 Internal Server
error. It should return 404 ideally.
Attached the exception stack trace from application logs when GET query is
fired.
Note : When a tag is not associated to the entity at all, and when the same GET
request is made with that tag name , 404 is returned.
For example , Tag Personal is not associated to the entity and the same GET
request with tag Personal returns 404 . *Only when a tag is associated and
disassociated from an entity, GET request throws 500 internal server *
was:
1. Associated a tag PII to an entity.
2. /api/atlas/v2/entity/guid/{guid}/PII GET query returned 200 OK.
3. Removed the PII tag from the entity.
4. /api/atlas/v2/entity/guid/{guid}/PII GET query returned 500 Internal Server
error. It should return 404 ideally.
Attached the exception stack trace from application logs when GET query is
fired.
Note : When a tag is not associated to the entity at all, and when the same GET
request is made with that tag name , 404 is returned.
For example , Tag Personal is not associated to the entity and the same GET
request with tag Personal returns 404 . *Only when a tag is associated and
disassociated from an entity, GET request throws 500 internal server *
> Incorrect error code while querying an entity for tag for which tag
> association is removed.
> ---
>
> Key: ATLAS-1708
> URL: https://issues.apache.org/jira/browse/ATLAS-1708
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: trunk, 0.9-incubating
>Reporter: Sharmadha Sainath
> Attachments: EntityTagException.txt
>
>
> 1. Associated a tag PII to an entity.
> 2. /api/atlas/v2/entity/guid/{guid}/classification/PII GET query returned 200
> OK.
> 3. Removed the PII tag from the entity.
> 4. /api/atlas/v2/entity/guid/{guid}/PII GET query returned 500 Internal
> Server error. It should return 404 ideally.
> Attached the exception stack trace from application logs when GET query is
> fired.
> Note : When a tag is not associated to the entity at all, and when the same
> GET request is made with that tag name , 404 is returned.
> For example , Tag Personal is not associated to the entity and the same GET
> request with tag Personal returns 404 . *Only when a tag is associated and
> disassociated from an entity, GET request throws 500 internal server *
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (ATLAS-1708) Incorrect error code while querying an entity for tag for which tag association is removed.
Sharmadha Sainath created ATLAS-1708:
Summary: Incorrect error code while querying an entity for tag for
which tag association is removed.
Key: ATLAS-1708
URL: https://issues.apache.org/jira/browse/ATLAS-1708
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: trunk, 0.9-incubating
Reporter: Sharmadha Sainath
Attachments: EntityTagException.txt
1. Associated a tag PII to an entity.
2. /api/atlas/v2/entity/guid/{guid}/PII GET query returned 200 OK.
3. Removed the PII tag from the entity.
4. /api/atlas/v2/entity/guid/{guid}/PII GET query returned 500 Internal Server
error. It should return 404 ideally.
Attached the exception stack trace from application logs when GET query is
fired.
Note : When a tag is not associated to the entity at all, and when the same GET
request is made with that tag name , 404 is returned.
For example , Tag Personal is not associated to the entity and the same GET
request with tag Personal returns 404 . *Only when a tag is associated and
disassociated from an entity, GET request throws 500 internal server *
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (ATLAS-1687) Upgrade: hbase_column_family and hbase_column are not loaded into Atlas, even though hbase model json has it.
Sharmadha Sainath created ATLAS-1687: Summary: Upgrade: hbase_column_family and hbase_column are not loaded into Atlas, even though hbase model json has it. Key: ATLAS-1687 URL: https://issues.apache.org/jira/browse/ATLAS-1687 Project: Atlas Issue Type: Bug Components: atlas-core Affects Versions: 0.8-incubating Reporter: Sharmadha Sainath Priority: Critical Fix For: trunk, 0.9-incubating Atlas is installed on a cluster and the cluster is upgraded. hbase_column_family and hbase_column are not found in the /api/atlas/v2/types/typedefs/headers response in the upgraded cluster. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1681) Atlas went into inconsistent state after creating a type with faulty definition
[
https://issues.apache.org/jira/browse/ATLAS-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharmadha Sainath updated ATLAS-1681:
-
Description:
Created an entity type with one of its attribute name empty with the following
definition with the following JSON:
{code}
{
"structDefs":[
],
"entityDefs":[
{
"category":"ENTITY",
"updateTime":12345,
"name":"entity_incorrect",
"typeVersion":"0.1",
"attributeDefs":[
{
"name":"type_str",
"isOptional":true,
"isUnique":false,
"isIndexable":false,
"typeName":"string",
"valuesMaxCount":1,
"cardinality":"SINGLE",
"valuesMinCount":0
},
{
"name":"",
"typeName":"int",
"isOptional":true,
"cardinality":"SINGLE",
"valuesMinCount":-1,
"valuesMaxCount":-1,
"isUnique":false,
"isIndexable":false
}
],
"superTypes":[
],
"version":12345,
"guid":"-48964f25979it51334479",
"createTime":12345,
"description":"incorrect json"
}
],
"classificationDefs":[
],
"enumDefs":[
]
}
{code}
*Note the second attribute name in the attribute definition*
POSTed the type definition to
{code}
/api/atlas/v2/types/typedefs
{code}
The type is created ,with 200 OK but with exception
{code}
java.lang.IllegalArgumentException: Attribute name cannot be empty
{code}
(Attached the complete stack trace as a file)
Inconsistency Observed :
1. Types drop down box lists the type entity_incorrect , but clicking on it
throws "Invalid Expression" exception
2. Therafter ,any type creation (entity type , classification etc) is
succeeding with 200 OK but application.log has exception :
{code}
org.apache.atlas.query.Expressions$UnresolvedException: Unresolved id,
expression: entity_correct
{code}
Example :
After POSTing the incorrect json to Atlas , created a tag tag_after in UI . It
succeeded. But Search of tag throws invalid expression and tag Association to
entity fails with
{code}
org.apache.atlas.exception.AtlasBaseException:
org.apache.atlas.repository.RepositoryException:
org.apache.atlas.typesystem.exception.TypeNotFoundException: Unknown datatype:
tag_after
{code}
Type registration is affected when Atlas accepts the wrong JSON.
Giving an empty attribute name is not a very common scenario but at what
conditions such wrong JSONs could be accepted should be looked at.
was:
Created an entity type with one of its attribute name empty with the following
definition with the following JSON:
{code}
{
"structDefs":[
],
"entityDefs":[
{
"category":"ENTITY",
"updateTime":12345,
"name":"entity_incorrect",
"typeVersion":"0.1",
"attributeDefs":[
{
"name":"type_str",
"isOptional":true,
"isUnique":false,
"isIndexable":false,
"typeName":"string",
"valuesMaxCount":1,
"cardinality":"SINGLE",
"valuesMinCount":0
},
{
"name":"",
"typeName":"int",
"isOptional":true,
"cardinality":"SINGLE",
"valuesMinCount":-1,
"valuesMaxCount":-1,
"isUnique":false,
"isIndexable":false
}
],
"superTypes":[
],
"version":12345,
"guid":"-48964f25979it51334479",
"createTime":12345,
"description":"incorrect json"
}
],
"classificationDefs":[
],
"enumDefs":[
]
}
{code}
*Note the second attribute name in the attribute definition*
POSTed the type definition to
{code}
/api/atlas/v2/types/typedefs
{code}
The type is created ,with 200 OK but with exception
{code}
java.lang.IllegalArgumentException: Attribute name cannot be empty
{code}
(Attached the complete stack trace as a file)
Inconsistency Observed :
1. Types drop down box lists the type , but clicking on it throws "Invalid
Expression" exception
2. Therafter ,any type creation (entity type , classification etc) is
succeeding with 200 OK but application.log has exception :
{code}
org.apache.atlas.query.Expressions$UnresolvedException: Unresolved id,
expression: entity_correct
{code}
Example :
After POSTing the incorrect json to Atlas , created a tag tag_after in UI . It
succeeded. But Search of tag throws invalid expression and tag Association to
entity fails with
{code}
org.apache.atlas.exception.AtlasBaseException:
org.apache.atlas.repository.RepositoryException:
org.apache.atlas.typesystem.exception.TypeNotFoundException: Unknown
[jira] [Created] (ATLAS-1681) Atlas went into inconsistent state after creating a type with faulty definition
Sharmadha Sainath created ATLAS-1681:
Summary: Atlas went into inconsistent state after creating a type
with faulty definition
Key: ATLAS-1681
URL: https://issues.apache.org/jira/browse/ATLAS-1681
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: trunk, 0.9-incubating
Reporter: Sharmadha Sainath
Attachments: EmptyAttrNameInTypeDef.txt
Created an entity type with one of its attribute name empty with the following
definition with the following JSON:
{code}
{
"structDefs":[
],
"entityDefs":[
{
"category":"ENTITY",
"updateTime":12345,
"name":"entity_incorrect",
"typeVersion":"0.1",
"attributeDefs":[
{
"name":"type_str",
"isOptional":true,
"isUnique":false,
"isIndexable":false,
"typeName":"string",
"valuesMaxCount":1,
"cardinality":"SINGLE",
"valuesMinCount":0
},
{
"name":"",
"typeName":"int",
"isOptional":true,
"cardinality":"SINGLE",
"valuesMinCount":-1,
"valuesMaxCount":-1,
"isUnique":false,
"isIndexable":false
}
],
"superTypes":[
],
"version":12345,
"guid":"-48964f25979it51334479",
"createTime":12345,
"description":"incorrect json"
}
],
"classificationDefs":[
],
"enumDefs":[
]
}
{code}
*Note the second attribute name in the attribute definition*
POSTed the type definition to
{code}
/api/atlas/v2/types/typedefs
{code}
The type is created ,with 200 OK but with exception
{code}
java.lang.IllegalArgumentException: Attribute name cannot be empty
{code}
(Attached the complete stack trace as a file)
Inconsistency Observed :
1. Types drop down box lists the type , but clicking on it throws "Invalid
Expression" exception
2. Therafter ,any type creation (entity type , classification etc) is
succeeding with 200 OK but application.log has exception :
{code}
org.apache.atlas.query.Expressions$UnresolvedException: Unresolved id,
expression: entity_correct
{code}
Example :
After POSTing the incorrect json to Atlas , created a tag tag_after in UI . It
succeeded. But Search of tag throws invalid expression and tag Association to
entity fails with
{code}
org.apache.atlas.exception.AtlasBaseException:
org.apache.atlas.repository.RepositoryException:
org.apache.atlas.typesystem.exception.TypeNotFoundException: Unknown datatype:
tag_after
{code}
Type registration is affected when Atlas accepts the wrong JSON.
Giving an empty attribute name is not a very common scenario but at what
conditions such wrong JSONs could be accepted should be looked at.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (ATLAS-1675) In HA mode , tag created in Active Server not present in new Active server after failover.
Sharmadha Sainath created ATLAS-1675: Summary: In HA mode , tag created in Active Server not present in new Active server after failover. Key: ATLAS-1675 URL: https://issues.apache.org/jira/browse/ATLAS-1675 Project: Atlas Issue Type: Bug Components: atlas-core Affects Versions: 0.9-incubating Reporter: Sharmadha Sainath A) 1.host1 , host2 both are up and host1 is ACTIVE. 2.Created a tag when host1 is ACTIVE and tag creation is successful . 3.Did a manual failover. 4.Now host2 is ACTIVE and host1 is PASSIVE. *same tag is not present in host2* B) : 1. host1 is up and host2 is down. 2.Created tag in host1 . 3.Started host2 4.brought down host1 and started host1 (just to make host2 ACTIVE) 5.*Now tag is present in host2 and host1* This happens only for tag . For entities created through hook or UI , entity persists in both hosts in both scenarios. (Verified with hive_table created through hook and an hdfs_path created in UI) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1661) import hive script to handle updates like rename/delete
[ https://issues.apache.org/jira/browse/ATLAS-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924301#comment-15924301 ] Sharmadha Sainath commented on ATLAS-1661: -- [~ayubkhan] >> I believe the intent of import-hive.sh tool is not to track all the metadata >> changes but to take a snapshot of the metadata at that point of time. I completely agree with you. That is the intent. Currently import-hive script looks for the qualified name of the table if it is already present , and updates the same . In the case mentioned in the description , it doesn't find the table tablenew so it creates a new table. But it would be a good to have feature if import hive script could have a mechanism to know the history of the tablenew and update accordingly. >> Are you suggesting to have the hiveHook capability built into import-hive.sh >> tool also? Yes , because that would be the expectation from the customer. Only difference customer would know is , hive hook updates as and when query is fired , and import hive script does bunch update when run. > import hive script to handle updates like rename/delete > --- > > Key: ATLAS-1661 > URL: https://issues.apache.org/jira/browse/ATLAS-1661 > Project: Atlas > Issue Type: Improvement > Components: atlas-intg >Reporter: Sharmadha Sainath >Priority: Minor > > 1. Disabled hive hook > 2. Created table table1 > 3. Ran import-hive.sh script , Atlas ingested table1. > 4. Altered table table1 , rename to table1_new. > 5. Ran import-hive.sh script , Atlas created a new table table1new . > table1 wasn't updated with new name. > This is the expected behavior with import-hive script as opposed to hive > hook, as hive hook is synchronous and import-hive is not. > But as a customer , running import-hive.sh multiple times and doing many hive > operations may result in inconsistency while applying ranger policies to the > table and in many scenarios , since it is not documented to run import hive > script only once. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1661) import hive script to handle updates like rename/delete
Sharmadha Sainath created ATLAS-1661: Summary: import hive script to handle updates like rename/delete Key: ATLAS-1661 URL: https://issues.apache.org/jira/browse/ATLAS-1661 Project: Atlas Issue Type: Improvement Components: atlas-intg Reporter: Sharmadha Sainath Priority: Minor 1. Disabled hive hook 2. Created table table1 3. Ran import-hive.sh script , Atlas ingested table1. 4. Altered table table1 , rename to table1_new. 5. Ran import-hive.sh script , Atlas created a new table table1new . table1 wasn't updated with new name. This is the expected behavior with import-hive script as opposed to hive hook, as hive hook is synchronous and import-hive is not. But as a customer , running import-hive.sh multiple times and doing many hive operations may result in inconsistency while applying ranger policies to the table and in many scenarios , since it is not documented to run import hive script only once. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1660) Regression : Error code mismatch in while GETing a type that doesn't exist.
Sharmadha Sainath created ATLAS-1660:
Summary: Regression : Error code mismatch in while GETing a type
that doesn't exist.
Key: ATLAS-1660
URL: https://issues.apache.org/jira/browse/ATLAS-1660
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 0.9-incubating
Reporter: Sharmadha Sainath
Querying for a type that doesn't exist results in 400 [Bad Request] . It should
be 404 [Not Found] .
Both V1 and V2 APIs return 400 .
{code}
/api/atlas/types/unknowntype
/api/atlas/v2/types/typedef/name/unknowntype
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (ATLAS-1646) V1 and V2 GET entity response show different values for date attribute of a tag which has no value set.
Sharmadha Sainath created ATLAS-1646:
Summary: V1 and V2 GET entity response show different values for
date attribute of a tag which has no value set.
Key: ATLAS-1646
URL: https://issues.apache.org/jira/browse/ATLAS-1646
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 0.8-incubating
Reporter: Sharmadha Sainath
Created a tag with date as attribute and POSTed to /api/atlas/types. Associated
the tag to an entity with no value for date through REST API. Association is
successful .V1 GET Entity API shows 1970-01-01T00:00:00.000Z as value for date
and V2 GET Entity API shows 0 as value for date.
V1 API :
{code}
/api/atlas/entities/b10e3c49-af76-4585-893e-c7de6a97ad9b
{code}
{code}
{
requestId: "pool-2-thread-9 - 2c83885c-166b-418c-a7ac-441e1b68d3f2",
definition: {
jsonClass:
"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
id: {
jsonClass:
"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
id: "b10e3c49-af76-4585-893e-c7de6a97ad9b",
version: 0,
typeName: "EntityTraitTestClasshqorbbnkkx",
state: "ACTIVE"
},
typeName: "EntityTraitTestClasshqorbbnkkx",
values: {
name: "EntityTraitTestEntity9psmssjmyp"
},
traitNames: [
"addTraitOptionalAttrNotSet9psmssjmyp"
],
traits: {
addTraitOptionalAttrNotSet9psmssjmyp: {
jsonClass:
"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
typeName:
"addTraitOptionalAttrNotSet9psmssjmyp",
values: {
date: "1970-01-01T00:00:00.000Z",
name: "addTraitOptionalAttrName"
}
}
},
systemAttributes: {
createdBy: "admin",
modifiedBy: "admin",
createdTime: "2017-03-06T13:08:37.666Z",
modifiedTime: "2017-03-06T13:08:37.666Z"
}
}
}
{code}
V2 API response
{code}
/api/atlas/v2/entity/guid/b10e3c49-af76-4585-893e-c7de6a97ad9b
{code}
{code}
{
referredEntities: {},
entity: {
typeName: "EntityTraitTestClasshqorbbnkkx",
attributes: {
name: "EntityTraitTestEntity9psmssjmyp"
},
guid: "b10e3c49-af76-4585-893e-c7de6a97ad9b",
status: "ACTIVE",
createdBy: "admin",
updatedBy: "admin",
createTime: 1488805717666,
updateTime: 1488805717666,
version: 0,
classifications: [{
typeName: "addTraitOptionalAttrNotSet9psmssjmyp",
attributes: {
date: 0,
name: "addTraitOptionalAttrName"
}
}]
}
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (ATLAS-1645) Tag is not associated when value for optional attributes are not provided for byte ,date, double,float,short,int.
[ https://issues.apache.org/jira/browse/ATLAS-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharmadha Sainath updated ATLAS-1645: - Affects Version/s: 0.8-incubating > Tag is not associated when value for optional attributes are not provided for > byte ,date, double,float,short,int. > - > > Key: ATLAS-1645 > URL: https://issues.apache.org/jira/browse/ATLAS-1645 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8-incubating >Reporter: Sharmadha Sainath > Attachments: Empty value for tag attributes exception.txt > > > 1. Created 8 tags. > 2. Each tag with one attribute of types byte,date, double,float,short,int, > string,boolean. > 3. Associated all the tags to an entity one by one without providing any > value for the tag attribute. > 4.Only tags with string and boolean as types got associated. Rest of the tag > association threw 500 internal server error as empty values are treated as > string and are validated against the datatype. > Trait attribute values are optional ,so empty values should be handled. > Following types expect value : > - byte > - date > - double > - float > - short > - int > Attached exception stack trace when associating an entity, a PII tag with > attribute id of type int ,with no value for id. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1645) Tag is not associated when value for optional attributes are not provided for byte ,date, double,float,short,int.
[ https://issues.apache.org/jira/browse/ATLAS-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharmadha Sainath updated ATLAS-1645: - Component/s: atlas-webui > Tag is not associated when value for optional attributes are not provided for > byte ,date, double,float,short,int. > - > > Key: ATLAS-1645 > URL: https://issues.apache.org/jira/browse/ATLAS-1645 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8-incubating >Reporter: Sharmadha Sainath > Attachments: Empty value for tag attributes exception.txt > > > 1. Created 8 tags. > 2. Each tag with one attribute of types byte,date, double,float,short,int, > string,boolean. > 3. Associated all the tags to an entity one by one without providing any > value for the tag attribute. > 4.Only tags with string and boolean as types got associated. Rest of the tag > association threw 500 internal server error as empty values are treated as > string and are validated against the datatype. > Trait attribute values are optional ,so empty values should be handled. > Following types expect value : > - byte > - date > - double > - float > - short > - int > Attached exception stack trace when associating an entity, a PII tag with > attribute id of type int ,with no value for id. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1645) Tag is not associated when value for optional attributes are not provided for byte ,date, double,float,short,int.
[ https://issues.apache.org/jira/browse/ATLAS-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharmadha Sainath updated ATLAS-1645: - Component/s: (was: atlas-webui) atlas-core > Tag is not associated when value for optional attributes are not provided for > byte ,date, double,float,short,int. > - > > Key: ATLAS-1645 > URL: https://issues.apache.org/jira/browse/ATLAS-1645 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8-incubating >Reporter: Sharmadha Sainath > Attachments: Empty value for tag attributes exception.txt > > > 1. Created 8 tags. > 2. Each tag with one attribute of types byte,date, double,float,short,int, > string,boolean. > 3. Associated all the tags to an entity one by one without providing any > value for the tag attribute. > 4.Only tags with string and boolean as types got associated. Rest of the tag > association threw 500 internal server error as empty values are treated as > string and are validated against the datatype. > Trait attribute values are optional ,so empty values should be handled. > Following types expect value : > - byte > - date > - double > - float > - short > - int > Attached exception stack trace when associating an entity, a PII tag with > attribute id of type int ,with no value for id. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1645) Tag is not associated when value for optional attributes are not provided for byte ,date, double,float,short,int.
Sharmadha Sainath created ATLAS-1645: Summary: Tag is not associated when value for optional attributes are not provided for byte ,date, double,float,short,int. Key: ATLAS-1645 URL: https://issues.apache.org/jira/browse/ATLAS-1645 Project: Atlas Issue Type: Bug Reporter: Sharmadha Sainath Attachments: Empty value for tag attributes exception.txt 1. Created 8 tags. 2. Each tag with one attribute of types byte,date, double,float,short,int, string,boolean. 3. Associated all the tags to an entity one by one without providing any value for the tag attribute. 4.Only tags with string and boolean as types got associated. Rest of the tag association threw 500 internal server error as empty values are treated as string and are validated against the datatype. Trait attribute values are optional ,so empty values should be handled. Following types expect value : - byte - date - double - float - short - int Attached exception stack trace when associating an entity, a PII tag with attribute id of type int ,with no value for id. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1644) Taxonomy API /api/atlas/v1/taxonomies is broken.
Sharmadha Sainath created ATLAS-1644:
Summary: Taxonomy API /api/atlas/v1/taxonomies is broken.
Key: ATLAS-1644
URL: https://issues.apache.org/jira/browse/ATLAS-1644
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 0.8-incubating
Reporter: Sharmadha Sainath
Priority: Blocker
The following API throws 500 Internal server error
{code}
http://localhost:21000/api/atlas/v1/taxonomies
{code}
with the following error notification :
{code}
An unexpected error has occurred.
org.apache.atlas.catalog.exception.CatalogRuntimeException: :
java.lang.ClassCastException:
org.apache.atlas.repository.graphdb.titan0.Titan0Vertex cannot be cast to
com.tinkerpop.blueprints.Element
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (ATLAS-1643) Edit Entity in UI : simple entity s1 association to compound entity c1 not broken after s1 is associated to some other compound entity c2.
[ https://issues.apache.org/jira/browse/ATLAS-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharmadha Sainath updated ATLAS-1643: - Description: 1. Created hbase_table "employee" in UI . 2. Created hbase_column_family "personalData" in UI with its hbase_table as "employee" (Now association is correct for both hbase_column_family and hbase_table) 3.Created another hbase_table "employee_abc" in UI. 4.Edited personalData and modified hbase_table to be "employee_abc". Now personalData's hbase_table is "employee_abc" and "employee_abc" has personalData as one of its column_families . *But hbase_table employee still has personalData as one of its column families. The broken association still prevails* . And unable to edit hbase_table employee and remove "personalData". was: 1. Created hbase_table "employee" in UI . 2. Created hbase_column_family "personalData" in UI with its hbase_table as "employee" (Now association was correct for both hbase_column_family and hbase_table) 3.Created another hbase_table "employee_abc" in UI. 4.Edited personalData and modified hbase_table to be "employee_abc". Now personalData's hbase_table is "employee_abc" and "employee_abc" has personalData as one of its column_families . *But hbase_table employee still has personalData as one of its column families. The broken association still prevails* > Edit Entity in UI : simple entity s1 association to compound entity c1 not > broken after s1 is associated to some other compound entity c2. > -- > > Key: ATLAS-1643 > URL: https://issues.apache.org/jira/browse/ATLAS-1643 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8-incubating >Reporter: Sharmadha Sainath >Priority: Critical > > 1. Created hbase_table "employee" in UI . > 2. Created hbase_column_family "personalData" in UI with its hbase_table as > "employee" > (Now association is correct for both hbase_column_family and hbase_table) > 3.Created another hbase_table "employee_abc" in UI. > 4.Edited personalData and modified hbase_table to be "employee_abc". > Now personalData's hbase_table is "employee_abc" and "employee_abc" has > personalData as one of its column_families . *But hbase_table employee still > has personalData as one of its column families. The broken association still > prevails* . And unable to edit hbase_table employee and remove "personalData". -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1643) Edit Entity in UI : simple entity s1 association to compound entity c1 not broken after s1 is associated to some other compound entity c2.
Sharmadha Sainath created ATLAS-1643: Summary: Edit Entity in UI : simple entity s1 association to compound entity c1 not broken after s1 is associated to some other compound entity c2. Key: ATLAS-1643 URL: https://issues.apache.org/jira/browse/ATLAS-1643 Project: Atlas Issue Type: Bug Components: atlas-core Affects Versions: 0.8-incubating Reporter: Sharmadha Sainath Priority: Critical 1. Created hbase_table "employee" in UI . 2. Created hbase_column_family "personalData" in UI with its hbase_table as "employee" (Now association was correct for both hbase_column_family and hbase_table) 3.Created another hbase_table "employee_abc" in UI. 4.Edited personalData and modified hbase_table to be "employee_abc". Now personalData's hbase_table is "employee_abc" and "employee_abc" has personalData as one of its column_families . *But hbase_table employee still has personalData as one of its column families. The broken association still prevails* -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1608) Search UI improvement
[ https://issues.apache.org/jira/browse/ATLAS-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15896821#comment-15896821 ] Sharmadha Sainath commented on ATLAS-1608: -- [~kevalbhatt] Few questions on this Search UI changes : 1. What is meant by making Search Tab *default* ? 2. Basic search (Full Text Search) also shows both Search by type and Search by query like DSL Search which seems confusing to the user . Only Atlas experts might know that one is making Full text call and other DSL. Why is Search by type introduced in the Basic Search ? 3. In Tags Tab ,we have DSL search of tag already. Basic Search has Search by tag. Why do we have tag search in Basic search ? > Search UI improvement > - > > Key: ATLAS-1608 > URL: https://issues.apache.org/jira/browse/ATLAS-1608 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Affects Versions: 0.8-incubating >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Fix For: 0.8-incubating > > Attachments: ATLAS-1608.1.patch, ATLAS-1608.2.patch, > ATLAS-1608.3.patch, ATLAS-1608.4.patch, ATLAS-1608.patch > > > 1) Make Search as a default tab. > 2) Add type and tag search droup-down for both DSL (Advance) and FULLTEXT > (basic) search. > 3) Add help popup. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (ATLAS-1641) UI Regression : Clicking on "Add Tag" button in the Search result table in index.html page doesn't open up the Add Tag window.
[ https://issues.apache.org/jira/browse/ATLAS-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharmadha Sainath reassigned ATLAS-1641: Assignee: Keval Bhatt > UI Regression : Clicking on "Add Tag" button in the Search result table in > index.html page doesn't open up the Add Tag window. > -- > > Key: ATLAS-1641 > URL: https://issues.apache.org/jira/browse/ATLAS-1641 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.8-incubating >Reporter: Sharmadha Sainath >Assignee: Keval Bhatt >Priority: Critical > > Clicking on "Add Tag" button corresponding to any entity in the Search result > table in index.html page doesn't open up the Add Tag window. Network tab in > the browser shows no action or query being fired on clicking the button. > But in the detailsPage of entity , Add tag button is clickable and opens up > the Add Tag Window. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1641) UI Regression : Clicking on "Add Tag" button in the Search result table in index.html page doesn't open up the Add Tag window.
Sharmadha Sainath created ATLAS-1641: Summary: UI Regression : Clicking on "Add Tag" button in the Search result table in index.html page doesn't open up the Add Tag window. Key: ATLAS-1641 URL: https://issues.apache.org/jira/browse/ATLAS-1641 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 0.8-incubating Reporter: Sharmadha Sainath Priority: Critical Clicking on "Add Tag" button corresponding to any entity in the Search result table in index.html page doesn't open up the Add Tag window. Network tab in the browser shows no action or query being fired on clicking the button. But in the detailsPage of entity , Add tag button is clickable and opens up the Add Tag Window. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1639) V1 DSL Query not working in V2.
Sharmadha Sainath created ATLAS-1639:
Summary: V1 DSL Query not working in V2.
Key: ATLAS-1639
URL: https://issues.apache.org/jira/browse/ATLAS-1639
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Sharmadha Sainath
Priority: Blocker
Query :
{code}
hive_table as t where name="table_1"
{code}
V1 API below gives correct results
{code}
http://localhost:21000/api/atlas/discovery/search/dsl?limit=25&query=hive_table+as+t+where+name%3D%22table_1%22+select+t
{code}
same query in V2 API throws 500 internal server error with invalid query
expression notification.
{code}
http://localhost:21000/api/atlas/v2/search/dsl?limit=25&query=hive_table+as+t+where+name%3D%22table_1%22+select+t
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (ATLAS-1639) V1 API DSL Query not working with V2 APIs.
[
https://issues.apache.org/jira/browse/ATLAS-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharmadha Sainath updated ATLAS-1639:
-
Summary: V1 API DSL Query not working with V2 APIs. (was: V1 DSL Query not
working in V2.)
> V1 API DSL Query not working with V2 APIs.
> --
>
> Key: ATLAS-1639
> URL: https://issues.apache.org/jira/browse/ATLAS-1639
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Sharmadha Sainath
>Priority: Blocker
>
> Query :
> {code}
> hive_table as t where name="table_1"
> {code}
> V1 API below gives correct results
> {code}
> http://localhost:21000/api/atlas/discovery/search/dsl?limit=25&query=hive_table+as+t+where+name%3D%22table_1%22+select+t
> {code}
> same query in V2 API throws 500 internal server error with invalid query
> expression notification.
> {code}
> http://localhost:21000/api/atlas/v2/search/dsl?limit=25&query=hive_table+as+t+where+name%3D%22table_1%22+select+t
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (ATLAS-1636) Hive partitions are showed as Columns in addition to hive columns in /api/atlas/entities response and in Atlas UI.
Sharmadha Sainath created ATLAS-1636: Summary: Hive partitions are showed as Columns in addition to hive columns in /api/atlas/entities response and in Atlas UI. Key: ATLAS-1636 URL: https://issues.apache.org/jira/browse/ATLAS-1636 Project: Atlas Issue Type: Bug Components: atlas-core Affects Versions: 0.8-incubating Reporter: Sharmadha Sainath Priority: Blocker Created table t1 with columns : id int,name string,dob date partitioned by country string. Atlas UI shows "country" in columns and also in partitionKeys /api/atlas/entities/ lists the "country" in columns. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1635) Qualified name in v1 lineage APIs have name even when Qualified name for that entity is available.
Sharmadha Sainath created ATLAS-1635:
Summary: Qualified name in v1 lineage APIs have name even when
Qualified name for that entity is available.
Key: ATLAS-1635
URL: https://issues.apache.org/jira/browse/ATLAS-1635
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 0.8-incubating
Reporter: Sharmadha Sainath
Following is the API response of the below V1 API.
{code}
http://localhost:21000/api/atlas/lineage/317a2edf-d280-4b36-a385-11d56f99dc66/inputs/graph
{code}
{code}
{
requestId: "pool-1-thread-9 - 5f7f24de-97a0-467e-9e23-6d9c385701ff",
results: {
jsonClass:
"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
typeName: "__tempQueryResultStruct2",
values: {
vertices: {
317 a2edf - d280 - 4 b36 - a385 - 11
d56f99dc66: {
jsonClass:
"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
typeName: "__tempQueryResultStruct0",
values: {
qualifiedName: "t1ctas",
vertexId: {
jsonClass:
"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
typeName: "__IdType",
values: {
guid:
"317a2edf-d280-4b36-a385-11d56f99dc66",
state: "ACTIVE",
typeName:
"hive_table"
}
},
name: "t1ctas"
}
},
fd9caa83 - c861 - 4314 - a33d - 56e9 dcea1c44: {
jsonClass:
"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
typeName: "__tempQueryResultStruct1",
values: {
qualifiedName: "t1",
vertexId: {
jsonClass:
"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
typeName: "__IdType",
values: {
guid:
"fd9caa83-c861-4314-a33d-56e9dcea1c44",
state: "ACTIVE",
typeName:
"hive_table"
}
},
name: "t1"
}
}
},
edges: {
317 a2edf - d280 - 4 b36 - a385 - 11
d56f99dc66: [
"305e65b3-6058-4ac8-be3c-9d60d42df4d4"
],
305e65 b3 - 6058 - 4 ac8 - be3c - 9
d60d42df4d4: [
"fd9caa83-c861-4314-a33d-56e9dcea1c44"
]
}
}
}
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (ATLAS-1633) Setting soft delete or hard delete to atlas.DeleteHandler.impl in atlas-application properties throws exceptions.
[
https://issues.apache.org/jira/browse/ATLAS-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharmadha Sainath updated ATLAS-1633:
-
Affects Version/s: (was: 0.6-incubating)
0.8-incubating
> Setting soft delete or hard delete to atlas.DeleteHandler.impl in
> atlas-application properties throws exceptions.
> --
>
> Key: ATLAS-1633
> URL: https://issues.apache.org/jira/browse/ATLAS-1633
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Sharmadha Sainath
> Attachments: Delete handler Exception.txt
>
>
> Providing any of the allowed values mentioned in atlas-application.properties
> throws exceptions while Atlas starts up.
> Set
> {code}
> atlas.DeleteHandler.impl=org.apache.atlas.repository.graph.SoftDeleteHandler
> {code}
> Attached the Exception stack trace.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (ATLAS-1633) Setting soft delete or hard delete to atlas.DeleteHandler.impl in atlas-application properties throws exceptions.
Sharmadha Sainath created ATLAS-1633:
Summary: Setting soft delete or hard delete to
atlas.DeleteHandler.impl in atlas-application properties throws exceptions.
Key: ATLAS-1633
URL: https://issues.apache.org/jira/browse/ATLAS-1633
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 0.6-incubating
Reporter: Sharmadha Sainath
Attachments: Delete handler Exception.txt
Providing any of the allowed values mentioned in atlas-application.properties
throws exceptions while Atlas starts up.
Set
{code}
atlas.DeleteHandler.impl=org.apache.atlas.repository.graph.SoftDeleteHandler
{code}
Attached the Exception stack trace.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (ATLAS-1619) import-hive.sh script failure
[ https://issues.apache.org/jira/browse/ATLAS-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharmadha Sainath updated ATLAS-1619: - Attachment: (was: atlas exception during import-hive.txt) > import-hive.sh script failure > - > > Key: ATLAS-1619 > URL: https://issues.apache.org/jira/browse/ATLAS-1619 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8-incubating >Reporter: Sharmadha Sainath >Priority: Blocker > Attachments: import-hive atlas logs.txt, import hive exception.txt > > > 1. Disabled the hive hook > 2. created hive_table in hive CLI > 3. ran import-hive.sh script which ran fine. > 4. Altered table in hive CLI and added new columns. > 5. Ran import-hive.sh script. Import-hive.sh failed to take the update > throwing 404 exception. > Attached the console logs on running import-hive and atlas logs. > Problems : > 1. /logs/import-hive.log is not created. > 2. Exceptions seen on console while executing the script and in > application.log are attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1619) import-hive.sh script failure
[ https://issues.apache.org/jira/browse/ATLAS-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharmadha Sainath updated ATLAS-1619: - Attachment: (was: import-hive console log.txt) > import-hive.sh script failure > - > > Key: ATLAS-1619 > URL: https://issues.apache.org/jira/browse/ATLAS-1619 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8-incubating >Reporter: Sharmadha Sainath >Priority: Blocker > Attachments: import-hive atlas logs.txt, import hive exception.txt > > > 1. Disabled the hive hook > 2. created hive_table in hive CLI > 3. ran import-hive.sh script which ran fine. > 4. Altered table in hive CLI and added new columns. > 5. Ran import-hive.sh script. Import-hive.sh failed to take the update > throwing 404 exception. > Attached the console logs on running import-hive and atlas logs. > Problems : > 1. /logs/import-hive.log is not created. > 2. Exceptions seen on console while executing the script and in > application.log are attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1619) import-hive.sh script failure
[ https://issues.apache.org/jira/browse/ATLAS-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharmadha Sainath updated ATLAS-1619: - Attachment: import-hive atlas logs.txt import hive exception.txt > import-hive.sh script failure > - > > Key: ATLAS-1619 > URL: https://issues.apache.org/jira/browse/ATLAS-1619 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8-incubating >Reporter: Sharmadha Sainath >Priority: Blocker > Attachments: import-hive atlas logs.txt, import hive exception.txt > > > 1. Disabled the hive hook > 2. created hive_table in hive CLI > 3. ran import-hive.sh script which ran fine. > 4. Altered table in hive CLI and added new columns. > 5. Ran import-hive.sh script. Import-hive.sh failed to take the update > throwing 404 exception. > Attached the console logs on running import-hive and atlas logs. > Problems : > 1. /logs/import-hive.log is not created. > 2. Exceptions seen on console while executing the script and in > application.log are attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1619) import-hive.sh script failure
[ https://issues.apache.org/jira/browse/ATLAS-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharmadha Sainath updated ATLAS-1619: - Description: 1. Disabled the hive hook 2. created hive_table in hive CLI 3. ran import-hive.sh script which ran fine. 4. Altered table in hive CLI and added new columns. 5. Ran import-hive.sh script. Import-hive.sh failed to take the update throwing 404 exception. Attached the console logs on running import-hive and atlas logs. Problems : 1. /logs/import-hive.log is not created. 2. Exceptions seen on console while executing the script and in application.log are attached. was: 1. Created hive tables with hook configuration set in hive. 2. Removed hook configuration in hive. Restarted hive. 3. Created tables in hive and ran the import-hive.sh Problems : 1. /logs/import-hive.log is not created. 2. Exceptions seen on console while executing the script and in application.log are attached. > import-hive.sh script failure > - > > Key: ATLAS-1619 > URL: https://issues.apache.org/jira/browse/ATLAS-1619 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8-incubating >Reporter: Sharmadha Sainath >Priority: Blocker > Attachments: import-hive atlas logs.txt, import hive exception.txt > > > 1. Disabled the hive hook > 2. created hive_table in hive CLI > 3. ran import-hive.sh script which ran fine. > 4. Altered table in hive CLI and added new columns. > 5. Ran import-hive.sh script. Import-hive.sh failed to take the update > throwing 404 exception. > Attached the console logs on running import-hive and atlas logs. > Problems : > 1. /logs/import-hive.log is not created. > 2. Exceptions seen on console while executing the script and in > application.log are attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1500) UI : "retention" attribute value is always shown as date in hive_table properties.
[ https://issues.apache.org/jira/browse/ATLAS-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15892674#comment-15892674 ] Sharmadha Sainath commented on ATLAS-1500: -- [~madhan.neethiraj] , right from 0.7-incubating branch , it is displayed as date. Previous branches don't have the file CommonViewFunction.js. So not able to figure it out in previous versions. > UI : "retention" attribute value is always shown as date in hive_table > properties. > -- > > Key: ATLAS-1500 > URL: https://issues.apache.org/jira/browse/ATLAS-1500 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Sharmadha Sainath >Assignee: Sharmadha Sainath >Priority: Minor > Attachments: ATLAS-1500.patch > > > retention is an int attribute in hive_table model . GET Response of the > hive_table entity has correct int value and also gets updated when edited. > But UI always shows a static date value "Thu Jan 01 1970 05:30:00 GMT+0530 > (IST)" for retention. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1620) Regression : Audit logs not generated when Adding/Removing Tag.
Sharmadha Sainath created ATLAS-1620: Summary: Regression : Audit logs not generated when Adding/Removing Tag. Key: ATLAS-1620 URL: https://issues.apache.org/jira/browse/ATLAS-1620 Project: Atlas Issue Type: Bug Components: atlas-core Affects Versions: 0.8-incubating Reporter: Sharmadha Sainath 1.Created kafka_topic entity in UI. 2.Audit Tab for that entity had an entry "Entity Created". 3.On Adding and removing tag from the entity , no audit logs are found. GET Audit Response also has only entry for Entity Create event. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1500) UI : "retention" attribute value is always shown as date in hive_table properties.
[ https://issues.apache.org/jira/browse/ATLAS-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891877#comment-15891877 ] Sharmadha Sainath commented on ATLAS-1500: -- [~kevalbhatt] [~madhan.neethiraj] [~svimal2106] Attaching patch for review. > UI : "retention" attribute value is always shown as date in hive_table > properties. > -- > > Key: ATLAS-1500 > URL: https://issues.apache.org/jira/browse/ATLAS-1500 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Sharmadha Sainath >Assignee: Sharmadha Sainath >Priority: Minor > Attachments: ATLAS-1500.patch > > > retention is an int attribute in hive_table model . GET Response of the > hive_table entity has correct int value and also gets updated when edited. > But UI always shows a static date value "Thu Jan 01 1970 05:30:00 GMT+0530 > (IST)" for retention. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1619) import-hive.sh script failure
[ https://issues.apache.org/jira/browse/ATLAS-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891844#comment-15891844 ] Sharmadha Sainath commented on ATLAS-1619: -- Faced the problem without ATLAS-1603 fix. I will update the JIRA with ATLAS-1603 fix as given in ATLAS-1604. > import-hive.sh script failure > - > > Key: ATLAS-1619 > URL: https://issues.apache.org/jira/browse/ATLAS-1619 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8-incubating >Reporter: Sharmadha Sainath >Priority: Blocker > Attachments: atlas exception during import-hive.txt, import-hive > console log.txt > > > 1. Created hive tables with hook configuration set in hive. > 2. Removed hook configuration in hive. Restarted hive. > 3. Created tables in hive and ran the import-hive.sh > Problems : > 1. /logs/import-hive.log is not created. > 2. Exceptions seen on console while executing the script and in > application.log are attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1619) import-hive.sh script failure
[ https://issues.apache.org/jira/browse/ATLAS-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharmadha Sainath updated ATLAS-1619: - Attachment: atlas exception during import-hive.txt > import-hive.sh script failure > - > > Key: ATLAS-1619 > URL: https://issues.apache.org/jira/browse/ATLAS-1619 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8-incubating >Reporter: Sharmadha Sainath >Priority: Blocker > Attachments: atlas exception during import-hive.txt, import-hive > console log.txt > > > 1. Created hive tables with hook configuration set in hive. > 2. Removed hook configuration in hive. Restarted hive. > 3. Created tables in hive and ran the import-hive.sh > Problems : > 1. /logs/import-hive.log is not created. > 2. Exceptions seen on console while executing the script and in > application.log are attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1619) import-hive.sh script failure
[ https://issues.apache.org/jira/browse/ATLAS-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharmadha Sainath updated ATLAS-1619: - Attachment: (was: atlas exception during import-hive.txt) > import-hive.sh script failure > - > > Key: ATLAS-1619 > URL: https://issues.apache.org/jira/browse/ATLAS-1619 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8-incubating >Reporter: Sharmadha Sainath >Priority: Blocker > Attachments: import-hive console log.txt > > > 1. Created hive tables with hook configuration set in hive. > 2. Removed hook configuration in hive. Restarted hive. > 3. Created tables in hive and ran the import-hive.sh > Problems : > 1. /logs/import-hive.log is not created. > 2. Exceptions seen on console while executing the script and in > application.log are attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1619) import-hive.sh script failure
Sharmadha Sainath created ATLAS-1619: Summary: import-hive.sh script failure Key: ATLAS-1619 URL: https://issues.apache.org/jira/browse/ATLAS-1619 Project: Atlas Issue Type: Bug Components: atlas-core Affects Versions: 0.8-incubating Reporter: Sharmadha Sainath Priority: Blocker Attachments: atlas exception during import-hive.txt, import-hive console log.txt 1. Created hive tables with hook configuration set in hive. 2. Removed hook configuration in hive. Restarted hive. 3. Created tables in hive and ran the import-hive.sh Problems : 1. /logs/import-hive.log is not created. 2. Exceptions seen on console while executing the script and in application.log are attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1500) UI : "retention" attribute value is always shown as date in hive_table properties.
[ https://issues.apache.org/jira/browse/ATLAS-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharmadha Sainath updated ATLAS-1500: - Attachment: ATLAS-1500.patch > UI : "retention" attribute value is always shown as date in hive_table > properties. > -- > > Key: ATLAS-1500 > URL: https://issues.apache.org/jira/browse/ATLAS-1500 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Sharmadha Sainath >Assignee: Sharmadha Sainath >Priority: Minor > Attachments: ATLAS-1500.patch > > > retention is an int attribute in hive_table model . GET Response of the > hive_table entity has correct int value and also gets updated when edited. > But UI always shows a static date value "Thu Jan 01 1970 05:30:00 GMT+0530 > (IST)" for retention. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1500) UI : "retention" attribute value is always shown as date in hive_table properties.
[ https://issues.apache.org/jira/browse/ATLAS-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharmadha Sainath updated ATLAS-1500: - Attachment: (was: ATLAS_1500.patch) > UI : "retention" attribute value is always shown as date in hive_table > properties. > -- > > Key: ATLAS-1500 > URL: https://issues.apache.org/jira/browse/ATLAS-1500 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Sharmadha Sainath >Assignee: Sharmadha Sainath >Priority: Minor > > retention is an int attribute in hive_table model . GET Response of the > hive_table entity has correct int value and also gets updated when edited. > But UI always shows a static date value "Thu Jan 01 1970 05:30:00 GMT+0530 > (IST)" for retention. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1605) Edit Entity in UI : Update button is not enabled when updating attribute of type date
Sharmadha Sainath created ATLAS-1605: Summary: Edit Entity in UI : Update button is not enabled when updating attribute of type date Key: ATLAS-1605 URL: https://issues.apache.org/jira/browse/ATLAS-1605 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 0.8-incubating Reporter: Sharmadha Sainath Assignee: Keval Bhatt On editing attributes of hdfs_path like CreateTime , ModifiedTime which are of type date , Update button is not enabled. This happens for all entity types which have attributes of type date. Editing other types enables the Update button. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1603) Regression : Edit Entity in UI : Unable to edit hive_table entity.
[ https://issues.apache.org/jira/browse/ATLAS-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharmadha Sainath updated ATLAS-1603: - Description: 1.set atlas.ui.editable.entity.types = * 2. Created an hive_table entity table1 in UI. 3. Created an hive_column entity col1 in UI. 4. Edited hive_table table1 in UI and added hive_column col1. 5. On clicking Update button, Notification "Something went wrong" popped up . POST call failed with 500 internal server. Attaching the application logs . 6. Any updates to an hive_table entity are failing. Note: 1.When hive_table is *Created* , this error is not thrown. Only when *Editing* hive_table , the error is thrown. 2.This doesn't happen for other entities like hive_column, hbase_model entities etc., was: 1.set atlas.ui.editable.entity.types = * 2. Created an hive_table entity table1 in UI. 3. Created an hive_column entity col1 in UI. 4. Edited hive_table table1 in UI and added hive_column col1. 5. On clicking Update button, Notification "Something went wrong" popped up . POST call failed with 500 internal server. Attaching the application logs . Note: 1.When hive_table is *Created* with hive_column , this error is not thrown. Only when *Editing* hive_table to add hive_column , the error is thrown. 2.This doesn't happen for other entities in hbase_model. Able to edit hbase_table and add hbase_column_family and edit hbase_column_family and add hbase_column. > Regression : Edit Entity in UI : Unable to edit hive_table entity. > -- > > Key: ATLAS-1603 > URL: https://issues.apache.org/jira/browse/ATLAS-1603 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8-incubating >Reporter: Sharmadha Sainath > Attachments: adding hive_column to hive_table exception.txt > > > 1.set atlas.ui.editable.entity.types = * > 2. Created an hive_table entity table1 in UI. > 3. Created an hive_column entity col1 in UI. > 4. Edited hive_table table1 in UI and added hive_column col1. > 5. On clicking Update button, Notification "Something went wrong" popped up . > POST call failed with 500 internal server. > Attaching the application logs . > 6. Any updates to an hive_table entity are failing. > Note: > 1.When hive_table is *Created* , this error is not thrown. Only when > *Editing* hive_table , the error is thrown. > 2.This doesn't happen for other entities like hive_column, hbase_model > entities etc., -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1603) Regression : Edit Entity in UI : Unable to edit hive_table entity.
[ https://issues.apache.org/jira/browse/ATLAS-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharmadha Sainath updated ATLAS-1603: - Summary: Regression : Edit Entity in UI : Unable to edit hive_table entity. (was: Regression : Edit Entity in UI : Unable to edit hive_table to add hive_column.) > Regression : Edit Entity in UI : Unable to edit hive_table entity. > -- > > Key: ATLAS-1603 > URL: https://issues.apache.org/jira/browse/ATLAS-1603 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8-incubating >Reporter: Sharmadha Sainath > Attachments: adding hive_column to hive_table exception.txt > > > 1.set atlas.ui.editable.entity.types = * > 2. Created an hive_table entity table1 in UI. > 3. Created an hive_column entity col1 in UI. > 4. Edited hive_table table1 in UI and added hive_column col1. > 5. On clicking Update button, Notification "Something went wrong" popped up . > POST call failed with 500 internal server. > Attaching the application logs . > Note: > 1.When hive_table is *Created* with hive_column , this error is not thrown. > Only when *Editing* hive_table to add hive_column , the error is thrown. > 2.This doesn't happen for other entities in hbase_model. Able to edit > hbase_table and add hbase_column_family and edit hbase_column_family and add > hbase_column. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (ATLAS-1604) import-hive.sh fails with Class Not Found Exception.
[
https://issues.apache.org/jira/browse/ATLAS-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharmadha Sainath reassigned ATLAS-1604:
Assignee: Ayub Khan
> import-hive.sh fails with Class Not Found Exception.
>
>
> Key: ATLAS-1604
> URL: https://issues.apache.org/jira/browse/ATLAS-1604
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Affects Versions: 0.8-incubating
>Reporter: Sharmadha Sainath
>Assignee: Ayub Khan
>Priority: Blocker
>
> import_hive.sh script fails with following exception :
> {code}
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/atlas/type/AtlasType
> at
> org.apache.atlas.AtlasClient$EntityResult.fromString(AtlasClient.java:322)
> at
> org.apache.atlas.AtlasClient.extractEntityResult(AtlasClient.java:496)
> at org.apache.atlas.AtlasClient.updateEntity(AtlasClient.java:582)
> at
> org.apache.atlas.hive.bridge.HiveMetaStoreBridge.updateInstance(HiveMetaStoreBridge.java:522)
> at
> org.apache.atlas.hive.bridge.HiveMetaStoreBridge.registerDatabase(HiveMetaStoreBridge.java:175)
> at
> org.apache.atlas.hive.bridge.HiveMetaStoreBridge.importDatabases(HiveMetaStoreBridge.java:140)
> at
> org.apache.atlas.hive.bridge.HiveMetaStoreBridge.importHiveMetadata(HiveMetaStoreBridge.java:134)
> at
> org.apache.atlas.hive.bridge.HiveMetaStoreBridge.main(HiveMetaStoreBridge.java:642)
> Caused by: java.lang.ClassNotFoundException: org.apache.atlas.type.AtlasType
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 8 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (ATLAS-1604) import-hive.sh fails with Class Not Found Exception.
Sharmadha Sainath created ATLAS-1604:
Summary: import-hive.sh fails with Class Not Found Exception.
Key: ATLAS-1604
URL: https://issues.apache.org/jira/browse/ATLAS-1604
Project: Atlas
Issue Type: Bug
Components: atlas-intg
Affects Versions: 0.8-incubating
Reporter: Sharmadha Sainath
Priority: Blocker
import_hive.sh script fails with following exception :
{code}
Exception in thread "main" java.lang.NoClassDefFoundError:
org/apache/atlas/type/AtlasType
at
org.apache.atlas.AtlasClient$EntityResult.fromString(AtlasClient.java:322)
at
org.apache.atlas.AtlasClient.extractEntityResult(AtlasClient.java:496)
at org.apache.atlas.AtlasClient.updateEntity(AtlasClient.java:582)
at
org.apache.atlas.hive.bridge.HiveMetaStoreBridge.updateInstance(HiveMetaStoreBridge.java:522)
at
org.apache.atlas.hive.bridge.HiveMetaStoreBridge.registerDatabase(HiveMetaStoreBridge.java:175)
at
org.apache.atlas.hive.bridge.HiveMetaStoreBridge.importDatabases(HiveMetaStoreBridge.java:140)
at
org.apache.atlas.hive.bridge.HiveMetaStoreBridge.importHiveMetadata(HiveMetaStoreBridge.java:134)
at
org.apache.atlas.hive.bridge.HiveMetaStoreBridge.main(HiveMetaStoreBridge.java:642)
Caused by: java.lang.ClassNotFoundException: org.apache.atlas.type.AtlasType
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 8 more
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (ATLAS-1603) Regression : Edit Entity in UI : Unable to edit hive_table to add hive_column.
Sharmadha Sainath created ATLAS-1603: Summary: Regression : Edit Entity in UI : Unable to edit hive_table to add hive_column. Key: ATLAS-1603 URL: https://issues.apache.org/jira/browse/ATLAS-1603 Project: Atlas Issue Type: Bug Components: atlas-core Affects Versions: 0.8-incubating Reporter: Sharmadha Sainath Attachments: adding hive_column to hive_table exception.txt 1.set atlas.ui.editable.entity.types = * 2. Created an hive_table entity table1 in UI. 3. Created an hive_column entity col1 in UI. 4. Edited hive_table table1 in UI and added hive_column col1. 5. On clicking Update button, Notification "Something went wrong" popped up . POST call failed with 500 internal server. Attaching the application logs . Note: 1.When hive_table is *Created* with hive_column , this error is not thrown. Only when *Editing* hive_table to add hive_column , the error is thrown. 2.This doesn't happen for other entities in hbase_model. Able to edit hbase_table and add hbase_column_family and edit hbase_column_family and add hbase_column. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1595) Create Entity in UI : All attributes are not listed for hdfs_path.
Sharmadha Sainath created ATLAS-1595: Summary: Create Entity in UI : All attributes are not listed for hdfs_path. Key: ATLAS-1595 URL: https://issues.apache.org/jira/browse/ATLAS-1595 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 0.8-incubating Reporter: Sharmadha Sainath Assignee: Keval Bhatt Fix For: 0.8-incubating Attachments: fieldset Not displayed.png 1.Clicked "Create Entity" button. 2.Toggled to "All" from required. 3. Selected the type "hdfs_path" 4. Attributes ClusterName,NumberOfReplicas, ExtendedAttributes which come under fieldset "hdfs_path" are not displayed. Tried to scroll down but it is the end of scroll. This doesn't happen when type is first selected and then toggled to "All". Attached the screenshot when toggled to "All" first and type "hdfs_path" is selected next. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1590) UI : Edit Button is enabled for Deleted entities.
Sharmadha Sainath created ATLAS-1590: Summary: UI : Edit Button is enabled for Deleted entities. Key: ATLAS-1590 URL: https://issues.apache.org/jira/browse/ATLAS-1590 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 0.8-incubating Reporter: Sharmadha Sainath Assignee: Keval Bhatt Deleted a kafka_topic entity using REST API. Add Tag ,Add Term button are not displayed but edit button is displayed and enabled in the detailsPage of deleted kafka_topic entity. Though no update is succeeded when trying to update , the edit button could be removed for deleted entities. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1587) UI Regression : GUID displayed when entities don't have Qualified Name or Name.
Sharmadha Sainath created ATLAS-1587: Summary: UI Regression : GUID displayed when entities don't have Qualified Name or Name. Key: ATLAS-1587 URL: https://issues.apache.org/jira/browse/ATLAS-1587 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 0.8-incubating Reporter: Sharmadha Sainath Fix For: 0.8-incubating Attachments: detailsPage of hive_storagedesc.png, DSL search storm_bolt.png When an entity doesn't have qualified name / name in its model , GUID is displayed. Instead , When name is not present , qualified name can be displayed and vice versa. For example, 1. hive_storagedesc doesn't have Name . Hence , in detailsPage of an hive_storagedesc entity , GUID is displayed. Instead its qualified name can be displayed. 2. storm_bolt doesn't have Qualified Name . Hence while searching storm_bolt in DSL search, results show GUIDs of all storm_bolt entities.Instead its name can be displayed. Attached the screenshots for both. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (ATLAS-1587) UI Regression : GUID displayed when entities don't have Qualified Name or Name.
[ https://issues.apache.org/jira/browse/ATLAS-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharmadha Sainath reassigned ATLAS-1587: Assignee: Keval Bhatt > UI Regression : GUID displayed when entities don't have Qualified Name or > Name. > --- > > Key: ATLAS-1587 > URL: https://issues.apache.org/jira/browse/ATLAS-1587 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.8-incubating >Reporter: Sharmadha Sainath >Assignee: Keval Bhatt > Fix For: 0.8-incubating > > Attachments: detailsPage of hive_storagedesc.png, DSL search > storm_bolt.png > > > When an entity doesn't have qualified name / name in its model , GUID is > displayed. Instead , When name is not present , qualified name can be > displayed and vice versa. > For example, > 1. hive_storagedesc doesn't have Name . Hence , in detailsPage of an > hive_storagedesc entity , GUID is displayed. Instead its qualified name can > be displayed. > 2. storm_bolt doesn't have Qualified Name . Hence while searching storm_bolt > in DSL search, results show GUIDs of all storm_bolt entities.Instead its > name can be displayed. > Attached the screenshots for both. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1578) Problem with Firefox UI : While creating/editing entity in UI ,value to be selected from a drop down list gets auto selected.
Sharmadha Sainath created ATLAS-1578: Summary: Problem with Firefox UI : While creating/editing entity in UI ,value to be selected from a drop down list gets auto selected. Key: ATLAS-1578 URL: https://issues.apache.org/jira/browse/ATLAS-1578 Project: Atlas Issue Type: Bug Components: atlas-webui Environment: Firefox 45.0 Reporter: Sharmadha Sainath Priority: Minor When creating hbase_column_family , hbase_table is one of its attributes which is a drop down list of all hbase_tables. Even before providing the hbase_table, an hbase_table entity is pre selected. This preselection doesn't happen on Chrome or Safari. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1574) Regression : "user" attribute is not found in Audit response for entity not created through UI.
Sharmadha Sainath created ATLAS-1574: Summary: Regression : "user" attribute is not found in Audit response for entity not created through UI. Key: ATLAS-1574 URL: https://issues.apache.org/jira/browse/ATLAS-1574 Project: Atlas Issue Type: Bug Components: atlas-core Affects Versions: 0.8-incubating Reporter: Sharmadha Sainath Fix For: 0.8-incubating Attachments: AuditResposne.png Created hive_table through hook. GET Audit response for the hive_table didn't have user attribute for "Entity Created" audit,whereas for "Tag added" audit , user attribute is present with value "admin". Attached the Screenshot of the Audit response for the above scenario. Entities created through UI have "Entity Created" audit with user attribute. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1502) UI to create/update entities - configuration to restrict entity-types editable via UI
[
https://issues.apache.org/jira/browse/ATLAS-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875373#comment-15875373
]
Sharmadha Sainath commented on ATLAS-1502:
--
Set the following in atlas-application.properties.
{code}
atlas.ui.editable.entity.types=*
{code}
and restarted Atlas. Not able to see all the entity types in the drop down.
What am I missing here ? Opened Atlas in Chrome incognito window hence no
browser cache.
> UI to create/update entities - configuration to restrict entity-types
> editable via UI
> -
>
> Key: ATLAS-1502
> URL: https://issues.apache.org/jira/browse/ATLAS-1502
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: 0.8-incubating
>Reporter: Madhan Neethiraj
>Assignee: Kalyani Kashikar
> Attachments: ATLAS-1502.patch
>
>
> ATLAS-1193 introduced UI to create and update entities. Currently the UI
> allows an user to create entity of any entity-type - including the superTypes
> like Referenceable, Asset, Process, etc. It may not be useful to support
> entity creation of many such entity-types via UI. Restricting the UI to
> support only a subset of entities would make the UI more usable and avoid
> potential confusion.
> It should be possible to configure the list of entity-types supported via a
> configuration, to enable deployments to satisfy specific needs. I would
> suggest to use a configuration like:
> {code}
> atlas.ui.editable.entity.types="type-1,type-2,type3"
> {code}
> - if the configuration is set to an empty value (or not set): UI should not
> support create/edit of any entity
> - if the configuration is set to is set to "*", then UI should allow
> create/edit of any type of entity
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (ATLAS-1573) Regression : Full text search returns empty results for any query
Sharmadha Sainath created ATLAS-1573:
Summary: Regression : Full text search returns empty results for
any query
Key: ATLAS-1573
URL: https://issues.apache.org/jira/browse/ATLAS-1573
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 0.8-incubating
Reporter: Sharmadha Sainath
Priority: Blocker
Fix For: 0.8-incubating
DSL search works fine.Any Full text search is not yielding any result. GET
response of the Full text search is empty.
Both v2 entity API response and old API response are empty
{code}
/api/atlas/v2/search/fulltext?limit=25&query=topic1
/api/atlas/discovery/search/fulltext?query=topic1
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (ATLAS-1562) Not able to delete hbase_column_family once associated to the hbase_table.
Sharmadha Sainath created ATLAS-1562: Summary: Not able to delete hbase_column_family once associated to the hbase_table. Key: ATLAS-1562 URL: https://issues.apache.org/jira/browse/ATLAS-1562 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 0.8-incubating Reporter: Sharmadha Sainath Assignee: Keval Bhatt Created 1. hbase_table "table1" 2. hbase_column_family "colfam1" wit hbase_table as "table1" 3. Edited "table1" and added "colfam1" . Column family is added. 4. Edited "table1" and removed "colfam1". Column family is not removed and still associated to table1. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1561) 'Entity Created/Updated' audit logs are not logged when Creating Entity in UI.
Sharmadha Sainath created ATLAS-1561: Summary: 'Entity Created/Updated' audit logs are not logged when Creating Entity in UI. Key: ATLAS-1561 URL: https://issues.apache.org/jira/browse/ATLAS-1561 Project: Atlas Issue Type: Bug Affects Versions: 0.8-incubating Reporter: Sharmadha Sainath Assignee: Keval Bhatt Fix For: 0.8-incubating For entities like hdfs_path,kafka_topic etc., created in UI, Entity Created /Entity Updated logs are not present in Audits tab of the respective entity. GET Response /api/atlas/entities/guid/audit is also empty. But after entity creation , audits for tag addition , tag deletion are logged. This issue is not seen in hive_table created via hook. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1533) Entity creation in UI fails with "javax.ws.rs.WebApplicationException"
[
https://issues.apache.org/jira/browse/ATLAS-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15861021#comment-15861021
]
Sharmadha Sainath commented on ATLAS-1533:
--
[~apoorvnaik] , stack trace attached in the JIRA description is the full stack
trace that comes when creating entity like "kafka_topic" in UI.
> Entity creation in UI fails with "javax.ws.rs.WebApplicationException"
> --
>
> Key: ATLAS-1533
> URL: https://issues.apache.org/jira/browse/ATLAS-1533
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Sharmadha Sainath
>Priority: Blocker
> Fix For: 0.8-incubating
>
>
> Entity creation in UI fails with notification "Something went wrong" and the
> following exception stack trace in application.logs.
> {code}
> Error handling a request: 5a3c7213b5168680 (ExceptionMapperUtil:32)
> javax.ws.rs.WebApplicationException
> at
> com.sun.jersey.server.impl.uri.rules.TerminatingRule.accept(TerminatingRule.java:66)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:286)
> at
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:276)
> at
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:181)
> at
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)
> at
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)
> at
> org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:77)
> at
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)
> at
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:120)
> at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:135)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
> at
> org.apache.atlas.web.filters.AtlasAuthorizationFilter.doFilter(AtlasAuthorizationFilter.java:154)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118)
> at
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:103)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.apache.atlas.web.filters.AtlasCSRFPreventionFilter$ServletFilterHttpInteraction.proceed(AtlasCSRFPreventionFilter.
