[jira] [Created] (ATLAS-3350) Add better logging in AtlasAuthenticationFilter
Sharmadha Sainath created ATLAS-3350:
Summary: Add better logging in AtlasAuthenticationFilter
Key: ATLAS-3350
URL: https://issues.apache.org/jira/browse/ATLAS-3350
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Sharmadha Sainath
Need better/more logging for AtlasAuthenticationFilter.
Certain scenario for which Atlas throws 500 server error , Atlas debug logs say
triggering authentication but no other logs follow that:
{code}
2019-07-26 07:08:51,327 DEBUG - [pool-2-thread-1:] ~ Request
[http://host:21000/api/atlas/admin/server/aasha$mycluster0] triggering
authentication (AtlasAuthenticationFilter:410)
2019-07-26 07:08:51,471 DEBUG - [pool-2-thread-3:] ~ Cleaning stale
transactions (StaleTransactionCleanupFilter:53)
2019-07-26 07:08:51,472 DEBUG - [pool-2-thread-3:] ~ Request
[http://host:21000/api/atlas/admin/server/aasha$mycluster0] triggering
authentication (AtlasAuthenticationFilter:410)
2019-07-26 07:08:52,781 DEBUG - [main-SendThread(master0.cloudera.site:2181):]
~ Got ping response for sessionid: 0x16c1852da6bfe40 after 0ms
(ClientCnxn$SendThread:742)
2019-07-26 07:08:52,907 DEBUG - [Connection evictor:] ~ Closing expired
connections (PoolingHttpClientConnectionManager:414)
{code}
CC : [~nixonrodrigues]
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Created] (ATLAS-3310) Relationships : After updating a bigint attribute , any operation on relationship instance,entity throws 500 internal server exception.
Sharmadha Sainath created ATLAS-3310:
Summary: Relationships : After updating a bigint attribute , any
operation on relationship instance,entity throws 500 internal server exception.
Key: ATLAS-3310
URL: https://issues.apache.org/jira/browse/ATLAS-3310
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Sharmadha Sainath
After updating bigint attribute , any operation (example : GET) on the
relationship fails throwing 500 internal server exception with the following
stack trace.
Stack trace :
{code:java}
2019-05-20 06:19:28,592 ERROR - [pool-2-thread-3 -
74ed4949-00ff-4f6d-87cb-e287684b55b8:] ~ Error handling a request:
aceb2d520cb74b37 (ExceptionMapperUtil:32)
java.lang.ArrayIndexOutOfBoundsException: Required size [1] exceeds actual
remaining size [0]
at
org.janusgraph.diskstorage.util.StaticArrayBuffer.require(StaticArrayBuffer.java:94)
at
org.janusgraph.diskstorage.util.StaticArrayBuffer.getByte(StaticArrayBuffer.java:170)
at
org.janusgraph.diskstorage.util.StaticArrayBuffer.getBytes(StaticArrayBuffer.java:253)
at
org.janusgraph.diskstorage.util.ReadArrayBuffer.getBytes(ReadArrayBuffer.java:120)
at
org.janusgraph.graphdb.database.serialize.attribute.ByteArraySerializer.read(ByteArraySerializer.java:46)
at
org.apache.atlas.repository.graphdb.janus.serializer.BigIntegerSerializer.read(BigIntegerSerializer.java:36)
at
org.apache.atlas.repository.graphdb.janus.serializer.BigIntegerSerializer.read(BigIntegerSerializer.java:30)
at
org.janusgraph.graphdb.database.serialize.StandardSerializer.readObjectNotNullInternal(StandardSerializer.java:265)
at
org.janusgraph.graphdb.database.serialize.StandardSerializer.readObjectInternal(StandardSerializer.java:255)
at
org.janusgraph.graphdb.database.serialize.StandardSerializer.readObject(StandardSerializer.java:235)
at
org.janusgraph.graphdb.database.EdgeSerializer.readPropertyValue(EdgeSerializer.java:205)
at
org.janusgraph.graphdb.database.EdgeSerializer.readInline(EdgeSerializer.java:191)
at
org.janusgraph.graphdb.database.EdgeSerializer.parseRelation(EdgeSerializer.java:162)
at
org.janusgraph.graphdb.database.EdgeSerializer.readRelation(EdgeSerializer.java:73)
at
org.janusgraph.graphdb.transaction.RelationConstructor.readRelationCache(RelationConstructor.java:41)
at
org.janusgraph.graphdb.relations.CacheEdge.getPropertyMap(CacheEdge.java:101)
at
org.janusgraph.graphdb.relations.CacheEdge.getValueDirect(CacheEdge.java:108)
at
org.janusgraph.graphdb.relations.AbstractTypedRelation.lambda$properties$1(AbstractTypedRelation.java:166)
at
java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:174)
at
java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
at
java.util.Spliterators$ArraySpliterator.tryAdvance(Spliterators.java:958)
at
java.util.stream.StreamSpliterators$WrappingSpliterator.lambda$initPartialTraversalState$0(StreamSpliterators.java:294)
at
java.util.stream.StreamSpliterators$AbstractWrappingSpliterator.fillBuffer(StreamSpliterators.java:206)
at
java.util.stream.StreamSpliterators$AbstractWrappingSpliterator.doAdvance(StreamSpliterators.java:161)
at
java.util.stream.StreamSpliterators$WrappingSpliterator.tryAdvance(StreamSpliterators.java:300)
at java.util.Spliterators$1Adapter.hasNext(Spliterators.java:681)
at
org.apache.tinkerpop.gremlin.structure.Element.property(Element.java:79)
at
org.apache.atlas.repository.graphdb.janus.AtlasJanusElement.getProperty(AtlasJanusElement.java:65)
at
org.apache.atlas.repository.store.graph.v2.AtlasGraphUtilsV2.getTypeName(AtlasGraphUtilsV2.java:126)
at
org.apache.atlas.repository.store.graph.v2.AtlasRelationshipStoreV2.update(AtlasRelationshipStoreV2.java:148)
at
org.apache.atlas.repository.store.graph.v2.AtlasRelationshipStoreV2$$FastClassBySpringCGLIB$$a8165974.invoke()
at
org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
at
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:736)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
at
org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:80)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at
org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:671)
at
org.apache.atlas.repository.store.graph.v2.AtlasRelationshipStoreV2$$EnhancerBySpringCGLIB$$a12f9384.update()
at
[jira] [Comment Edited] (ATLAS-3177) Regression , Export : changeMarker is not set right - set to older value compared to entity's lastModifedTime
[
https://issues.apache.org/jira/browse/ATLAS-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16850538#comment-16850538
]
Sharmadha Sainath edited comment on ATLAS-3177 at 5/29/19 6:31 AM:
---
[~ashutoshm] , But changeMarker is always set to value even older than the
entity's creation timestamp.I tried quite many times. Due to this , incremental
export is not adding any value.
Also could you please explain what is request timestamp ? Is it the latest time
stamp the entity was accessed / requested ?
was (Author: ssainath):
[~ashutoshm] , But changeMarker is always set to value even older than the
entity's creation timestamp.I tried quite many times. Due to this , incremental
export is not adding any value.
> Regression , Export : changeMarker is not set right - set to older value
> compared to entity's lastModifedTime
> -
>
> Key: ATLAS-3177
> URL: https://issues.apache.org/jira/browse/ATLAS-3177
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 1.1.0
>Reporter: Sharmadha Sainath
>Priority: Major
> Fix For: 1.1.0, trunk
>
> Attachments: db_axyz.zip, db_def.json
>
>
> Export request body :
> {code}
> {"itemsToExport": [{"typeName": "hive_db", "uniqueAttributes":
> {"qualifiedName": "database_rbltx@mycluster0"}}], "options": {"fetchType":
> "incremental", "changeMarker": 0, "replicatedTo": "mycluster1"}}
> {code}
> The db's createTime is 1556276114134 (Friday, April 26, 2019 4:25:14.134 PM
> GMT+05:30)
> updatedTime is 1556276125588 (Friday, April 26, 2019 4:25:25.588 PM GMT+05:30)
> The changeMarker in exported zip file is 1556187028462 (Thursday, April 25,
> 2019 3:40:28.462 PM GMT+05:30)
> due to this unmodified entities are also exported everytime due to
> incremental export.
> Attaching the entity definition of db entity and the exported zip.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ATLAS-3177) Regression , Export : changeMarker is not set right - set to older value compared to entity's lastModifedTime
[
https://issues.apache.org/jira/browse/ATLAS-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16850538#comment-16850538
]
Sharmadha Sainath commented on ATLAS-3177:
--
[~ashutoshm] , But changeMarker is always set to value even older than the
entity's creation timestamp.I tried quite many times. Due to this , incremental
export is not adding any value.
> Regression , Export : changeMarker is not set right - set to older value
> compared to entity's lastModifedTime
> -
>
> Key: ATLAS-3177
> URL: https://issues.apache.org/jira/browse/ATLAS-3177
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 1.1.0
>Reporter: Sharmadha Sainath
>Priority: Major
> Fix For: 1.1.0, trunk
>
> Attachments: db_axyz.zip, db_def.json
>
>
> Export request body :
> {code}
> {"itemsToExport": [{"typeName": "hive_db", "uniqueAttributes":
> {"qualifiedName": "database_rbltx@mycluster0"}}], "options": {"fetchType":
> "incremental", "changeMarker": 0, "replicatedTo": "mycluster1"}}
> {code}
> The db's createTime is 1556276114134 (Friday, April 26, 2019 4:25:14.134 PM
> GMT+05:30)
> updatedTime is 1556276125588 (Friday, April 26, 2019 4:25:25.588 PM GMT+05:30)
> The changeMarker in exported zip file is 1556187028462 (Thursday, April 25,
> 2019 3:40:28.462 PM GMT+05:30)
> due to this unmodified entities are also exported everytime due to
> incremental export.
> Attaching the entity definition of db entity and the exported zip.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ATLAS-3233) Relationships, Export & Import : Issue with ACTIVE and DELETED relationship-def instances
Sharmadha Sainath created ATLAS-3233: Summary: Relationships, Export & Import : Issue with ACTIVE and DELETED relationship-def instances Key: ATLAS-3233 URL: https://issues.apache.org/jira/browse/ATLAS-3233 Project: Atlas Issue Type: Bug Components: atlas-core Affects Versions: 1.0.0 Reporter: Sharmadha Sainath Fix For: 2.0.0 1. In source cluster , create 2 types and a relationship-def between them. 2. Create 2 entities and create relationship instance between them. (relationship_guid_1 is created and it is ACTIVE) 3. Export & Import entity1. 4. On target cluster , relationship_guid_1 is imported and it is ACTIVE. 5. Now, on source cluster , delete relationship_guid_1 and create a new relationship between entity1 and entity2. 6. In source cluster , relationship_guid_1 is DELETED and new relationship_guid_2 is ACTIVE. 7. Export and Import the entity1 to target cluster. 8. In target cluster , relationship_guid_1 is still ACTIVE and relationship_guid_2 is not imported at all . (GET on relationship_guid_2 throws 404 on target cluster) 9. In the exported zip , there is no information about relationship_guid_1 but only about relationship_guid_2. CC : [~ashutoshm] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3232) Relationships, Export & Import : Updates to relationshipDef are not honored during import
[ https://issues.apache.org/jira/browse/ATLAS-3232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharmadha Sainath updated ATLAS-3232: - Description: 1. In source cluster , updated relationshipDef "hive_table_db" propagateTags to "ONE_TO_TWO" from NONE and exported. 2.In export zip , atlas-typesdef.json has "ONE_TO_TWO" propagateTags value for "hive_table_db" . 3. But in the import cluster, propagateTags value for hive_table_db is NONE still. In the import options , provided updateTypeDefinition to True too. CC : [~ashutoshm] was: 1. In source cluster , updated relationshipDef "hive_db_columns" propagateTags to "ONE_TO_TWO" from NONE and exported. 2.In export zip , atlas-typesdef.json has "ONE_TO_TWO" propagateTags value for "hive_db_columns" . 3. But in the import cluster, propagateTags value for hive_db_columns is NONE still. In the import options , provided updateTypeDefinition to True too. CC : [~ashutoshm] > Relationships, Export & Import : Updates to relationshipDef are not honored > during import > - > > Key: ATLAS-3232 > URL: https://issues.apache.org/jira/browse/ATLAS-3232 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Sharmadha Sainath >Priority: Major > Fix For: 2.0.0 > > > 1. In source cluster , updated relationshipDef "hive_table_db" propagateTags > to "ONE_TO_TWO" from NONE and exported. > 2.In export zip , atlas-typesdef.json has "ONE_TO_TWO" propagateTags value > for "hive_table_db" . > 3. But in the import cluster, propagateTags value for hive_table_db is NONE > still. In the import options , provided updateTypeDefinition to True too. > CC : [~ashutoshm] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3232) Relationships, Export & Import : Updates to relationshipDef are not honored during import
Sharmadha Sainath created ATLAS-3232: Summary: Relationships, Export & Import : Updates to relationshipDef are not honored during import Key: ATLAS-3232 URL: https://issues.apache.org/jira/browse/ATLAS-3232 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Sharmadha Sainath Fix For: 2.0.0 1. In source cluster , updated relationshipDef "hive_db_columns" propagateTags to "ONE_TO_TWO" from NONE and exported. 2.In export zip , atlas-typesdef.json has "ONE_TO_TWO" propagateTags value for "hive_db_columns" . 3. But in the import cluster, propagateTags value for hive_db_columns is NONE still. In the import options , provided updateTypeDefinition to True too. CC : [~ashutoshm] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3187) Regression, Relationship updates : In GET entity definition of a deleted table, columns,sd etc., are empty
Sharmadha Sainath created ATLAS-3187:
Summary: Regression, Relationship updates : In GET entity
definition of a deleted table, columns,sd etc., are empty
Key: ATLAS-3187
URL: https://issues.apache.org/jira/browse/ATLAS-3187
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 2.0.0
Reporter: Sharmadha Sainath
Fix For: 2.0.0
Attachments: table_entity_def.json
Adding the table_entity_def["entity"]["attributes"]:
Here , table is deleted , but the columns array and sd are [] and null
respectively. Expected is all entities in DELETED state.
Attaching the complete table definition :
{code}
attributes: {
owner: "hrt_qa",
temporary: false,
lastAccessTime: 1556788686000,
aliases: null,
replicatedTo: null,
replicatedFrom: null,
qualifiedName: "default.table1@cl1",
columns: [ ],
description: null,
viewExpandedText: null,
tableType: "MANAGED_TABLE",
sd: null,
createTime: 1556788686000,
name: "table1",
comment: null,
partitionKeys: [ ],
parameters: {
totalSize: "0",
numRows: "0",
rawDataSize: "0",
transactional_properties: "default",
COLUMN_STATS_ACCURATE: "{"BASIC_STATS":"true","COLUMN_STATS":{"id":"true"}}",
numFiles: "0",
transient_lastDdlTime: "1556788686",
bucketing_version: "2",
transactional: "true"
},
retention: 0,
viewOriginalText: null,
db: {
guid: "ab02dd3b-1d1c-4522-8c2c-0fa60d82fcbe",
typeName: "hive_db"
}
}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ATLAS-3177) Regression , Export : changeMarker is not set right - set to older value compared to entity's lastModifedTime
Sharmadha Sainath created ATLAS-3177:
Summary: Regression , Export : changeMarker is not set right - set
to older value compared to entity's lastModifedTime
Key: ATLAS-3177
URL: https://issues.apache.org/jira/browse/ATLAS-3177
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 1.1.0
Reporter: Sharmadha Sainath
Fix For: 2.0.0, 1.1.0
Attachments: db_axyz.zip, db_def.json
Export request body :
{code}
{"itemsToExport": [{"typeName": "hive_db", "uniqueAttributes":
{"qualifiedName": "database_rbltx@mycluster0"}}], "options": {"fetchType":
"incremental", "changeMarker": 0, "replicatedTo": "mycluster1"}}
{code}
The db's createTime is 1556276114134 (Friday, April 26, 2019 4:25:14.134 PM
GMT+05:30)
updatedTime is 1556276125588 (Friday, April 26, 2019 4:25:25.588 PM GMT+05:30)
The changeMarker in exported zip file is 1556187028462 (Thursday, April 25,
2019 3:40:28.462 PM GMT+05:30)
due to this unmodified entities are also exported everytime due to incremental
export.
Attaching the entity definition of db entity and the exported zip.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ATLAS-3176) Regression , Export : Export zip doesn't contain all entities which are listed in atlas-export-order.json
Sharmadha Sainath created ATLAS-3176: Summary: Regression , Export : Export zip doesn't contain all entities which are listed in atlas-export-order.json Key: ATLAS-3176 URL: https://issues.apache.org/jira/browse/ATLAS-3176 Project: Atlas Issue Type: Bug Components: atlas-core Affects Versions: 1.1.0, 2.0.0 Reporter: Sharmadha Sainath Fix For: 2.0.0 Attachments: export.zip In Previous versions , entities listed in atlas-export-order.json are present in zip as .json. In recent versions, hive_column_lineage entities are missing. But this doesn't affect import. The lineage is created between the columns without any issue. The hive_column_lineage information is present in entity definition of hive_table and hive_process so it creates the hive_column_lineage. Attaching the zip file. CC : [~ashutoshm] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (ATLAS-3108) Unable search terms at a subcategory glossary
[ https://issues.apache.org/jira/browse/ATLAS-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16806400#comment-16806400 ] Sharmadha Sainath edited comment on ATLAS-3108 at 4/1/19 5:42 AM: -- [~Raymond_C] , >> After creating category and subcategory via AtlasUI >> (http://sandbox-hdp.hortonworks.com:21000/), at the one subcategory, unable >> to search any terms. In the attached screenshot ,I see that there is no sub category created yet for "2nd deliveryLeadTime". Here ,Time is the Glossary and "2nd deliveryLeadTime" is the category. I see you're trying to search "deliveryLeadTime" - which is a Glossary. So , if you want to create a term under Time , switch to "Terms" in the toggle , Create a term under the Glossary. Now to assign Term to Category, you can either do that in "Terms" or toggle back to "Category". By your example , toggle to "Category" , you will see "Terms +" (Terms Assign) button . Click on that and search the term you want to assign the category to. Please let me know if you still find issues. Also , refer to http://atlas.apache.org/Glossary.html for more detailed information. was (Author: ssainath): [~Raymond_C] , >> After creating category and subcategory via AtlasUI >> (http://sandbox-hdp.hortonworks.com:21000/), at the one subcategory, unable >> to search any terms. In the attached screenshot ,I see that there is no sub category created yet for "2nd deliveryLeadTime". Here ,Time is the Glossary and 2nd "deliveryLeadTime" is the category. I see you're trying to search "deliveryLeadTime" - which is a Glossary. So , if you want to create a term under Time , switch to "Terms" in the toggle , Create a term under the Glossary. Now to assign Term to Category, you can either do that in "Terms" or toggle back to "Category". By your example , toggle to "Category" , you will see "Terms +" (Terms Assign) button . Click on that and search the term you want to assign the category to. Please let me know if you still find issues. Also , refer to http://atlas.apache.org/Glossary.html for more detailed information. > Unable search terms at a subcategory glossary > - > > Key: ATLAS-3108 > URL: https://issues.apache.org/jira/browse/ATLAS-3108 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 1.1.0 >Reporter: Raymond C >Priority: Major > Labels: beginner > Attachments: image-2019-03-31-12-51-55-042.png > > > 1 Launching HDP Sandbox 3.0. > 2 After creating category and subcategory via AtlasUI > ([http://sandbox-hdp.hortonworks.com:21000/]), at the one subcategory, unable > to search any terms. > 3 Typed one existing term, but did not show any term on the search bar. Also > the Assign button is invalid. > !image-2019-03-31-12-51-55-042.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3108) Unable search terms at a subcategory glossary
[ https://issues.apache.org/jira/browse/ATLAS-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16806400#comment-16806400 ] Sharmadha Sainath commented on ATLAS-3108: -- [~Raymond_C] , >> After creating category and subcategory via AtlasUI >> (http://sandbox-hdp.hortonworks.com:21000/), at the one subcategory, unable >> to search any terms. In the attached screenshot ,I see that there is no sub category created yet for "2nd deliveryLeadTime". Here ,Time is the Glossary and 2nd "deliveryLeadTime" is the category. I see you're trying to search "deliveryLeadTime" - which is a Glossary. So , if you want to create a term under Time , switch to "Terms" in the toggle , Create a term under the Glossary. Now to assign Term to Category, you can either do that in "Terms" or toggle back to "Category". By your example , toggle to "Category" , you will see "Terms +" (Terms Assign) button . Click on that and search the term you want to assign the category to. Please let me know if you still find issues. Also , refer to http://atlas.apache.org/Glossary.html for more detailed information. > Unable search terms at a subcategory glossary > - > > Key: ATLAS-3108 > URL: https://issues.apache.org/jira/browse/ATLAS-3108 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 1.1.0 >Reporter: Raymond C >Priority: Major > Labels: beginner > Attachments: image-2019-03-31-12-51-55-042.png > > > 1 Launching HDP Sandbox 3.0. > 2 After creating category and subcategory via AtlasUI > ([http://sandbox-hdp.hortonworks.com:21000/]), at the one subcategory, unable > to search any terms. > 3 Typed one existing term, but did not show any term on the search bar. Also > the Assign button is invalid. > !image-2019-03-31-12-51-55-042.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3101) UI,Regression : Unable to search by _CLASSIFIED
Sharmadha Sainath created ATLAS-3101: Summary: UI,Regression : Unable to search by _CLASSIFIED Key: ATLAS-3101 URL: https://issues.apache.org/jira/browse/ATLAS-3101 Project: Atlas Issue Type: Bug Components: atlas-webui Reporter: Sharmadha Sainath On selecting _CLASSIFIED in classifications dropdown , "Search" button is not enabled. After selecting _CLASSIFIED in classifications dropdown, selecting a type (say hive_table) from types list , clears the _CLASSIFIED in classifications. CC : [~kevalbhatt] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3086) Regression : Atlas Hive Hook doesn't capture insert into table values() queries
Sharmadha Sainath created ATLAS-3086: Summary: Regression : Atlas Hive Hook doesn't capture insert into table values() queries Key: ATLAS-3086 URL: https://issues.apache.org/jira/browse/ATLAS-3086 Project: Atlas Issue Type: Bug Components: atlas-intg Affects Versions: 1.0.0 Reporter: Sharmadha Sainath Fix For: 2.0.0 Atlas Hive Hook doesn't capture the query "insert into table values()" . This is a regression as this event was captured in 0.8 Other queries like "from table1 a insert overwrite table bkp_table select a.id", "insert into tableB select c1,c2 from tableA" , information is captured and lineage is created in 1.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3068) Regression : Removal of ownedRef/inverseRef constraints in hive types causes related entities missing from the response's "attributes"
Sharmadha Sainath created ATLAS-3068:
Summary: Regression : Removal of ownedRef/inverseRef constraints
in hive types causes related entities missing from the response's "attributes"
Key: ATLAS-3068
URL: https://issues.apache.org/jira/browse/ATLAS-3068
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 1.2.0, 2.0.0
Reporter: Sharmadha Sainath
Fix For: 1.2.0, 2.0.0
In GET entity response of hive_table , "attributes" doesn't have table, column
attributes anymore due to recent change
[ATLAS-3067|https://issues.apache.org/jira/browse/ATLAS-3067].
Example :
{code}
attributes: {
owner: "admin",
temporary: false,
lastAccessTime: 769588200,
aliases: null,
replicatedTo: null,
replicatedFrom: null,
qualifiedName: "default.hive_table_nogsc_9@cl1",
description: null,
viewExpandedText: null,
tableType: "MANAGED_TABLE",
createTime: 1552306685000,
name: "hive_table_nogsc_9",
comment: null,
parameters: {
totalSize: "0",
numRows: "0",
rawDataSize: "0",
transactional_properties: "default",
COLUMN_STATS_ACCURATE:
"{"BASIC_STATS":"true","COLUMN_STATS":{"id":"true","name":"true"}}",
numFiles: "0",
transient_lastDdlTime: "1552306685",
bucketing_version: "2",
transactional: "true"
},
retention: 1,
viewOriginalText: null
},
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ATLAS-2900) Regression : Import fails with Error converting file to JSON
Sharmadha Sainath created ATLAS-2900:
Summary: Regression : Import fails with Error converting file to
JSON
Key: ATLAS-2900
URL: https://issues.apache.org/jira/browse/ATLAS-2900
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Sharmadha Sainath
Attachments: uPqvN.zip
On Importing the attached zip file , request fails with
{code}
2018-09-26 23:02:50,705 INFO - [pool-2-thread-18 -
84ea8d84-ead8-428d-a4db-4451812dd241:] ~ ==> import(user=admin,
from=10.22.16.153, request=AtlasImportRequest{options={}}) (ImportService:89)
2018-09-26 23:02:50,864 INFO - [pool-2-thread-18 -
84ea8d84-ead8-428d-a4db-4451812dd241:] ~ bulkImport(): progress: 14% (of 7) -
entity:last-imported:hive_table:[1]:(d7773c32-ce56-4d8a-96c1-5a4aa97e982e)
(AtlasEntityStoreV1:146)
2018-09-26 23:02:50,865 ERROR - [pool-2-thread-18 -
84ea8d84-ead8-428d-a4db-4451812dd241:] ~ getNextEntityWithExtInfo
(ZipSource:213)
org.apache.atlas.exception.AtlasBaseException: Error converting file to JSON.
at
org.apache.atlas.repository.impexp.ZipSource.convertFromJson(ZipSource.java:177)
at
org.apache.atlas.repository.impexp.ZipSource.getEntityWithExtInfo(ZipSource.java:139)
at
org.apache.atlas.repository.impexp.ZipSource.getNextEntityWithExtInfo(ZipSource.java:211)
at
org.apache.atlas.repository.store.graph.v1.BulkImporterImpl$EntityImportStreamWithResidualList.getNextEntityWithExtInfo(BulkImporterImpl.java:183)
at
org.apache.atlas.repository.store.graph.v1.BulkImporterImpl.bulkImport(BulkImporterImpl.java:72)
at
org.apache.atlas.repository.impexp.ImportService.processEntities(ImportService.java:213)
at
org.apache.atlas.repository.impexp.ImportService.run(ImportService.java:100)
at
org.apache.atlas.web.resources.AdminResource.importData(AdminResource.java:390)
at sun.reflect.GeneratedMethodAccessor227.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
at
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
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
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1507)
at
org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:76)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1495)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:317)
at
org.apache.atlas.web.filters.AtlasAuthorizationFilter.doFilter(AtlasAuthorizationFilter.java:157)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
at
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:127)
at
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:91)
at
[jira] [Created] (ATLAS-2899) Regression : When export "options" is provided null , export fails with NPE at getSkipLineageOptionValue
Sharmadha Sainath created ATLAS-2899:
Summary: Regression : When export "options" is provided null ,
export fails with NPE at getSkipLineageOptionValue
Key: ATLAS-2899
URL: https://issues.apache.org/jira/browse/ATLAS-2899
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Sharmadha Sainath
With the following export "options" , export fails with NPE at
getSkipLineageOptionValue(AtlasExportRequest.java:97) :
{code}
{
"itemsToExport":[
{
"typeName":"hdfs_path",
"uniqueAttributes":{
"qualifiedName":"/atlas"
}
}
],
"options":null
}
{code}
whereas , when no options key is specified or some valid options are provided ,
export succeeds.
Complete exception stack trace :
{code}
2018-09-26 20:23:30,967 ERROR - [pool-2-thread-18 -
76af7fbc-cdc6-4196-9273-bc8b40b62d15:] ~ Error handling a request:
eca69d150a7a5b5c (ExceptionMapperUtil:32)
java.lang.NullPointerException
at
org.apache.atlas.model.impexp.AtlasExportRequest.getSkipLineageOptionValue(AtlasExportRequest.java:97)
at
org.apache.atlas.repository.impexp.ExportService$ExportContext.(ExportService.java:633)
at
org.apache.atlas.repository.impexp.ExportService.run(ExportService.java:97)
at
org.apache.atlas.web.resources.AdminResource.export(AdminResource.java:342)
at sun.reflect.GeneratedMethodAccessor200.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
at
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
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
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1507)
at
org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:76)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1495)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:317)
at
org.apache.atlas.web.filters.AtlasAuthorizationFilter.doFilter(AtlasAuthorizationFilter.java:157)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
at
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:127)
at
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:91)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
at
org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:114)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
at
org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:137)
at
[jira] [Created] (ATLAS-2826) Saving Search fails with 403 auth error after the new relationship auth changes
Sharmadha Sainath created ATLAS-2826: Summary: Saving Search fails with 403 auth error after the new relationship auth changes Key: ATLAS-2826 URL: https://issues.apache.org/jira/browse/ATLAS-2826 Project: Atlas Issue Type: Bug Components: atlas-core Affects Versions: 1.1.0 Reporter: Sharmadha Sainath Attachments: SaveSearchLog.txt Saving search as any user fails with 403 after new fine grained authorization support added for relationship. Attached the complete stack trace. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2697) V2 Notifications : "Propagated classification added" audit message is present instead of "classification added"
Sharmadha Sainath created ATLAS-2697: Summary: V2 Notifications : "Propagated classification added" audit message is present instead of "classification added" Key: ATLAS-2697 URL: https://issues.apache.org/jira/browse/ATLAS-2697 Project: Atlas Issue Type: Bug Components: atlas-core Affects Versions: 1.0.0 Reporter: Sharmadha Sainath With V2 notifications ,when tag is added to an entity , instead of "classification added" audit , "Propagated classification added" audit message is present. CC : [~sarath.ku...@gmail.com] [~nixonrodrigues] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2475) HBase Atlas import utility : importing using -t default:table fails when namespace is default
Sharmadha Sainath created ATLAS-2475:
Summary: HBase Atlas import utility : importing using -t
default:table fails when namespace is default
Key: ATLAS-2475
URL: https://issues.apache.org/jira/browse/ATLAS-2475
Project: Atlas
Issue Type: Bug
Components: atlas-intg
Affects Versions: 1.0.0
Reporter: Sharmadha Sainath
Fix For: 1.0.0
Running following scripts work :
./import-hbase.sh -t ns1:table5
./import-hbase.sh -t table2
But following import script specifying default namespace doesn't work :
./import-hbase.sh -t default:table2
and throws following exception :
{code}
Exception in thread "main" org.apache.atlas.hook.AtlasHookException:
ImportHBaseEntities failed.
at
org.apache.atlas.hbase.util.ImportHBaseEntities.main(ImportHBaseEntities.java:57)
Caused by: java.lang.NullPointerException
at
org.apache.atlas.hbase.util.ImportHBaseEntities.importTable(ImportHBaseEntities.java:115)
at
org.apache.atlas.hbase.util.ImportHBaseEntities.execute(ImportHBaseEntities.java:88)
at
org.apache.atlas.hbase.util.ImportHBaseEntities.main(ImportHBaseEntities.java:54)
Failed to import HBase Data Model!!!
{code}
In HBase shell , it is possible to create table in default namespace by
specifying the default namespace explicitly :
> create 'default:table2,'cf1'
so ,expectation is that importing by explicitly specifying default namespace
also should work.
CC : [~rmani]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (ATLAS-2453) Atlas HBase Hook : Datatype of maxFileSize should be Long instead of Integer
[ https://issues.apache.org/jira/browse/ATLAS-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16367478#comment-16367478 ] Sharmadha Sainath edited comment on ATLAS-2453 at 2/16/18 3:38 PM: --- Review Request : https://reviews.apache.org/r/65688/ CC : [~rmani] was (Author: ssainath): Review Request : https://reviews.apache.org/r/65688/ > Atlas HBase Hook : Datatype of maxFileSize should be Long instead of Integer > > > Key: ATLAS-2453 > URL: https://issues.apache.org/jira/browse/ATLAS-2453 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Reporter: Sharmadha Sainath >Priority: Major > Attachments: ATLAS-2453.patch > > > maxFileSize attribute of hbase_table should be of type long. > Currently it is an Integer , hence , when creating/updating hbase_table with > maxFileSize value more than integer's range , data between HBase and Atlas is > inconsistent. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2453) Atlas HBase Hook : Datatype of maxFileSize should be Long instead of Integer
[ https://issues.apache.org/jira/browse/ATLAS-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16367478#comment-16367478 ] Sharmadha Sainath commented on ATLAS-2453: -- Review Request : https://reviews.apache.org/r/65688/ > Atlas HBase Hook : Datatype of maxFileSize should be Long instead of Integer > > > Key: ATLAS-2453 > URL: https://issues.apache.org/jira/browse/ATLAS-2453 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Reporter: Sharmadha Sainath >Priority: Major > Attachments: ATLAS-2453.patch > > > maxFileSize attribute of hbase_table should be of type long. > Currently it is an Integer , hence , when creating/updating hbase_table with > maxFileSize value more than integer's range , data between HBase and Atlas is > inconsistent. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2453) Atlas HBase Hook : Datatype of maxFileSize should be Long instead of Integer
[ https://issues.apache.org/jira/browse/ATLAS-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharmadha Sainath updated ATLAS-2453: - Attachment: ATLAS-2453.patch > Atlas HBase Hook : Datatype of maxFileSize should be Long instead of Integer > > > Key: ATLAS-2453 > URL: https://issues.apache.org/jira/browse/ATLAS-2453 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Reporter: Sharmadha Sainath >Priority: Major > Attachments: ATLAS-2453.patch > > > maxFileSize attribute of hbase_table should be of type long. > Currently it is an Integer , hence , when creating/updating hbase_table with > maxFileSize value more than integer's range , data between HBase and Atlas is > inconsistent. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2453) Atlas HBase Hook : Datatype of maxFileSize should be Long instead of Integer
Sharmadha Sainath created ATLAS-2453: Summary: Atlas HBase Hook : Datatype of maxFileSize should be Long instead of Integer Key: ATLAS-2453 URL: https://issues.apache.org/jira/browse/ATLAS-2453 Project: Atlas Issue Type: Bug Components: atlas-intg Reporter: Sharmadha Sainath maxFileSize attribute of hbase_table should be of type long. Currently it is an Integer , hence , when creating/updating hbase_table with maxFileSize value more than integer's range , data between HBase and Atlas is inconsistent. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2452) HBase Atlas Hook : isReadOnly hbase_table parameter is always false
[ https://issues.apache.org/jira/browse/ATLAS-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16367305#comment-16367305 ] Sharmadha Sainath commented on ATLAS-2452: -- Review request : https://reviews.apache.org/r/65684/ > HBase Atlas Hook : isReadOnly hbase_table parameter is always false > --- > > Key: ATLAS-2452 > URL: https://issues.apache.org/jira/browse/ATLAS-2452 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Reporter: Sharmadha Sainath >Priority: Major > Attachments: ATLAS-2452.patch > > > isReadOnly hbase_table attribute is always set as -1 because of : > table.setAttribute(ATTR_TABLE_ISREADONLY, htableDescriptor.getMaxFileSize()); > (https://github.com/apache/atlas/blob/master/addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/bridge/HBaseAtlasHook.java#L453) > Change needed to use htableDescriptor.isReadOnly() instead of > htableDescriptor.getMaxFileSize(). > CC : [~rmani] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2452) HBase Atlas Hook : isReadOnly hbase_table parameter is always false
[ https://issues.apache.org/jira/browse/ATLAS-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharmadha Sainath updated ATLAS-2452: - Attachment: ATLAS-2452.patch > HBase Atlas Hook : isReadOnly hbase_table parameter is always false > --- > > Key: ATLAS-2452 > URL: https://issues.apache.org/jira/browse/ATLAS-2452 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Reporter: Sharmadha Sainath >Priority: Major > Attachments: ATLAS-2452.patch > > > isReadOnly hbase_table attribute is always set as -1 because of : > table.setAttribute(ATTR_TABLE_ISREADONLY, htableDescriptor.getMaxFileSize()); > (https://github.com/apache/atlas/blob/master/addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/bridge/HBaseAtlasHook.java#L453) > Change needed to use htableDescriptor.isReadOnly() instead of > htableDescriptor.getMaxFileSize(). > CC : [~rmani] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2452) HBase Atlas Hook : isReadOnly hbase_table parameter is always false
Sharmadha Sainath created ATLAS-2452: Summary: HBase Atlas Hook : isReadOnly hbase_table parameter is always false Key: ATLAS-2452 URL: https://issues.apache.org/jira/browse/ATLAS-2452 Project: Atlas Issue Type: Bug Components: atlas-intg Reporter: Sharmadha Sainath isReadOnly hbase_table attribute is always set as -1 because of : table.setAttribute(ATTR_TABLE_ISREADONLY, htableDescriptor.getMaxFileSize()); (https://github.com/apache/atlas/blob/master/addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/bridge/HBaseAtlasHook.java#L453) Change needed to use htableDescriptor.isReadOnly() instead of htableDescriptor.getMaxFileSize(). CC : [~rmani] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2423) UI : Min values for Double and Float require modification
[
https://issues.apache.org/jira/browse/ATLAS-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16344503#comment-16344503
]
Sharmadha Sainath commented on ATLAS-2423:
--
Review request : https://reviews.apache.org/r/65417/
> UI : Min values for Double and Float require modification
> -
>
> Key: ATLAS-2423
> URL: https://issues.apache.org/jira/browse/ATLAS-2423
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Sharmadha Sainath
>Priority: Major
> Attachments: ATLAS-2423.patch
>
>
> https://github.com/apache/atlas/blob/master/dashboardv2/public/js/utils/Enums.js
> has hard coded values for min and max values for double and float :
> {code}
> "float": {
> min: 1.4E-45,
> max: 3.4028235E38
> },
> "double": {
> min: 4.9E-324,
> max: 1.7976931348623157E308
> }
> {code}
> Hence UI doesn't allow negative values at all in faceted search.
> Values should be -3.4028235E38 and -1.7976931348623157E308 for min value of
> float and double respectively.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2423) UI : Min values for Double and Float require modification
[
https://issues.apache.org/jira/browse/ATLAS-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharmadha Sainath updated ATLAS-2423:
-
Attachment: ATLAS-2423.patch
> UI : Min values for Double and Float require modification
> -
>
> Key: ATLAS-2423
> URL: https://issues.apache.org/jira/browse/ATLAS-2423
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Sharmadha Sainath
>Priority: Major
> Attachments: ATLAS-2423.patch
>
>
> https://github.com/apache/atlas/blob/master/dashboardv2/public/js/utils/Enums.js
> has hard coded values for min and max values for double and float :
> {code}
> "float": {
> min: 1.4E-45,
> max: 3.4028235E38
> },
> "double": {
> min: 4.9E-324,
> max: 1.7976931348623157E308
> }
> {code}
> Hence UI doesn't allow negative values at all in faceted search.
> Values should be -3.4028235E38 and -1.7976931348623157E308 for min value of
> float and double respectively.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ATLAS-2423) UI : Min values for Double and Float require modification
Sharmadha Sainath created ATLAS-2423:
Summary: UI : Min values for Double and Float require modification
Key: ATLAS-2423
URL: https://issues.apache.org/jira/browse/ATLAS-2423
Project: Atlas
Issue Type: Bug
Components: atlas-webui
Reporter: Sharmadha Sainath
https://github.com/apache/atlas/blob/master/dashboardv2/public/js/utils/Enums.js
has hard coded values for min and max values for double and float :
{code}
"float": {
min: 1.4E-45,
max: 3.4028235E38
},
"double": {
min: 4.9E-324,
max: 1.7976931348623157E308
}
{code}
Hence UI doesn't allow negative values at all in faceted search.
Values should be -3.4028235E38 and -1.7976931348623157E308 for min value of
float and double respectively.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ATLAS-2328) Regression : Request body with invalid JSON gets accepted by Atlas
Sharmadha Sainath created ATLAS-2328:
Summary: Regression : Request body with invalid JSON gets accepted
by Atlas
Key: ATLAS-2328
URL: https://issues.apache.org/jira/browse/ATLAS-2328
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Sharmadha Sainath
Priority: Minor
{code}
{
"tagFilters": null,
"classification": "*",
"entityFilters": null,
"excludeDeletedEntities": true,
"typeName": "hdfs_path",
"limit": 100,
"offset": 0,
"includeClassificationAttributes": false,
"attributes": []
}}
{code}
s a wrong JSON with extra braces at the end.
Atlas accepts such JSONs and returns 20X code.
Options
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (ATLAS-2327) Regression : Creating entity using V1 APIs with invalid values for attribute types succeeds
Sharmadha Sainath created ATLAS-2327: Summary: Regression : Creating entity using V1 APIs with invalid values for attribute types succeeds Key: ATLAS-2327 URL: https://issues.apache.org/jira/browse/ATLAS-2327 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Sharmadha Sainath Creating an entity with invalid values using V1 APIs succeeds with 201. Expected is 400 Bad Request. This doesn't happen with V2 APIs. Example : 1.Create type by posting JSON to /api/atlas/types 2.Create entity with random string value for float attribute by posting JSON to /api/atlas/entities 3. Request succeeds with 201. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2326) V1 API /api/atlas/entities/ throws 500 Internal exception
Sharmadha Sainath created ATLAS-2326:
Summary: V1 API /api/atlas/entities/ throws 500
Internal exception
Key: ATLAS-2326
URL: https://issues.apache.org/jira/browse/ATLAS-2326
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Sharmadha Sainath
Attachments: invalid_guid_exception.txt
V1 API /api/atlas/entities/ throws 500 Internal server exception
but with expected error message :
{code}
{
error: "Given instance guid invalidGUIDkqDFDFNyb2zs5 is invalid\/not found"
}
{code}
>From application logs, we could see that it throws the Atlas Base Exception
>first , but later WebApplicationException is thrown.
V2 API /api/atlas/v2/entity/ throws 404.
Attached the complete stack trace.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (ATLAS-2325) Creating entity containing attribute of type set with duplicate values
Sharmadha Sainath created ATLAS-2325:
Summary: Creating entity containing attribute of type set with
duplicate values
Key: ATLAS-2325
URL: https://issues.apache.org/jira/browse/ATLAS-2325
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Sharmadha Sainath
Creating an entity having an attribute of type set with duplicate values is
expected to have only unique values. But duplicate values are retained.
Example : POSTing [1,2,3,1] stored as [1,2,3,1]. Expected is [1,2,3]
Repro :
1. POST the following JSON to /api/atlas/v2/types/typedefs
{code}
{
"enumDefs":[
],
"structDefs":[
],
"classificationDefs":[
],
"entityDefs":[
{
"superTypes":[
],
"attributeDefs":[
{
"name":"type_set",
"typeName":"array",
"isOptional":true,
"cardinality":"SET",
"valuesMinCount":-1,
"valuesMaxCount":-1,
"isUnique":false,
"isIndexable":false
}
],
"category":"ENTITY",
"guid":"kcdnvdsvsdvidnvidsonvosid",
"createdBy":"USER",
"updatedBy":"USER",
"createTime":12345,
"updateTime":12345,
"version":12345,
"name":"simple_entity_type_set",
"description":"simple_entity_type_set",
"typeVersion":"0.1"
}
]
}
{code}
2. Create entity of the type
{code}
"referredEntities":{},
"entity":{
"typeName":"simple_entity_type_set",
"attributes":{
"type_set":["a","a","b"]
},
"guid":"-1",
"status":"ACTIVE",
"createdBy":"admin",
"updatedBy":"admin",
"createTime":1489585008165,
"updateTime":1489585008801,
"version":0,
"classifications":[],
"superTypes":[]
}
}
{code}
3. entity is created with value for type_set as [a,a,b] instead of [a,b]
This is a regression in V1 APIs and seen in V2 APIs too.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (ATLAS-2324) Regression : Entity update by PUT using V1 APIs throws 500 Internal server exception
Sharmadha Sainath created ATLAS-2324: Summary: Regression : Entity update by PUT using V1 APIs throws 500 Internal server exception Key: ATLAS-2324 URL: https://issues.apache.org/jira/browse/ATLAS-2324 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Sharmadha Sainath Attachments: NPE_during_PUT_update.txt, ent_v1, put_v1, type_v1 Steps to repro : 1. Create type using JSON type_v1 by POSTing to /api/atlas/types 2. Create entity for the type using JSON ent_v1 by POSTing to /api/atlas/entities 3. Update the entity using JSON put_v1 (guid to be changed in the JSON) by PUTting to /api/atlas/entities. Update using PUT using V1 APIs throws NPE. Attached the complete exception stack trace . in V2 APIs , full entity update is done using POST and not PUT. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2320) classification "*" with query throws 500 Internal server exception.
Sharmadha Sainath created ATLAS-2320:
Summary: classification "*" with query throws 500 Internal server
exception.
Key: ATLAS-2320
URL: https://issues.apache.org/jira/browse/ATLAS-2320
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Sharmadha Sainath
Attachments: query_and_classification_asterisk.txt
Following basic post query throws 500 internal server exception :
{code}
{
"query":"hive_table",
"classification":"*"
}
{code}
Exception:
{code}
Request to collection fulltext_index failed due to (400)
org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error
from server at http://172.27.58.128:8886/solr/fulltext_index:
org.apache.solr.search.SyntaxError: Cannot parse 'sg5_t:(hive_table AND ())':
Encountered " ")" ") "" at line 1, column 16.
Was expecting one of:
...
"+" ...
"-" ...
...
"(" ...
"*" ...
...
...
...
...
...
"[" ...
"{" ...
...
"filter(" ...
...
...
"*" ...
, retry? 0 (CloudSolrClient:903)
{code}
Attached the complete exception stack trace.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (ATLAS-2319) UI : Deleting a tag which at 25+ position in the tag list in both Flat and Tree structure needs a refresh to remove the tag from the list.
Sharmadha Sainath created ATLAS-2319: Summary: UI : Deleting a tag which at 25+ position in the tag list in both Flat and Tree structure needs a refresh to remove the tag from the list. Key: ATLAS-2319 URL: https://issues.apache.org/jira/browse/ATLAS-2319 Project: Atlas Issue Type: Bug Components: atlas-webui Reporter: Sharmadha Sainath Created a tag tag26 which is the 26th tag in the list. On deleting tag26 from UI , tag26 is successfully deleted , but the entry is still present in the list in both Flat and Tree list structure. After clicking refresh button for tags , tag26 is removed. This doesn't happen with tags which are at position 25 or less. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2318) UI : Clicking on child tag twice , parent tag is selected
Sharmadha Sainath created ATLAS-2318: Summary: UI : Clicking on child tag twice , parent tag is selected Key: ATLAS-2318 URL: https://issues.apache.org/jira/browse/ATLAS-2318 Project: Atlas Issue Type: Bug Components: atlas-webui Reporter: Sharmadha Sainath 1.Created tags super_tag and child_tag with supertag as super_tag. 2.Navigated to child_tag in Tree structure. 3.Clicked on child_tag. The child_tag was selected. 4.Clicked on child_tag again. Now its parent tag (super_tag) was selected. 5.Now any operation performed on super_tag is applied to child_tag (like deleting tag) which is confusing. 6. But if super_tag is selected , operations are applied to super_tag only. CC : [~kevalbhatt] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2301) Concurrent modification exception when saving the search
Sharmadha Sainath created ATLAS-2301:
Summary: Concurrent modification exception when saving the search
Key: ATLAS-2301
URL: https://issues.apache.org/jira/browse/ATLAS-2301
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Sharmadha Sainath
Priority: Critical
Attachments: ConModExceptionSaveSearch.txt
The Atlas instance has 626 types , 332 saved searches. (Search queries are
large).
Post 332 saved searches ,when trying to save a query , ConcurrentModification
exception is thrown with
{code}
audit record too long: entityType=__AtlasUserProfile,
guid=8b9f8e79-30e5-4bfe-afca-cc3adc2a97c6, size=1048743; maxSize=1048576.
entity attribute values not stored in audit (EntityAuditListener:156)
{code}
Attached the complete exception stack trace.
Other functionalities like creating tag , entity ,hive hook functionalities ,
tag association , tag deletion , basic search , faceted basic search works well.
On other instance of Atlas , less types are created and 350+ saved searches are
created (The save search attributes content differ in first instance and second
instance. Former has more filters).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (ATLAS-2294) Extra parameter "description" added when creating a type
Sharmadha Sainath created ATLAS-2294: Summary: Extra parameter "description" added when creating a type Key: ATLAS-2294 URL: https://issues.apache.org/jira/browse/ATLAS-2294 Project: Atlas Issue Type: Bug Components: atlas-core Affects Versions: 1.0.0 Reporter: Sharmadha Sainath When creating a type , there is inconsistency with "description" parameter of the attributes in the type definition. For example : 1.Adding no description parameter in the POST adds “description” :”” in the created type. 2.Adding “description” : “null" in the POST , no description parameter is found in the created type. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2285) UI : Renamed saved search with date attribute.
Sharmadha Sainath created ATLAS-2285: Summary: UI : Renamed saved search with date attribute. Key: ATLAS-2285 URL: https://issues.apache.org/jira/browse/ATLAS-2285 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 1.0.0 Reporter: Sharmadha Sainath Priority: Critical Attachments: saved_search_with_date_renamed.mov 1. Fired basic search typename = hive_table , filter CreateTime = 08/02/2017 9:10 PM and saved search as date_search 2. Clicked on the saved search "date_search" and verified the filters. filter CreateTime = 08/02/2017 9:10 PM is rightly set. 3. Clicked on the "date_search" and renamed it to "date_search_renamed" without modifying the filters . 4.PUT REST call to update the search had the correct filter value. 5. Refreshed the page and clicked on the "date_search_renamed". Now , the date filter was modified to CreateTime = 01/01/1970 5:30 AM . 6. /api/atlas/v2/search/saved GET response had 08/02/2017 9:10 PM filter value for "date_search_renamed" but UI shows 01/01/1970 5:30 AM. Attached the video recording. CC : [~kevalbhatt] [~praik24mac] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2284) Import hive fails with "java.lang.NoClassDefFoundError: com/sun/jersey/multipart/BodyPart"
Sharmadha Sainath created ATLAS-2284:
Summary: Import hive fails with "java.lang.NoClassDefFoundError:
com/sun/jersey/multipart/BodyPart"
Key: ATLAS-2284
URL: https://issues.apache.org/jira/browse/ATLAS-2284
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 1.0.0
Reporter: Sharmadha Sainath
Priority: Blocker
Import hive fails with following error :
{code}
java.io.FileNotFoundException:
/usr/hdp/current/atlas-server/logs/import-hive.log (No such file or directory)
at java.io.FileOutputStream.open0(Native Method)
at java.io.FileOutputStream.open(FileOutputStream.java:270)
at java.io.FileOutputStream.(FileOutputStream.java:213)
at java.io.FileOutputStream.(FileOutputStream.java:133)
at org.apache.log4j.FileAppender.setFile(FileAppender.java:294)
at
org.apache.log4j.RollingFileAppender.setFile(RollingFileAppender.java:207)
at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165)
at
org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307)
at
org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:295)
at
org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:176)
at
org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:191)
at
org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:523)
at
org.apache.log4j.xml.DOMConfigurator.parseCategory(DOMConfigurator.java:436)
at org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:1004)
at
org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:872)
at
org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:778)
at
org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:483)
at org.apache.log4j.LogManager.(LogManager.java:127)
at
org.slf4j.impl.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:64)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:281)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:301)
at
org.apache.atlas.hive.bridge.HiveMetaStoreBridge.(HiveMetaStoreBridge.java:97)
Exception in thread "main" java.lang.NoClassDefFoundError:
com/sun/jersey/multipart/BodyPart
at
org.apache.atlas.hive.bridge.HiveMetaStoreBridge.main(HiveMetaStoreBridge.java:634)
Caused by: java.lang.ClassNotFoundException: com.sun.jersey.multipart.BodyPart
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)
... 1 more
Failed to import Hive Data Model!!
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (ATLAS-2282) Saved favorite search appears only on refresh after creation when there are many favorite search .
Sharmadha Sainath created ATLAS-2282: Summary: Saved favorite search appears only on refresh after creation when there are many favorite search . Key: ATLAS-2282 URL: https://issues.apache.org/jira/browse/ATLAS-2282 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 1.0.0 Reporter: Sharmadha Sainath 1. Created 24 basic favorite search . 2. Created 25th basic favorite search. Popup notification displayed that the search is successfully created.Without any refresh , 25th favorite search appeared in the favorite search list. 3. Created 26th basic favorite search. Popup notification displayed that the search is successfully created. 4.But the favorite search list didn't display the 26th basic favorite search but only the ld 25 searches, 5.On page refresh , the 26th favorite search was displayed. Thus , when more than 25 Basic/Advanced favorite searches (Basic and Advanced separately 25) are created , the newly created favorite search is displayed only on page refresh. CC : [~kevalbhatt] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2282) Saved favorite search appears only on refresh after creation when there are 25+ favorite searches .
[ https://issues.apache.org/jira/browse/ATLAS-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharmadha Sainath updated ATLAS-2282: - Summary: Saved favorite search appears only on refresh after creation when there are 25+ favorite searches . (was: Saved favorite search appears only on refresh after creation when there are many favorite search .) > Saved favorite search appears only on refresh after creation when there are > 25+ favorite searches . > --- > > Key: ATLAS-2282 > URL: https://issues.apache.org/jira/browse/ATLAS-2282 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 1.0.0 >Reporter: Sharmadha Sainath > > 1. Created 24 basic favorite search . > 2. Created 25th basic favorite search. Popup notification displayed that the > search is successfully created.Without any refresh , 25th favorite search > appeared in the favorite search list. > 3. Created 26th basic favorite search. Popup notification displayed that the > search is successfully created. > 4.But the favorite search list didn't display the 26th basic favorite search > but only the ld 25 searches, > 5.On page refresh , the 26th favorite search was displayed. > Thus , when more than 25 Basic/Advanced favorite searches (Basic and Advanced > separately 25) are created , the newly created favorite search is displayed > only on page refresh. > CC : [~kevalbhatt] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2281) Saving Tag/Type attribute filter queries with null/not null filters.
Sharmadha Sainath created ATLAS-2281: Summary: Saving Tag/Type attribute filter queries with null/not null filters. Key: ATLAS-2281 URL: https://issues.apache.org/jira/browse/ATLAS-2281 Project: Atlas Issue Type: Bug Components: atlas-webui Reporter: Sharmadha Sainath Priority: Critical 1. Fired Basic Search typename = hive_table , filter : "Name" condition : "is not null". 2. Saved the query. 3. Executed the saved query which fetched all the correct tables. 4. Now to modify the search , clicked on the saved search and clicked on the type filter. 5. The Attribute filter window didn't load. " Error: Undefined operator "notNull" " was thrown in browser's console logs. Same happens when clicking the saved search containing "is null" filter. "Error: Undefined operator "isNull" " is thrown in console.log. But the saved search can be executed without any issues. Also seen in tag attributes filters. This is not seen with other filters for all data types. CC : [~kevalbhatt] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2277) Search using entity and trait attributes - excludeDeletedEntities parameter doesn't take effect when classification is "*"
Sharmadha Sainath created ATLAS-2277:
Summary: Search using entity and trait attributes -
excludeDeletedEntities parameter doesn't take effect when classification is "*"
Key: ATLAS-2277
URL: https://issues.apache.org/jira/browse/ATLAS-2277
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 1.0.0
Reporter: Sharmadha Sainath
POST request body to /api/atlas/v2/search/basic :
{code}
{
"excludeDeletedEntities":true,
"includeClassificationAttributes": true,
"entityFilters":null,
"tagFilters":null,
"attributes":[],
"limit":100,
"offset":0,
"classification":"*"
}
{code}
though excludeDeletedEntities is True , when classification is "*" , the result
has the DELETED entities too.
When any tag name is provided and excludeDeletedEntities when set to True ,
response doesn't have DELETED entities.
Hence incorrect results only when classification is "*".
CC : [~sarath.ku...@gmail.com] [~nixonrodrigues]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ATLAS-2274) Search using entity and trait attributes - typename and "*" in classificationName throws Invalid condition exception
[
https://issues.apache.org/jira/browse/ATLAS-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharmadha Sainath updated ATLAS-2274:
-
Attachment: Atlas_asterisk_in_classification_and type_name_exception.txt
> Search using entity and trait attributes - typename and "*" in
> classificationName throws Invalid condition exception
>
>
> Key: ATLAS-2274
> URL: https://issues.apache.org/jira/browse/ATLAS-2274
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
> Attachments: Atlas_asterisk_in_classification_and
> type_name_exception.txt
>
>
> Following is the POST request body to /api/atlas/v2/search/basic
> {code}
> {
> "excludeDeletedEntities":true,
> "entityFilters":null,
> "tagFilters":null,
> "attributes":[],
> "limit":25,
> "offset":0,
> "typeName":"hive_table",
> "classification":"*"
> }
> {code}
> When any typeName is provided , Atlas throws 500 Internal server
> exception.Attached the exception stack trace.
> When typeName parameter is removed ,or is given "null" value , response is
> 200 OK.
> When a tag name is provided instead of "*" , and typeName is given ,no issues
> are seen.
> Hence , issue with * in classificationName and typeName provided together.
> CC : [~sarath.ku...@gmail.com]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ATLAS-1116) Performance monitoring of backend methods in API requests
[ https://issues.apache.org/jira/browse/ATLAS-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharmadha Sainath updated ATLAS-1116: - Attachment: (was: Atlas_asterisk_in_classification_and type_name_exception.txt) > Performance monitoring of backend methods in API requests > - > > Key: ATLAS-1116 > URL: https://issues.apache.org/jira/browse/ATLAS-1116 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma >Assignee: Shwetha G S > Fix For: 0.8-incubating > > Attachments: ATLAS-1116-v2.patch, ATLAS-1116-v3.patch, > ATLAS-1116.patch > > > Time taken by methods used in API calls for add/update/delete entities and > traits need to be monitored for performance -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2274) Search using entity and trait attributes - typename and "*" in classificationName throws Invalid condition exception
Sharmadha Sainath created ATLAS-2274:
Summary: Search using entity and trait attributes - typename and
"*" in classificationName throws Invalid condition exception
Key: ATLAS-2274
URL: https://issues.apache.org/jira/browse/ATLAS-2274
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 1.0.0
Reporter: Sharmadha Sainath
Following is the POST request body to /api/atlas/v2/search/basic
{code}
{
"excludeDeletedEntities":true,
"entityFilters":null,
"tagFilters":null,
"attributes":[],
"limit":25,
"offset":0,
"typeName":"hive_table",
"classification":"*"
}
{code}
When any typeName is provided , Atlas throws 500 Internal server
exception.Attached the exception stack trace.
When typeName parameter is removed ,or is given "null" value , response is 200
OK.
When a tag name is provided instead of "*" , and typeName is given ,no issues
are seen.
Hence , issue with * in classificationName and typeName provided together.
CC : [~sarath.ku...@gmail.com]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ATLAS-1116) Performance monitoring of backend methods in API requests
[ https://issues.apache.org/jira/browse/ATLAS-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharmadha Sainath updated ATLAS-1116: - Attachment: Atlas_asterisk_in_classification_and type_name_exception.txt > Performance monitoring of backend methods in API requests > - > > Key: ATLAS-1116 > URL: https://issues.apache.org/jira/browse/ATLAS-1116 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma >Assignee: Shwetha G S > Fix For: 0.8-incubating > > Attachments: ATLAS-1116-v2.patch, ATLAS-1116-v3.patch, > ATLAS-1116.patch, Atlas_asterisk_in_classification_and type_name_exception.txt > > > Time taken by methods used in API calls for add/update/delete entities and > traits need to be monitored for performance -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2268) UI : Faceted Search : Filters are not removed when not cleared between searches.
Sharmadha Sainath created ATLAS-2268: Summary: UI : Faceted Search : Filters are not removed when not cleared between searches. Key: ATLAS-2268 URL: https://issues.apache.org/jira/browse/ATLAS-2268 Project: Atlas Issue Type: Bug Components: atlas-webui Reporter: Sharmadha Sainath 1. In Basic search , fire search type = hive_table , filter = name contains hive. Apply Search 2.Fire another search ,type = kafka_topic (without clicking clear button). 3.Now fire search again : type = hive_table without any filters (without clicking clear button). Though only type name is searched , last filter "name contains hive" is applied still. Expected that the type search would be cleared completely when other type search is made. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2257) hive_column type definition changes for position and table attributes when updated
Sharmadha Sainath created ATLAS-2257:
Summary: hive_column type definition changes for position and
table attributes when updated
Key: ATLAS-2257
URL: https://issues.apache.org/jira/browse/ATLAS-2257
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Sharmadha Sainath
On a fresh instance of Atlas , following is the type definition of hive_column :
{code}
{
category:"ENTITY",
guid:"076ceac2-5c0d-400f-8f89-ab455125191d",
createdBy:"atlas",
updatedBy:"atlas",
createTime:1510294855527,
updateTime:1510294855527,
version:1,
name:"hive_column",
description:"hive_column",
typeVersion:"1.3",
options:{
schemaAttributes:"[" name",
"description",
"owner",
"type",
"comment",
"position"
] "
},
attributeDefs: [
{
name: " type",
typeName:"string",
isOptional:false,
cardinality:"SINGLE",
valuesMinCount:1,
valuesMaxCount:1,
isUnique:false,
isIndexable:true
},
{
name:"comment",
typeName:"string",
isOptional:true,
cardinality:"SINGLE",
valuesMinCount:0,
valuesMaxCount:1,
isUnique:false,
isIndexable:false
},
{
name:"position",
typeName:"int",
isOptional:true,
cardinality:"SINGLE",
valuesMinCount:-1,
valuesMaxCount:-1,
isUnique:false,
isIndexable:false
},
{
name:"table",
typeName:"hive_table",
isOptional:true,
cardinality:"SINGLE",
valuesMinCount:-1,
valuesMaxCount:-1,
isUnique:false,
isIndexable:false
}
],
superTypes:[
"DataSet"
]
}
{code}
fired an update PUT request to update the hive_column type definition without
changing the definition . Update is successful. After update , following is the
type definition of hive_column :
{code}
{
category:"ENTITY",
guid:"076ceac2-5c0d-400f-8f89-ab455125191d",
createdBy:"atlas",
updatedBy:"admin",
createTime:1510294855527,
updateTime:1510294918066,
version:5,
name:"hive_column",
description:"hive_column",
typeVersion:"1.3",
options:{
schemaAttributes:"[" name",
"description",
"owner",
"type",
"comment",
"position"
] "
},
attributeDefs: [
{
name: " type",
typeName:"string",
isOptional:false,
cardinality:"SINGLE",
valuesMinCount:1,
valuesMaxCount:1,
isUnique:false,
isIndexable:true
},
{
name:"comment",
typeName:"string",
isOptional:true,
cardinality:"SINGLE",
valuesMinCount:0,
valuesMaxCount:1,
isUnique:false,
isIndexable:false
},
{
name:"position",
typeName:"int",
isOptional:true,
cardinality:"SINGLE",
valuesMinCount:0,
valuesMaxCount:1,
isUnique:false,
isIndexable:false
},
{
name:"table",
typeName:"hive_table",
isOptional:true,
cardinality:"SINGLE",
valuesMinCount:0,
valuesMaxCount:1,
isUnique:false,
isIndexable:false
}
],
superTypes:[
"DataSet"
]
}
{code}
valuesMinCount and valuesMaxCount values differ for "position" and "table"
attributes post update.
Thanks [~ayubkhan] for helping to reproduce the issue .
This issue is not seen in other data types in hive model.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ATLAS-2237) Exponential values for tag attribute values for float, double are stored differently.
[ https://issues.apache.org/jira/browse/ATLAS-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharmadha Sainath updated ATLAS-2237: - Description: On providing 1. 3.4e+10 to a float tag attribute value , it is stored as 3399000 . 2. 34e+10 to a float tag attribute value , it is stored as 34014000. But 3.4e+9 for a float attribute is stored as 34 correctly. The POST body is sent with the exponential values but stored differently. was: On providing 1. 3.4e+10 to a float tag attribute value , it is stored as 3399000 . 2. 34e+10 to a float tag attribute value , it is stored as 34014000. The POST body is sent with the exponential values but stored differently. > Exponential values for tag attribute values for float, double are stored > differently. > - > > Key: ATLAS-2237 > URL: https://issues.apache.org/jira/browse/ATLAS-2237 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Sharmadha Sainath > > On providing > 1. 3.4e+10 to a float tag attribute value , it is stored as 3399000 . > 2. 34e+10 to a float tag attribute value , it is stored as 34014000. > But 3.4e+9 for a float attribute is stored as 34 correctly. > The POST body is sent with the exponential values but stored differently. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2237) Exponential values for tag attribute values for float, double are stored differently.
Sharmadha Sainath created ATLAS-2237: Summary: Exponential values for tag attribute values for float, double are stored differently. Key: ATLAS-2237 URL: https://issues.apache.org/jira/browse/ATLAS-2237 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Sharmadha Sainath On providing 1. 3.4e+10 to a float tag attribute value , it is stored as 3399000 . 2. 34e+10 to a float tag attribute value , it is stored as 34014000. The POST body is sent with the exponential values but stored differently. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2231) UI: Unable to provide f,d notation for float and double tag attribute values respectively.
Sharmadha Sainath created ATLAS-2231: Summary: UI: Unable to provide f,d notation for float and double tag attribute values respectively. Key: ATLAS-2231 URL: https://issues.apache.org/jira/browse/ATLAS-2231 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 1.0.0 Reporter: Sharmadha Sainath Input box for float and double doesn't accept f and d notations respectively . -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2222) UI: Search using entity and trait attributes - "," in string attribute filter throws 400 Bad request
Sharmadha Sainath created ATLAS-:
Summary: UI: Search using entity and trait attributes - "," in
string attribute filter throws 400 Bad request
Key: ATLAS-
URL: https://issues.apache.org/jira/browse/ATLAS-
Project: Atlas
Issue Type: Bug
Components: atlas-webui
Reporter: Sharmadha Sainath
Priority: Critical
In UI , When string attribute filter contains comma , it is taken as separate
attribute filter.
For example basic search : hive_table , filter : description = a , b
POST request body :
{code}
{
"excludeDeletedEntities":true,
"entityFilters":{
"condition":"AND",
"criterion":[
{
"attributeName":"description",
"operator":"eq",
"attributeValue":"a"
},
{
"attributeName":"b",
"operator":"string"
}
]
},
"tagFilters":null,
"attributes":[
],
"limit":25,
"offset":0,
"typeName":"hive_table",
"classification":null
}
{code}
The search throws 400 Bad request with error notification "Attribute b not
found for type hive_table".
This is seen only in UI ,as when search is fired with attributeValue given as
"a,b" using REST API , fetches correct results.
{code}
{
"excludeDeletedEntities":true,
"entityFilters":{
"condition":"AND",
"criterion":[
{
"attributeName":"description",
"operator":"eq",
"attributeValue":"a,b"
}
]
},
"tagFilters":null,
"attributes":[
],
"limit":25,
"offset":0,
"typeName":"hdfs_path",
"classification":null
}
{code}
CC : [~kevalbhatt] [~madhan.neethiraj] [~apoorvnaik]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (ATLAS-2219) UI Regression : Unable to provide exponential values for tag attribute values in UI.
Sharmadha Sainath created ATLAS-2219: Summary: UI Regression : Unable to provide exponential values for tag attribute values in UI. Key: ATLAS-2219 URL: https://issues.apache.org/jira/browse/ATLAS-2219 Project: Atlas Issue Type: Bug Components: atlas-webui Reporter: Sharmadha Sainath Assignee: Keval Bhatt Priority: Critical For tag attributes of data type double , float etc, the corresponding text box is not accepting 'E' character for providing exponential values. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2214) Search using trait attributes "!=" and "is not null" together and in order in string,boolean tag attribute filter comparison
[
https://issues.apache.org/jira/browse/ATLAS-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharmadha Sainath updated ATLAS-2214:
-
Summary: Search using trait attributes "!=" and "is not null" together
and in order in string,boolean tag attribute filter comparison (was: Search
using entity and trait attributes "!=" and "is not null" together and in
order in string,boolean tag filter attribute comparison)
> Search using trait attributes "!=" and "is not null" together and in order
> in string,boolean tag attribute filter comparison
> --
>
> Key: ATLAS-2214
> URL: https://issues.apache.org/jira/browse/ATLAS-2214
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Sharmadha Sainath
>Priority: Critical
> Attachments: not_equals_and_not_null_tag_filter_exception.txt
>
>
> 1. Created a tag tag1 with attributes of all data types.
> 2. Fired a basic search with tag1 and following tag filters of type string:
> a)string != rand
> b)string is not null
> POST body
> {code}
> {
>"excludeDeletedEntities":true,
>"entityFilters":null,
>"tagFilters":{
> "condition":"AND",
> "criterion":[
> {
> "attributeName":"string",
> "operator":"neq",
> "attributeValue":"rand"
> },
> {
> "attributeName":"string",
> "operator":"not_null",
> "attributeValue":""
> }
> ]
>},
>"attributes":null,
>"limit":25,
>"offset":0,
>"typeName":null,
>"classification":"tag1"
> }
> {code}
> The search threw 500 Internal server exception. Attached the stack trace .
> Note :
> 1)This exception is not seen if order is reversed (i.e) , in the order
>a)string is not null
>b)string != rand
> In this order , correct results are fetched.
> 2)For string and boolean data types , this exception is seen. This was not
> seen with int , float, short , double , date , enum .
>
> 3)Also , this issue is seen only in tag attribute filters and not in type
> attribute filters.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (ATLAS-2214) Search using entity and trait attributes "!=" and "is not null" together and in order in string,boolean tag filter attribute comparison
Sharmadha Sainath created ATLAS-2214:
Summary: Search using entity and trait attributes "!=" and "is
not null" together and in order in string,boolean tag filter attribute
comparison
Key: ATLAS-2214
URL: https://issues.apache.org/jira/browse/ATLAS-2214
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Sharmadha Sainath
Priority: Critical
Attachments: not_equals_and_not_null_tag_filter_exception.txt
1. Created a tag tag1 with attributes of all data types.
2. Fired a basic search with tag1 and following tag filters of type string:
a)string != rand
b)string is not null
POST body
{code}
{
"excludeDeletedEntities":true,
"entityFilters":null,
"tagFilters":{
"condition":"AND",
"criterion":[
{
"attributeName":"string",
"operator":"neq",
"attributeValue":"rand"
},
{
"attributeName":"string",
"operator":"not_null",
"attributeValue":""
}
]
},
"attributes":null,
"limit":25,
"offset":0,
"typeName":null,
"classification":"tag1"
}
{code}
The search threw 500 Internal server exception. Attached the stack trace .
Note :
1)This exception is not seen if order is reversed (i.e) , in the order
a)string is not null
b)string != rand
In this order , correct results are fetched.
2)For string and boolean data types , this exception is seen. This was not seen
with int , float, short , double , date , enum .
3)Also , this issue is seen only in tag attribute filters and not in type
attribute filters.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ATLAS-2212) Regression : Unable to provide negative values directly for tag attributes of data type int.
[ https://issues.apache.org/jira/browse/ATLAS-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharmadha Sainath updated ATLAS-2212: - Summary: Regression : Unable to provide negative values directly for tag attributes of data type int. (was: Unable to provide negative values directly for tag attributes of data type int.) > Regression : Unable to provide negative values directly for tag attributes of > data type int. > > > Key: ATLAS-2212 > URL: https://issues.apache.org/jira/browse/ATLAS-2212 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 1.0.0 >Reporter: Sharmadha Sainath >Assignee: pratik pandey > > 1. Created a tag with int attribute. > 2. Tried to associate the tag to an entity with tag attribute value as -1. > Unable to provide negative value.(i.e) minus sign is not accepted. > 3. Able to set negative value for int if value is changed using Up and Down > Arrow . > 4. This behavior is not observed for short,byte,float,double attribute > values. Able to provide negative value directly for datatypes other than int. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2212) Unable to provide negative values directly for tag attributes of data type int.
Sharmadha Sainath created ATLAS-2212: Summary: Unable to provide negative values directly for tag attributes of data type int. Key: ATLAS-2212 URL: https://issues.apache.org/jira/browse/ATLAS-2212 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 1.0.0 Reporter: Sharmadha Sainath 1. Created a tag with int attribute. 2. Tried to associate the tag to an entity with tag attribute value as -1. Unable to provide negative value.(i.e) minus sign is not accepted. 3. Able to set negative value for int if value is changed using Up and Down Arrow . 4. This behavior is not observed for short,byte,float,double attribute values. Able to provide negative value directly for datatypes other than int. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (ATLAS-2212) Unable to provide negative values directly for tag attributes of data type int.
[ https://issues.apache.org/jira/browse/ATLAS-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharmadha Sainath reassigned ATLAS-2212: Assignee: Keval Bhatt > Unable to provide negative values directly for tag attributes of data type > int. > --- > > Key: ATLAS-2212 > URL: https://issues.apache.org/jira/browse/ATLAS-2212 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 1.0.0 >Reporter: Sharmadha Sainath >Assignee: Keval Bhatt > > 1. Created a tag with int attribute. > 2. Tried to associate the tag to an entity with tag attribute value as -1. > Unable to provide negative value.(i.e) minus sign is not accepted. > 3. Able to set negative value for int if value is changed using Up and Down > Arrow . > 4. This behavior is not observed for short,byte,float,double attribute > values. Able to provide negative value directly for datatypes other than int. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2208) Include historical entities in Schema tab checked by default for DELETED tables
[ https://issues.apache.org/jira/browse/ATLAS-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharmadha Sainath updated ATLAS-2208: - Attachment: SchemaTab of Deleted table.png > Include historical entities in Schema tab checked by default for DELETED > tables > --- > > Key: ATLAS-2208 > URL: https://issues.apache.org/jira/browse/ATLAS-2208 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Sharmadha Sainath > Attachments: SchemaTab of Deleted table.png > > > 1. Created and dropped hive_table table1 with columns col1 , col2 > 2. Fired basic search hive_table and checked "Show historical entities" which > listed the DELETED table. > 3. Clicked on the DELETED table and clicked on the Schema Tab for the table. > 4. Include historical entities was checked by default (I suppose it is > displaying the Show historical entities value checked in the Search page ). > 5. Though it is checked , no columns were listed. > 6. Toggled the value twice. Now Include historical entities is checked again > , and now DELETED columns were listed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2208) Include historical entities in Schema tab checked by default for DELETED tables
Sharmadha Sainath created ATLAS-2208: Summary: Include historical entities in Schema tab checked by default for DELETED tables Key: ATLAS-2208 URL: https://issues.apache.org/jira/browse/ATLAS-2208 Project: Atlas Issue Type: Bug Components: atlas-webui Reporter: Sharmadha Sainath 1. Created and dropped hive_table table1 with columns col1 , col2 2. Fired basic search hive_table and checked "Show historical entities" which listed the DELETED table. 3. Clicked on the DELETED table and clicked on the Schema Tab for the table. 4. Include historical entities was checked by default (I suppose it is displaying the Show historical entities value checked in the Search page ). 5. Though it is checked , no columns were listed. 6. Toggled the value twice. Now Include historical entities is checked again , and now DELETED columns were listed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2203) Regression Atlas Knox Proxy : j_spring_security_check not found during login
Sharmadha Sainath created ATLAS-2203:
Summary: Regression Atlas Knox Proxy : j_spring_security_check
not found during login
Key: ATLAS-2203
URL: https://issues.apache.org/jira/browse/ATLAS-2203
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Sharmadha Sainath
Priority: Blocker
1.Enabled knox proxy for Atlas.
2. On accessing https://knox_gateway:8443/gateway/ui/atlas/login.jsp , 404 is
thrown with the following :
{code}
POST
404 Not Found
https://knox_gateway:8443/gateway/j_spring_security_check
{code}
and
{code}
GET
404 Not Found
https://knox_gateway:8443/favicon.ico
{code}
which should ideally go to
{code}
https://knox_gateway:8443/gateway/ui/atlas/j_spring_security_check
{code}
CC : [~nixonrodrigues]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ATLAS-2171) Error in parsing API when accessing Atlas via knox proxy without "/" at the end
[
https://issues.apache.org/jira/browse/ATLAS-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharmadha Sainath updated ATLAS-2171:
-
Summary: Error in parsing API when accessing Atlas via knox proxy without
"/" at the end (was: Accessing atlas via knox proxy without "/" at the end
logs in as UNKNOWN user)
> Error in parsing API when accessing Atlas via knox proxy without "/" at the
> end
> ---
>
> Key: ATLAS-2171
> URL: https://issues.apache.org/jira/browse/ATLAS-2171
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Critical
> Attachments: ATLAS-2171.patch
>
>
> 1. Enabled knox proxy for atlas.
> 2.Accessed Atlas UI via proxy using https://knox_gateway:8443/gateway/ui/atlas
> 3. Provided admin username and password and logged into Atlas
> 4. Now, opened another tab in browser with URL
> {code}
> https://knox_gateway:8443/gateway/ui/atlas
> {code}
> I was not logged in as admin but as an unknown user.No read/write operations
> were allowed. Found the following application logs :
> {code}
> 2017-09-26 05:39:31,467 ERROR - [pool-2-thread-9:] ~ Unable to find Atlas
> Resource corresponding to :
> Setting UNKNOWN (AtlasAuthorizationUtils:143)
> {code}
> If the URL is accessed with "/" at the end , logs in as admin user and all
> operations work fine.
> Example :
> {code}
> https://knox_gateway:8443/gateway/ui/atlas/
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ATLAS-2182) UI : Web elements are hidden when zoomed in
[ https://issues.apache.org/jira/browse/ATLAS-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharmadha Sainath updated ATLAS-2182: - Description: Opened Atlas UI on Chrome . On zooming at 150% , most of the elements on Search tab are not visible. Attached the screenshot. At 200 % , complete left Search pane is not visible. was: Opened Atlas UI on Chrome . On zooming at 150% , few elements on Search tab are not visible. Attached the screenshot. At 200 % , complete left Search pane is not visible. > UI : Web elements are hidden when zoomed in > > > Key: ATLAS-2182 > URL: https://issues.apache.org/jira/browse/ATLAS-2182 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 1.0.0 >Reporter: Sharmadha Sainath > Attachments: Atlas_UI_zoomed_at_150%.png > > > Opened Atlas UI on Chrome . On zooming at 150% , most of the elements on > Search tab are not visible. > Attached the screenshot. At 200 % , complete left Search pane is not visible. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2182) UI : Web elements are hidden when zoomed in
Sharmadha Sainath created ATLAS-2182: Summary: UI : Web elements are hidden when zoomed in Key: ATLAS-2182 URL: https://issues.apache.org/jira/browse/ATLAS-2182 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 1.0.0 Reporter: Sharmadha Sainath Attachments: Atlas_UI_zoomed_at_150%.png Opened Atlas UI on Chrome . On zooming at 150% , few elements on Search tab are not visible. Attached the screenshot. At 200 % , complete left Search pane is not visible. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (ATLAS-2180) Regression : Hive hook is broken
[
https://issues.apache.org/jira/browse/ATLAS-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16182280#comment-16182280
]
Sharmadha Sainath edited comment on ATLAS-2180 at 9/27/17 9:51 AM:
---
Falcon,Storm hooks are working well. Problem is with hive hook only. (Didn't
test Sqoop hook as there is an already existing issue with Sqoop hive
integration itself)
was (Author: ssainath):
Falcon,Storm hooks are working well. Problem is with hive hook only. (Didn't
test Sqoop hook as there is an already existing issue with Sqoop component
itself)
> Regression : Hive hook is broken
>
>
> Key: ATLAS-2180
> URL: https://issues.apache.org/jira/browse/ATLAS-2180
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Priority: Blocker
>
> Hive table creation succeeded but while invoking Atlas hook , following error
> message seen in hive logs :
> {code}
> 2017-09-27 06:29:26,084 INFO [Atlas Logger 0]: hook.HiveHook
> (HiveHook.java:collect(244)) - Entered Atlas hook for hook type
> POST_EXEC_HOOK, operation CREATETABLE , user null as hive
> 2017-09-27 06:29:26,084 INFO [HiveServer2-Background-Pool: Thread-236]:
> log.PerfLogger (PerfLogger.java:PerfLogBegin(149)) - method=releaseLocks from=org.apache.hadoop.hive.ql.Driver>
> 2017-09-27 06:29:26,084 INFO [HiveServer2-Background-Pool: Thread-236]:
> log.PerfLogger (PerfLogger.java:PerfLogEnd(177)) - method=releaseLocks start=1506493766084 end=1506493766084 duration=0
> from=org.apache.hadoop.hive.ql.Driver>
> 2017-09-27 06:29:26,085 INFO [HiveServer2-Background-Pool: Thread-236]:
> log.PerfLogger (PerfLogger.java:PerfLogEnd(177)) - method=Driver.run start=1506493763780 end=1506493766085 duration=2305
> from=org.apache.hadoop.hive.ql.Driver>
> 2017-09-27 06:29:26,087 ERROR [Atlas Logger 0]: hook.HiveHook
> (HiveHook.java:run(205)) - Atlas hook failed due to error
> java.lang.NoClassDefFoundError: org/apache/atlas/AtlasServiceException
> at org.apache.atlas.hive.hook.HiveHook.collect(HiveHook.java:246)
> at org.apache.atlas.hive.hook.HiveHook.access$200(HiveHook.java:83)
> at org.apache.atlas.hive.hook.HiveHook$2$1.run(HiveHook.java:198)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1866)
> at org.apache.atlas.hive.hook.HiveHook$2.run(HiveHook.java:195)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.atlas.AtlasServiceException
> at java.lang.ClassLoader.findClass(ClassLoader.java:530)
> at
> org.apache.atlas.plugin.classloader.AtlasPluginClassLoader$MyClassLoader.findClass(AtlasPluginClassLoader.java:328)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at
> org.apache.atlas.plugin.classloader.AtlasPluginClassLoader.loadClass(AtlasPluginClassLoader.java:136)
> ... 12 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (ATLAS-2180) Regression : Hive hook is broken
[
https://issues.apache.org/jira/browse/ATLAS-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16182280#comment-16182280
]
Sharmadha Sainath commented on ATLAS-2180:
--
Falcon,Storm hooks are working well. Problem is with hive hook only. (Didn't
test Sqoop hook as there is an already existing issue with Sqoop component
itself)
> Regression : Hive hook is broken
>
>
> Key: ATLAS-2180
> URL: https://issues.apache.org/jira/browse/ATLAS-2180
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Priority: Blocker
>
> Hive table creation succeeded but while invoking Atlas hook , following error
> message seen in hive logs :
> {code}
> 2017-09-27 06:29:26,084 INFO [Atlas Logger 0]: hook.HiveHook
> (HiveHook.java:collect(244)) - Entered Atlas hook for hook type
> POST_EXEC_HOOK, operation CREATETABLE , user null as hive
> 2017-09-27 06:29:26,084 INFO [HiveServer2-Background-Pool: Thread-236]:
> log.PerfLogger (PerfLogger.java:PerfLogBegin(149)) - method=releaseLocks from=org.apache.hadoop.hive.ql.Driver>
> 2017-09-27 06:29:26,084 INFO [HiveServer2-Background-Pool: Thread-236]:
> log.PerfLogger (PerfLogger.java:PerfLogEnd(177)) - method=releaseLocks start=1506493766084 end=1506493766084 duration=0
> from=org.apache.hadoop.hive.ql.Driver>
> 2017-09-27 06:29:26,085 INFO [HiveServer2-Background-Pool: Thread-236]:
> log.PerfLogger (PerfLogger.java:PerfLogEnd(177)) - method=Driver.run start=1506493763780 end=1506493766085 duration=2305
> from=org.apache.hadoop.hive.ql.Driver>
> 2017-09-27 06:29:26,087 ERROR [Atlas Logger 0]: hook.HiveHook
> (HiveHook.java:run(205)) - Atlas hook failed due to error
> java.lang.NoClassDefFoundError: org/apache/atlas/AtlasServiceException
> at org.apache.atlas.hive.hook.HiveHook.collect(HiveHook.java:246)
> at org.apache.atlas.hive.hook.HiveHook.access$200(HiveHook.java:83)
> at org.apache.atlas.hive.hook.HiveHook$2$1.run(HiveHook.java:198)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1866)
> at org.apache.atlas.hive.hook.HiveHook$2.run(HiveHook.java:195)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.atlas.AtlasServiceException
> at java.lang.ClassLoader.findClass(ClassLoader.java:530)
> at
> org.apache.atlas.plugin.classloader.AtlasPluginClassLoader$MyClassLoader.findClass(AtlasPluginClassLoader.java:328)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at
> org.apache.atlas.plugin.classloader.AtlasPluginClassLoader.loadClass(AtlasPluginClassLoader.java:136)
> ... 12 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (ATLAS-2180) Regression : Hive hook is broken
Sharmadha Sainath created ATLAS-2180:
Summary: Regression : Hive hook is broken
Key: ATLAS-2180
URL: https://issues.apache.org/jira/browse/ATLAS-2180
Project: Atlas
Issue Type: Bug
Components: atlas-intg
Affects Versions: 1.0.0
Reporter: Sharmadha Sainath
Priority: Blocker
Hive table creation succeeded but while invoking Atlas hook , following error
message seen in hive logs :
{code}
2017-09-27 06:29:26,084 INFO [Atlas Logger 0]: hook.HiveHook
(HiveHook.java:collect(244)) - Entered Atlas hook for hook type POST_EXEC_HOOK,
operation CREATETABLE , user null as hive
2017-09-27 06:29:26,084 INFO [HiveServer2-Background-Pool: Thread-236]:
log.PerfLogger (PerfLogger.java:PerfLogBegin(149)) -
2017-09-27 06:29:26,084 INFO [HiveServer2-Background-Pool: Thread-236]:
log.PerfLogger (PerfLogger.java:PerfLogEnd(177)) -
2017-09-27 06:29:26,085 INFO [HiveServer2-Background-Pool: Thread-236]:
log.PerfLogger (PerfLogger.java:PerfLogEnd(177)) -
2017-09-27 06:29:26,087 ERROR [Atlas Logger 0]: hook.HiveHook
(HiveHook.java:run(205)) - Atlas hook failed due to error
java.lang.NoClassDefFoundError: org/apache/atlas/AtlasServiceException
at org.apache.atlas.hive.hook.HiveHook.collect(HiveHook.java:246)
at org.apache.atlas.hive.hook.HiveHook.access$200(HiveHook.java:83)
at org.apache.atlas.hive.hook.HiveHook$2$1.run(HiveHook.java:198)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1866)
at org.apache.atlas.hive.hook.HiveHook$2.run(HiveHook.java:195)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.ClassNotFoundException:
org.apache.atlas.AtlasServiceException
at java.lang.ClassLoader.findClass(ClassLoader.java:530)
at
org.apache.atlas.plugin.classloader.AtlasPluginClassLoader$MyClassLoader.findClass(AtlasPluginClassLoader.java:328)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at
org.apache.atlas.plugin.classloader.AtlasPluginClassLoader.loadClass(AtlasPluginClassLoader.java:136)
... 12 more
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (ATLAS-2177) offset is not reset when search by type is changed, leads to undesired results.
[ https://issues.apache.org/jira/browse/ATLAS-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16180633#comment-16180633 ] Sharmadha Sainath commented on ATLAS-2177: -- [~ayubkhan] Looks like duplicate of [ATLAS-2168|https://issues.apache.org/jira/browse/ATLAS-2168] > offset is not reset when search by type is changed, leads to undesired > results. > --- > > Key: ATLAS-2177 > URL: https://issues.apache.org/jira/browse/ATLAS-2177 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating >Reporter: Ayub Pathan >Priority: Critical > Fix For: 0.9-incubating > > Attachments: bug-snap2.mp4 > > > Attaching recording for reference. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2171) Accessing atlas via knox proxy without "/" at the end logs in as UNKNOWN user
Sharmadha Sainath created ATLAS-2171:
Summary: Accessing atlas via knox proxy without "/" at the end
logs in as UNKNOWN user
Key: ATLAS-2171
URL: https://issues.apache.org/jira/browse/ATLAS-2171
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 0.9-incubating
Reporter: Sharmadha Sainath
Priority: Critical
1. Enabled knox proxy for atlas.
2.Accessed Atlas UI via proxy using https://knox_gateway:8443/gateway/ui/atlas
3. Provided admin username and password and logged into Atlas
4. Now, opened another tab in browser with URL
{code}
https://knox_gateway:8443/gateway/ui/atlas
{code}
I was not logged in as admin but as an unknown user.No read/write operations
were allowed. Found the following application logs :
{code}
2017-09-26 05:39:31,467 ERROR - [pool-2-thread-9:] ~ Unable to find Atlas
Resource corresponding to :
Setting UNKNOWN (AtlasAuthorizationUtils:143)
{code}
If the URL is accessed with "/" at the end , logs in as admin user and all
operations work fine.
Example :
{code}
https://knox_gateway:8443/gateway/ui/atlas/
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (ATLAS-2164) Unable to execute the saved search query using its GUID
[
https://issues.apache.org/jira/browse/ATLAS-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharmadha Sainath resolved ATLAS-2164.
--
Resolution: Invalid
> Unable to execute the saved search query using its GUID
> ---
>
> Key: ATLAS-2164
> URL: https://issues.apache.org/jira/browse/ATLAS-2164
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Priority: Critical
>
> 1.Created and saved 2 searches - one basic , one Advanced.
> Following is the response of /api/atlas/v2/search/saved :
> {code}
> [
>{
> "guid":"153e89bb-eabb-4cc6-9cda-07c7ed084bac",
> "ownerName":"admin",
> "name":"basic_search1",
> "searchType":"BASIC",
> "searchParameters":{
> "query":"default",
> "typeName":"Asset",
> "classification":"tag3",
> "excludeDeletedEntities":true,
> "limit":0,
> "offset":0
> }
>},
>{
> "guid":"19be50af-bba1-424f-80e1-c49681b2bdeb",
> "ownerName":"admin",
> "name":"dsl_search_1",
> "searchType":"ADVANCED",
> "searchParameters":{
> "query":"where name=\"h1\"",
> "typeName":"hdfs_path",
> "excludeDeletedEntities":true,
> "limit":0,
> "offset":0
> }
>}
> ]
> {code}
> 2.Fired the following to execute basic saved query using its GUID:
> {code}
> http://localhost:21000/api/atlas/v2/search/saved/execute/153e89bb-eabb-4cc6-9cda-07c7ed084bac
> {code}
> Response :
> {code}
> {
> errorCode: "ATLAS-404-00-009",
> errorMessage: "Instance __AtlasUserSavedSearch with unique attribute
> {uniqueName=admin:153e89bb-eabb-4cc6-9cda-07c7ed084bac:BASIC} does not exist"
> }
> {code}
> Note : Logged in as admin while executing the "execute" query.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (ATLAS-2165) Limit set to 0 while executing saved query hence no results are fetched.
[
https://issues.apache.org/jira/browse/ATLAS-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharmadha Sainath resolved ATLAS-2165.
--
Resolution: Invalid
> Limit set to 0 while executing saved query hence no results are fetched.
>
>
> Key: ATLAS-2165
> URL: https://issues.apache.org/jira/browse/ATLAS-2165
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Priority: Blocker
>
> Fired REST call to execute a saved query using its name :
> {code}
> http://localhost:21000/api/atlas/v2/search/saved/execute/basic_search1
> {code}
> Following was the response :
> {code}
> {
>guid:"153e89bb-eabb-4cc6-9cda-07c7ed084bac",
>ownerName:"admin",
>name:"basic_search1",
>searchType:"BASIC",
>searchParameters:{
> query:"default",
> typeName:"Asset",
> classification:"tag3",
> excludeDeletedEntities:true,
> limit:0,
> offset:0
>}
> }
> {code}
> limit is set to 0 hence no entities are fetched though the query has many
> resulting entities.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (ATLAS-2165) Limit set to 0 while executing saved query hence no results are fetched.
Sharmadha Sainath created ATLAS-2165:
Summary: Limit set to 0 while executing saved query hence no
results are fetched.
Key: ATLAS-2165
URL: https://issues.apache.org/jira/browse/ATLAS-2165
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 0.9.1
Reporter: Sharmadha Sainath
Priority: Blocker
Fired REST call to execute a saved query using its name :
{code}
http://localhost:21000/api/atlas/v2/search/saved/execute/basic_search1
{code}
Following was the response :
{code}
{
guid:"153e89bb-eabb-4cc6-9cda-07c7ed084bac",
ownerName:"admin",
name:"basic_search1",
searchType:"BASIC",
searchParameters:{
query:"default",
typeName:"Asset",
classification:"tag3",
excludeDeletedEntities:true,
limit:0,
offset:0
}
}
{code}
limit is set to 0 hence no entities are fetched though the query has many
resulting entities.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ATLAS-2164) Unable to execute the saved search query using its GUID
[
https://issues.apache.org/jira/browse/ATLAS-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharmadha Sainath updated ATLAS-2164:
-
Description:
1.Created and saved 2 searches - one basic , one Advanced.
Following is the response of /api/atlas/v2/search/saved :
{code}
[
{
"guid":"153e89bb-eabb-4cc6-9cda-07c7ed084bac",
"ownerName":"admin",
"name":"basic_search1",
"searchType":"BASIC",
"searchParameters":{
"query":"default",
"typeName":"Asset",
"classification":"tag3",
"excludeDeletedEntities":true,
"limit":0,
"offset":0
}
},
{
"guid":"19be50af-bba1-424f-80e1-c49681b2bdeb",
"ownerName":"admin",
"name":"dsl_search_1",
"searchType":"ADVANCED",
"searchParameters":{
"query":"where name=\"h1\"",
"typeName":"hdfs_path",
"excludeDeletedEntities":true,
"limit":0,
"offset":0
}
}
]
{code}
2.Fired the following to execute basic saved query using its GUID:
{code}
http://localhost:21000/api/atlas/v2/search/saved/execute/153e89bb-eabb-4cc6-9cda-07c7ed084bac
{code}
Response :
{code}
{
errorCode: "ATLAS-404-00-009",
errorMessage: "Instance __AtlasUserSavedSearch with unique attribute
{uniqueName=admin:153e89bb-eabb-4cc6-9cda-07c7ed084bac:BASIC} does not exist"
}
{code}
Note : Logged in as admin while executing the "execute" query.
was:
1.Created and saved 2 searches - one basic , one Advanced.
Following is the response of /api/atlas/v2/search/saved :
{code}
[
{
"guid":"153e89bb-eabb-4cc6-9cda-07c7ed084bac",
"ownerName":"admin",
"name":"basic_search1",
"searchType":"BASIC",
"searchParameters":{
"query":"default",
"typeName":"Asset",
"classification":"tag3",
"excludeDeletedEntities":true,
"limit":0,
"offset":0
}
},
{
"guid":"19be50af-bba1-424f-80e1-c49681b2bdeb",
"ownerName":"admin",
"name":"dsl_search_1",
"searchType":"ADVANCED",
"searchParameters":{
"query":"where name=\"h1\"",
"typeName":"hdfs_path",
"excludeDeletedEntities":true,
"limit":0,
"offset":0
}
}
]
{code}
2.Fired the following to execute basic saved query using its GUID:
{code}
http://localhost:21000/api/atlas/v2/search/saved/execute/153e89bb-eabb-4cc6-9cda-07c7ed084bac
{code}
Response :
{code}
{
errorCode: "ATLAS-404-00-009",
errorMessage: "Instance __AtlasUserSavedSearch with unique attribute
{uniqueName=admin:153e89bb-eabb-4cc6-9cda-07c7ed084bac:BASIC} does not exist"
}
{code}
> Unable to execute the saved search query using its GUID
> ---
>
> Key: ATLAS-2164
> URL: https://issues.apache.org/jira/browse/ATLAS-2164
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9.1
>Reporter: Sharmadha Sainath
>Priority: Critical
>
> 1.Created and saved 2 searches - one basic , one Advanced.
> Following is the response of /api/atlas/v2/search/saved :
> {code}
> [
>{
> "guid":"153e89bb-eabb-4cc6-9cda-07c7ed084bac",
> "ownerName":"admin",
> "name":"basic_search1",
> "searchType":"BASIC",
> "searchParameters":{
> "query":"default",
> "typeName":"Asset",
> "classification":"tag3",
> "excludeDeletedEntities":true,
> "limit":0,
> "offset":0
> }
>},
>{
> "guid":"19be50af-bba1-424f-80e1-c49681b2bdeb",
> "ownerName":"admin",
> "name":"dsl_search_1",
> "searchType":"ADVANCED",
> "searchParameters":{
> "query":"where name=\"h1\"",
> "typeName":"hdfs_path",
> "excludeDeletedEntities":true,
> "limit":0,
> "offset":0
> }
>}
> ]
> {code}
> 2.Fired the following to execute basic saved query using its GUID:
> {code}
> http://localhost:21000/api/atlas/v2/search/saved/execute/153e89bb-eabb-4cc6-9cda-07c7ed084bac
> {code}
> Response :
> {code}
> {
> errorCode: "ATLAS-404-00-009",
> errorMessage: "Instance __AtlasUserSavedSearch with unique attribute
> {uniqueName=admin:153e89bb-eabb-4cc6-9cda-07c7ed084bac:BASIC} does not exist"
> }
> {code}
> Note : Logged in as admin while executing the "execute" query.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (ATLAS-2164) Unable to execute the saved search query using its GUID
Sharmadha Sainath created ATLAS-2164:
Summary: Unable to execute the saved search query using its GUID
Key: ATLAS-2164
URL: https://issues.apache.org/jira/browse/ATLAS-2164
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 0.9.1
Reporter: Sharmadha Sainath
Priority: Critical
1.Created and saved 2 searches - one basic , one Advanced.
Following is the response of /api/atlas/v2/search/saved :
{code}
[
{
"guid":"153e89bb-eabb-4cc6-9cda-07c7ed084bac",
"ownerName":"admin",
"name":"basic_search1",
"searchType":"BASIC",
"searchParameters":{
"query":"default",
"typeName":"Asset",
"classification":"tag3",
"excludeDeletedEntities":true,
"limit":0,
"offset":0
}
},
{
"guid":"19be50af-bba1-424f-80e1-c49681b2bdeb",
"ownerName":"admin",
"name":"dsl_search_1",
"searchType":"ADVANCED",
"searchParameters":{
"query":"where name=\"h1\"",
"typeName":"hdfs_path",
"excludeDeletedEntities":true,
"limit":0,
"offset":0
}
}
]
{code}
2.Fired the following to execute basic saved query using its GUID:
{code}
http://localhost:21000/api/atlas/v2/search/saved/execute/153e89bb-eabb-4cc6-9cda-07c7ed084bac
{code}
Response :
{code}
{
errorCode: "ATLAS-404-00-009",
errorMessage: "Instance __AtlasUserSavedSearch with unique attribute
{uniqueName=admin:153e89bb-eabb-4cc6-9cda-07c7ed084bac:BASIC} does not exist"
}
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (ATLAS-2161) UI : Save Search Query: Search button is not enabled when a saved search has only "Query" without typename / classification
Sharmadha Sainath created ATLAS-2161: Summary: UI : Save Search Query: Search button is not enabled when a saved search has only "Query" without typename / classification Key: ATLAS-2161 URL: https://issues.apache.org/jira/browse/ATLAS-2161 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 0.9.1 Reporter: Sharmadha Sainath Priority: Minor 1.Fired a basic search : query = table1 (without typename and classification name). Now Search button was enabled. 2.Saved the search as hive_table_search. 3.Cleared the search. 4.Clicked on the saved search - hive_table_search. 5.table1 was populated in the query text box. But Search button was not enabled. 6.But on clicking the "..." on the hive_table_search and selecting "Search" option fired the search and fetched the entity. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2153) UI : Adding more columns to the search table masks the "Remove tag" button
Sharmadha Sainath created ATLAS-2153: Summary: UI : Adding more columns to the search table masks the "Remove tag" button Key: ATLAS-2153 URL: https://issues.apache.org/jira/browse/ATLAS-2153 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 0.9-incubating, 0.9.1 Reporter: Sharmadha Sainath Priority: Minor For basic search typename = hive_table , 20 attributes can be added in the columns filter. When more attributes are added , "Remove Tag" (Cross button) on the Tag under Tags column is masked. This happens when the screen size is less and more columns are added. When columns are removed , Remove button shows up again. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2151) Search using entity and trait attributes - OR condition considers only the first criterion in the list
[
https://issues.apache.org/jira/browse/ATLAS-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharmadha Sainath updated ATLAS-2151:
-
Summary: Search using entity and trait attributes - OR condition considers
only the first criterion in the list (was: Search using entity and trait
attributes - OR condition takes only the first parameter)
> Search using entity and trait attributes - OR condition considers only the
> first criterion in the list
> ---
>
> Key: ATLAS-2151
> URL: https://issues.apache.org/jira/browse/ATLAS-2151
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9-incubating, 0.9.1
>Reporter: Sharmadha Sainath
>Priority: Critical
>
> 1.Created 2 hive_table entities by name : table1 and table2.
> 2. Fired basic search query with following POST body :
> {code}
> {
>"entityFilters":{
> "condition":"OR",
> "criterion":[
> {
> "attributeName":"name",
> "operator":"=",
> "attributeValue":"table1"
> },
> {
> "attributeName":"name",
> "operator":"=",
> "attributeValue":"table2"
> }
> ]
>},
>"tagFilters":null,
>"attributes":[
>],
>"query":null,
>"limit":25,
>"offset":0,
>"typeName":"hive_table",
>"classification":null,
>"excludeDeletedEntities": false
> }
> {code}
> 2. Expected the response would return both table1 and table2.
> 3. Only table1 (first filter) is returned. Any filter other than "!=" in the
> second condition doesn't fetch expected results.
> 4. Also when "excludeDeletedEntities" is set to true , though table1 and
> table2 are ACTIVE , no entity is returned.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (ATLAS-2151) Search using entity and trait attributes - OR condition takes only the first parameter
Sharmadha Sainath created ATLAS-2151:
Summary: Search using entity and trait attributes - OR condition
takes only the first parameter
Key: ATLAS-2151
URL: https://issues.apache.org/jira/browse/ATLAS-2151
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 0.9-incubating, 0.9.1
Reporter: Sharmadha Sainath
Priority: Critical
1.Created 2 hive_table entities by name : table1 and table2.
2. Fired basic search query with following POST body :
{code}
{
"entityFilters":{
"condition":"OR",
"criterion":[
{
"attributeName":"name",
"operator":"=",
"attributeValue":"table1"
},
{
"attributeName":"name",
"operator":"=",
"attributeValue":"table2"
}
]
},
"tagFilters":null,
"attributes":[
],
"query":null,
"limit":25,
"offset":0,
"typeName":"hive_table",
"classification":null,
"excludeDeletedEntities": false
}
{code}
2. Expected the response would return both table1 and table2.
3. Only table1 (first filter) is returned. Any filter other than "!=" in the
second condition doesn't fetch expected results.
4. Also when "excludeDeletedEntities" is set to true , though table1 and table2
are ACTIVE , no entity is returned.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (ATLAS-2142) Regression : Disassociating tag from Entity and Editing tag attributes associated to an entity throw NPE
[ https://issues.apache.org/jira/browse/ATLAS-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharmadha Sainath resolved ATLAS-2142. -- Resolution: Duplicate Duplicate of [ATLAS-2141|https://issues.apache.org/jira/browse/ATLAS-2142] . Filed twice by mistake when Apache was down for some time. > Regression : Disassociating tag from Entity and Editing tag attributes > associated to an entity throw NPE > > > Key: ATLAS-2142 > URL: https://issues.apache.org/jira/browse/ATLAS-2142 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.9-incubating >Reporter: Sharmadha Sainath > > Editing tag attribute value associated to an entity throws 500 Internal > server error with NPE and with Error Notification "Tag could not be > added". > Disassociating a tag from an entity also throws 500 Internal server error > with NPE , and with Error Notification "Tag could not be deleted". > Tag addition works fine. > This is a regression caused after > [ATLAS-2100|https://issues.apache.org/jira/browse/ATLAS-2100]. > Attached the exception stack trace seen for both cases. > CC :[~ashutoshm] [~madhan.neethiraj] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2142) Regression : Disassociating tag from Entity and Editing tag attributes associated to an entity throw NPE
Sharmadha Sainath created ATLAS-2142: Summary: Regression : Disassociating tag from Entity and Editing tag attributes associated to an entity throw NPE Key: ATLAS-2142 URL: https://issues.apache.org/jira/browse/ATLAS-2142 Project: Atlas Issue Type: Bug Components: atlas-core Affects Versions: 0.9-incubating Reporter: Sharmadha Sainath Editing tag attribute value associated to an entity throws 500 Internal server error with NPE and with Error Notification "Tag could not be added". Disassociating a tag from an entity also throws 500 Internal server error with NPE , and with Error Notification "Tag could not be deleted". Tag addition works fine. This is a regression caused after [ATLAS-2100|https://issues.apache.org/jira/browse/ATLAS-2100]. Attached the exception stack trace seen for both cases. CC :[~ashutoshm] [~madhan.neethiraj] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2141) Regression : Disassociating tag from Entity and Editing tag attributes associated to an entity throw NPE
Sharmadha Sainath created ATLAS-2141: Summary: Regression : Disassociating tag from Entity and Editing tag attributes associated to an entity throw NPE Key: ATLAS-2141 URL: https://issues.apache.org/jira/browse/ATLAS-2141 Project: Atlas Issue Type: Bug Components: atlas-core Affects Versions: 0.9-incubating Reporter: Sharmadha Sainath Attachments: NPE_during_tag_delete.txt, NPE_during_tag_edit.txt Editing tag attribute value associated to an entity throws 500 Internal server error with NPE and with Error Notification "Tag could not be added". Disassociating a tag from an entity also throws 500 Internal server error with NPE , and with Error Notification "Tag could not be deleted". Tag addition works fine. This is a regression caused after [ATLAS-2100|https://issues.apache.org/jira/browse/ATLAS-2100]. Attached the exception stack trace seen for both cases. CC :[~ashutoshm] [~madhan.neethiraj] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2132) Error code during invalid file path/unreadable file provided during import
Sharmadha Sainath created ATLAS-2132:
Summary: Error code during invalid file path/unreadable file
provided during import
Key: ATLAS-2132
URL: https://issues.apache.org/jira/browse/ATLAS-2132
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 0.9-incubating
Reporter: Sharmadha Sainath
Priority: Minor
When firing import command using
{code}
/api/atlas/admin/importfile
{code}
when file provided in the import_options.json doesn't have read permission or
file is not present , Atlas throws 500 Internal server error but with proper
error message.
Example :
{code}
{"errorCode":"ATLAS-500-00-001","errorMessage":"org.apache.atlas.exception.AtlasBaseException:
invalid parameters: /exportimport/db5.zip: file not found"}
{code}
{code}
{"errorCode":"ATLAS-500-00-001","errorMessage":"org.apache.atlas.exception.AtlasBaseException:
java.io.IOException: File '/exportimport/db6.zip' cannot be read"}
{code}
Expected that Atlas would throw 400 Bad Request instead of 500 Internal Server
error.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (ATLAS-2131) Issues during navigation from table in Tables tab with Include historical entities checked
[
https://issues.apache.org/jira/browse/ATLAS-2131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16164207#comment-16164207
]
Sharmadha Sainath commented on ATLAS-2131:
--
CC : [~kevalbhatt] [~madhan.neethiraj]
> Issues during navigation from table in Tables tab with Include historical
> entities checked
> --
>
> Key: ATLAS-2131
> URL: https://issues.apache.org/jira/browse/ATLAS-2131
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
> Attachments: TablesInDbNavigation.mov
>
>
> Following is one of the scenarios where there is issue when navigating. Not
> sure what other scenarios can also lead to the issue.
> 1.Created 100 hive_table entities in a database db1.
> 2. Fired basic query hive_db = db1.
> 3. In the Tables tab of db1 , all 100 tables were listed.
> 4.Checked Include historical entities check box. Now , URL changed to
> {code}
> localhost:21000/#!/search/searchResult?guid=8c7549db-c514-419e-bc2c-f3fe9e3c34f6=relationship=true=true
> {code}
> 5.Clicked on any of the tables in the result which landed in the detailsPage
> of the table.
> 6.Now , when "Back To Results" button is clicked , URL changed to
> {code}
> http://localhost:21000/#!/search/searchResult?guid=8c7549db-c514-419e-bc2c-f3fe9e3c34f6=relationship=true=true
> {code}
> and landed in Atlas home page (ie. Search page) with all search cleared.
> 7. Fired some basic query and clicked Search . Search was not functioning.
> 8.Switched from Basic - DSL - Basic . Now fired search again . This time
> search was working . But Include Historical entities was checked on by
> default.
> 9. If Include historical entities was not checked in Tables tab and any
> entity was selected , this issue was not seen.
> Added a screen recording of the scenario explained above.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ATLAS-2131) Issues during navigation from table in Tables tab with Include historical entities checked
[
https://issues.apache.org/jira/browse/ATLAS-2131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharmadha Sainath updated ATLAS-2131:
-
Summary: Issues during navigation from table in Tables tab with Include
historical entities checked (was: Issues during navigation from deleted table
in Tables tab)
> Issues during navigation from table in Tables tab with Include historical
> entities checked
> --
>
> Key: ATLAS-2131
> URL: https://issues.apache.org/jira/browse/ATLAS-2131
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
> Attachments: TablesInDbNavigation.mov
>
>
> Following is one of the scenarios where there is issue when navigating. Not
> sure what other scenarios can also lead to the issue.
> 1.Created 100 hive_table entities in a database db1.
> 2. Fired basic query hive_db = db1.
> 3. In the Tables tab of db1 , all 100 tables were listed.
> 4.Checked Include historical entities check box. Now , URL changed to
> {code}
> localhost:21000/#!/search/searchResult?guid=8c7549db-c514-419e-bc2c-f3fe9e3c34f6=relationship=true=true
> {code}
> 5.Clicked on any of the tables in the result which landed in the detailsPage
> of the table.
> 6.Now , when "Back To Results" button is clicked , URL changed to
> {code}
> http://localhost:21000/#!/search/searchResult?guid=8c7549db-c514-419e-bc2c-f3fe9e3c34f6=relationship=true=true
> {code}
> and landed in Atlas home page (ie. Search page) with all search cleared.
> 7. Fired some basic query and clicked Search . Search was not functioning.
> 8.Switched from Basic - DSL - Basic . Now fired search again . This time
> search was working . But Include Historical entities was checked on by
> default.
> 9. If Include historical entities was not checked in Tables tab and any
> entity was selected , this issue was not seen.
> Added a screen recording of the scenario explained above.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (ATLAS-2131) Issues during navigation from deleted table in Tables tab
Sharmadha Sainath created ATLAS-2131:
Summary: Issues during navigation from deleted table in Tables tab
Key: ATLAS-2131
URL: https://issues.apache.org/jira/browse/ATLAS-2131
Project: Atlas
Issue Type: Bug
Components: atlas-webui
Affects Versions: 0.9-incubating
Reporter: Sharmadha Sainath
Attachments: TablesInDbNavigation.mov
Following is one of the scenarios where there is issue when navigating. Not
sure what other scenarios can also lead to the issue.
1.Created 100 hive_table entities in a database db1.
2. Fired basic query hive_db = db1.
3. In the Tables tab of db1 , all 100 tables were listed.
4.Checked Include historical entities check box. Now , URL changed to
{code}
localhost:21000/#!/search/searchResult?guid=8c7549db-c514-419e-bc2c-f3fe9e3c34f6=relationship=true=true
{code}
5.Clicked on any of the tables in the result which landed in the detailsPage of
the table.
6.Now , when "Back To Results" button is clicked , URL changed to
{code}
http://localhost:21000/#!/search/searchResult?guid=8c7549db-c514-419e-bc2c-f3fe9e3c34f6=relationship=true=true
{code}
and landed in Atlas home page (ie. Search page) with all search cleared.
7. Fired some basic query and clicked Search . Search was not functioning.
8.Switched from Basic - DSL - Basic . Now fired search again . This time
search was working . But Include Historical entities was checked on by default.
9. If Include historical entities was not checked in Tables tab and any entity
was selected , this issue was not seen.
Added a screen recording of the scenario explained above.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ATLAS-2130) Call made to fetch tables of a database doesn't have exlcudeDeletedEntities parameter
[
https://issues.apache.org/jira/browse/ATLAS-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharmadha Sainath updated ATLAS-2130:
-
Description:
Following is the query fired to fetch the tables in a db :
{code}
http://localhost:21000/api/atlas/v2/search/relationship?limit=25=8b110b04-b5ad-4738-b7f7-576cc85b2fd4=__hive_table.db=name=ASCENDING&_=1505280717115
{code}
Since exlcudeDeletedEntities=true is not set in the param , deleted tables are
also shown in the Tables tab of a hive_database's detailPage.
was:
Following is the query fired to fetch the tables in a db :
{code}
http://localhost:21000/api/atlas/v2/search/relationship?limit=25=8b110b04-b5ad-4738-b7f7-576cc85b2fd4=__hive_table.db=name=ASCENDING&_=1505280717115
{code}
Since exlcudeDeletedEntities=true is not set in the param , deleted tables are
also shown in the Tables tab.
> Call made to fetch tables of a database doesn't have exlcudeDeletedEntities
> parameter
> -
>
> Key: ATLAS-2130
> URL: https://issues.apache.org/jira/browse/ATLAS-2130
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9.1
>Reporter: Sharmadha Sainath
>
> Following is the query fired to fetch the tables in a db :
> {code}
> http://localhost:21000/api/atlas/v2/search/relationship?limit=25=8b110b04-b5ad-4738-b7f7-576cc85b2fd4=__hive_table.db=name=ASCENDING&_=1505280717115
> {code}
> Since exlcudeDeletedEntities=true is not set in the param , deleted tables
> are also shown in the Tables tab of a hive_database's detailPage.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ATLAS-2130) Call made to fetch tables of a database doesn't have exlcudeDeletedEntities parameter
[
https://issues.apache.org/jira/browse/ATLAS-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharmadha Sainath updated ATLAS-2130:
-
Affects Version/s: 0.9.1
Description:
Following is the query fired to fetch the tables in a db :
{code}
http://localhost:21000/api/atlas/v2/search/relationship?limit=25=8b110b04-b5ad-4738-b7f7-576cc85b2fd4=__hive_table.db=name=ASCENDING&_=1505280717115
{code}
Since exlcudeDeletedEntities=true is not set in the param , deleted tables are
also shown in the Tables tab.
Component/s: atlas-core
Summary: Call made to fetch tables of a database doesn't have
exlcudeDeletedEntities parameter (was: Tables tab in details view of )
> Call made to fetch tables of a database doesn't have exlcudeDeletedEntities
> parameter
> -
>
> Key: ATLAS-2130
> URL: https://issues.apache.org/jira/browse/ATLAS-2130
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9.1
>Reporter: Sharmadha Sainath
>
> Following is the query fired to fetch the tables in a db :
> {code}
> http://localhost:21000/api/atlas/v2/search/relationship?limit=25=8b110b04-b5ad-4738-b7f7-576cc85b2fd4=__hive_table.db=name=ASCENDING&_=1505280717115
> {code}
> Since exlcudeDeletedEntities=true is not set in the param , deleted tables
> are also shown in the Tables tab.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (ATLAS-2130) Tables tab in details view of
Sharmadha Sainath created ATLAS-2130: Summary: Tables tab in details view of Key: ATLAS-2130 URL: https://issues.apache.org/jira/browse/ATLAS-2130 Project: Atlas Issue Type: Bug Reporter: Sharmadha Sainath -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2127) Import of an entity associated with a tag into backup cluster with updateTypeDefinition options set to false
[
https://issues.apache.org/jira/browse/ATLAS-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharmadha Sainath updated ATLAS-2127:
-
Attachment: hdfs_path1.zip
[~ashutoshm] , Attached a zip file containing an hdfs_path attached to a tag
tag1.
Import_options.json :
{code}
{
"options":{
"updateTypeDefinition":false
}
}
{code}
Steps to reproduce :
Import the zip file into the cluster which doesn't have a tag named tag1 with
import option updateTypeDefinition set to false.
> Import of an entity associated with a tag into backup cluster with
> updateTypeDefinition options set to false
>
>
> Key: ATLAS-2127
> URL: https://issues.apache.org/jira/browse/ATLAS-2127
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Ashutosh Mestry
> Attachments: hdfs_path1.zip, ImportExceptionWithTag.txt
>
>
> 1. On cluster1 , created an entity and associated it to a tag.
> 2. Exported the entity into a zipfile.
> 3. cluster2 is in clean state.(i.e no entity / tag is created)
> 4. Tried to import the entity zip into cluster2 with import option
> "updateTypeDefinition" set to false.
> 5. Import failed with NPE.
> Since updateTypeDefinition is set to false , NPE is thrown when the entity is
> attempted to be associated to the tag in the backup cluster.
> This is the expected behavior , but the cause of the issue is not very
> explicit to the end user when Atlas throws NPE.
> Attached the exception stack trace.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (ATLAS-2129) Atlas shutdown during progress of bulk import throws ConcurrentModificationException
Sharmadha Sainath created ATLAS-2129:
Summary: Atlas shutdown during progress of bulk import throws
ConcurrentModificationException
Key: ATLAS-2129
URL: https://issues.apache.org/jira/browse/ATLAS-2129
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 0.9-incubating
Reporter: Sharmadha Sainath
Priority: Blocker
1. Exported an hive_db containing 300 hive_table entities from cluster1 into a
zip file .
2. Tried to import into cluster2.
3. When the import was in progress ( at 34%) , stopped Atlas.
4. Following exception was seen in application logs of cluster2 :
{code}
2017-09-11 10:17:09,192 INFO - [pool-2-thread-9 -
83fe24a2-ff2b-4add-a94e-a54b09090912:] ~ bulkImport(): progress: 34% (of 301) -
entity:last-imported:hive_table:[102]:(2d629a8e-5c94-40e8-b83f-8a9c91c6de8d)
(AtlasEntityStoreV1:238)
2017-09-11 10:17:09,340 ERROR - [SIGTERM handler:] ~ Could not commit
transaction [1] due to exception (StandardTitanGraph:731)
java.util.ConcurrentModificationException
at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901)
at java.util.ArrayList$Itr.next(ArrayList.java:851)
at
atlas.shaded.titan.guava.common.collect.Iterators$7.computeNext(Iterators.java:701)
at
atlas.shaded.titan.guava.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143)
at
atlas.shaded.titan.guava.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138)
at
com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.prepareCommit(StandardTitanGraph.java:473)
at
com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.commit(StandardTitanGraph.java:654)
at
com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.commit(StandardTitanTx.java:1337)
at
com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.shutdown(TitanBlueprintsGraph.java:120)
at
com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.shutdownInternal(StandardTitanGraph.java:171)
at
com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.access$700(StandardTitanGraph.java:75)
at
com.thinkaurelius.titan.graphdb.database.StandardTitanGraph$ShutdownThread.start(StandardTitanGraph.java:756)
at
java.lang.ApplicationShutdownHooks.runHooks(ApplicationShutdownHooks.java:102)
at
java.lang.ApplicationShutdownHooks$1.run(ApplicationShutdownHooks.java:46)
at java.lang.Shutdown.runHooks(Shutdown.java:123)
at java.lang.Shutdown.sequence(Shutdown.java:167)
at java.lang.Shutdown.exit(Shutdown.java:212)
at java.lang.Terminator$1.handle(Terminator.java:52)
at sun.misc.Signal$1.run(Signal.java:212)
at java.lang.Thread.run(Thread.java:748)
{code}
Other operations that are called during Atlas shut down such as Shutdown hook ,
Stopping KafkaNotification service , NotificationHookConsumer ,
HBaseBasedAuditRepository are not called.
5.After that , restarted Atlas. Atlas functioned properly.
6.Resumed import with import option , startGuid=
7. Import completed successfully.
8.Post import, only entities from 33% to 100% were imported . Initial 32% of
the entities were not imported.
9.Fired an import command again without any interruption and without specifying
the startGUID. All 300 hive_table entities and 1 hive_db were imported
successfully.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (ATLAS-2128) UI Regression : DSL Results pagination doesn't spawn more than 2 pages
Sharmadha Sainath created ATLAS-2128: Summary: UI Regression : DSL Results pagination doesn't spawn more than 2 pages Key: ATLAS-2128 URL: https://issues.apache.org/jira/browse/ATLAS-2128 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 0.9-incubating, 0.8.1-incubating Reporter: Sharmadha Sainath Priority: Blocker 1. Created 300 hive_tables. 2. On Basic Search in UI , fired search typename= hive_table 3. hive_table results were fetched across 12 pages - 25 entities in each page - which is the correct behavior. 4.On Advanced Search in UI , fired search typename = hive_table * In the 1st page , 1- 25 results were shown. * On clicking next , in the 2nd page , 26 - 50 results were shown * On clicking next , Expected to land in 3rd page with 51 - 75 results , but , 26-50 results were loaded again and the Next Button was disabled. Calls made to the Atlas backend seem to be correct. On clicking "Next" each time , correct set of results were fetched. For example , call was made to fetch entities from offset 50 , limit = 25 , but the UI still showed 26-50 results and disabled "Next" button. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2127) Import of an entity associated with a tag into backup cluster with updateTypeDefinition options set to false
Sharmadha Sainath created ATLAS-2127: Summary: Import of an entity associated with a tag into backup cluster with updateTypeDefinition options set to false Key: ATLAS-2127 URL: https://issues.apache.org/jira/browse/ATLAS-2127 Project: Atlas Issue Type: Bug Components: atlas-core Affects Versions: 0.9-incubating Reporter: Sharmadha Sainath Attachments: ImportExceptionWithTag.txt 1. On cluster1 , created an entity and associated it to a tag. 2. Exported the entity into a zipfile. 3. cluster2 is in clean state.(i.e no entity / tag is created) 4. Tried to import the entity zip into cluster2 with import option "updateTypeDefinition" set to false. 5. Import failed with NPE. Since updateTypeDefinition is set to false , NPE is thrown when the entity is attempted to be associated to the tag in the backup cluster. This is the expected behavior , but the cause of the issue is not very explicit to the end user when Atlas throws NPE. Attached the exception stack trace. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-2120) Inconsistency in Importing already existing types on backup cluster with new definition.
[
https://issues.apache.org/jira/browse/ATLAS-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158887#comment-16158887
]
Sharmadha Sainath commented on ATLAS-2120:
--
Steps to reproduce :
1. On cluster1 , created an hdfs_path with qualifiedname : path1
2.Created a tag on cluster1 - tag1 with attributes attrib1 : string ,
attrib2:int
3.Associated tag1 to path1 with values attrib1: randstr , attrib2:5
hdfs_path1.json
{code}
{
"itemsToExport": [
{ "typeName": "hdfs_path", "uniqueAttributes": { "qualifiedName": "path1" } }
],
"options": null
}
{code}
4.Exported into zip file [^hdfs_path1.zip] using command :
{code}
curl -v -X POST -u admin:admin -H "Content-Type: application/json" -H
"Cache-Control: no-cache" -d @hdfs_path1.json
"http://host1:21000/api/atlas/admin/export; > hdfs_path1.zip
{code}
5.Tried to import to cluster2 using :
{code}
curl -v -X POST -u admin:admin -H "Content-Type: multipart/form-data" -H
"Cache-Control: no-cache" -F data=@hdfs_path1.zip
"http://host2:21000/api/atlas/admin/import;
{code}
6 . Following exception was thrown :
{code}
{"errorCode":"ATLAS-500-00-001","errorMessage":"org.apache.atlas.exception.AtlasBaseException:
org.apache.atlas.repository.graphdb.AtlasSchemaViolationException:
com.thinkaurelius.titan.core.SchemaViolationException: Value [randstr] is not
an instance of the expected data type for property key [tag1.attrib1] and
cannot be converted. Expected: class java.lang.Long, found: class
java.lang.String"}
{code}
CC : [~ashutoshm]
> Inconsistency in Importing already existing types on backup cluster with new
> definition.
>
>
> Key: ATLAS-2120
> URL: https://issues.apache.org/jira/browse/ATLAS-2120
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Ashutosh Mestry
>Priority: Critical
> Attachments: hdfs_path1.zip
>
>
> 1.Created a tag tag1 on cluster1 with attributes :
> * attrib1 : string
> * attrib2 : integer
> 2.Created a tag with same name on cluster2 with attributes:
> *attrib1: date
> *attrib3: integer
> (Note the tag names are same , and attrib1 is same but datatypes of attrib1
> are different in both the clusters)
> 3. On cluster1 , created an entity and associated the tag1 to the entity with
> attribute values
> *attrib1: "randstr"
> *attrib2: 5
> and exported the entity into zip file .
> 4.Tried to import the entity into cluster2.
> Import failed with 500 Internal server error and with following exception :
> {code}
> {"errorCode":"ATLAS-500-00-001","errorMessage":"org.apache.atlas.exception.AtlasBaseException:
> org.apache.atlas.repository.graphdb.AtlasSchemaViolationException:
> com.thinkaurelius.titan.core.SchemaViolationException: Value [rand_str] is
> not an instance of the expected data type for property key [tag1.attrib1] and
> cannot be converted. Expected: class java.lang.Long, found: class
> java.lang.String"}
> {code}
> Following is the inconsistency observed :
> Entity is not imported into the cluster2 , but the type definition of tag1 in
> cluster2 had 3 attributes now (attrib1 : date , attrib2:Integer ,
> attrib3:Integer) and 500 Internal server error is thrown.
> Normally, when a datatype of an attribute is attempted to be updated , Atlas
> throws the following exception and the type is not updated.
> {code}
> {"errorCode":"ATLAS-400-00-029","errorMessage":"Data type update for
> attribute is not supported"}
> {code}
> Expected the same to happen while importing (i.e) Import failing with Bad
> request with the proper error message.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (ATLAS-2124) Difference is results of Basic search and DSL search when an entity is associated to the child tag containing a super tag
Sharmadha Sainath created ATLAS-2124:
Summary: Difference is results of Basic search and DSL search when
an entity is associated to the child tag containing a super tag
Key: ATLAS-2124
URL: https://issues.apache.org/jira/browse/ATLAS-2124
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 0.9-incubating
Reporter: Sharmadha Sainath
Priority: Critical
1.Created a tag super_tag .
2.Created a tag child_tag with superType as super_tag.
3.Associated an entity to child_tag.
4.Basic query :
{code}
http://localhost:21000/api/atlas/v2/search/basic?typeName=hdfs_path=child_tag
http://localhost:21000/api/atlas/v2/search/basic?typeName=hdfs_path=super_tag
{code}
Both returned the entity.
DSL search :
{code}
http://localhost:21000/api/atlas/v2/search/dsl?typeName=hdfs_path=child_tag
{code}
returned the correct entity.
whereas
{code}
http://localhost:21000/api/atlas/v2/search/dsl?typeName=hdfs_path=super_tag
{code}
returned 0 results.
Following log is found in application.log for the DSL Search of tags.
{code}
WARN - [pool-1-thread-10 - 51ba13c9-493c-4c62-b11c-a8513ba771e9:] ~ Found
non-extractable argument '_().out('super_tag')' in the 'and' expression
'g.V().or(has('__typeName','hdfs_path'),has('__superTypeNames','hdfs_path')).as('a0').and(_().out('super_tag'))'
(ExpandAndsOptimization:111)
{code}
The above log is not specific to search with parent tag. Such log is printed
for search with child tags also.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (ATLAS-2121) Inconsistency in basic search results due to case sensitivity of type names
Sharmadha Sainath created ATLAS-2121:
Summary: Inconsistency in basic search results due to case
sensitivity of type names
Key: ATLAS-2121
URL: https://issues.apache.org/jira/browse/ATLAS-2121
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 0.8-incubating, 0.9-incubating
Reporter: Sharmadha Sainath
Priority: Critical
Type names are case sensitive hence 2 types can be created with different
cases.
Example :
1. type1 with attributes a , b
2. TYPE1 with attributes c , d
The types creation succeeds and
{code}
/api/atlas/v2/types/entitydef/name/type1
/api/atlas/v2/types/entitydef/name/TYPE1
{code}
return the corresponding type definitions correctly.
When an entity e1 of type1 is created,
and when a BASIC search is fired with
typeName= type1 , e1 is returned and
typeName=TYPE1 also , e1 is returned.
But in the case of DSL search ,
typeName = type1 returns e1
typeName = TYPE1 doesn't return any result - which is the correct behavior.
This issue is major from tag side too because , UI Tag search is Basic and
returns entity tagged with tag1 when searched for tag1 or TAG1.
Whereas DSL search with
classification=tag1 returns entity
classification=TAG1 does not return any entity. - which is the correct behavior.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ATLAS-2120) Inconsistency in Importing already existing types on backup cluster with new definition.
[
https://issues.apache.org/jira/browse/ATLAS-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharmadha Sainath updated ATLAS-2120:
-
Description:
1.Created a tag tag1 on cluster1 with attributes :
* attrib1 : string
* attrib2 : integer
2.Created a tag with same name on cluster2 with attributes:
*attrib1: date
*attrib3: integer
(Note the tag names are same , and attrib1 is same but datatypes of attrib1 are
different in both the clusters)
3. On cluster1 , created an entity and associated the tag1 to the entity with
attribute values
*attrib1: "randstr"
*attrib2: 5
and exported the entity into zip file .
4.Tried to import the entity into cluster2.
Import failed with 500 Internal server error and with following exception :
{code}
{"errorCode":"ATLAS-500-00-001","errorMessage":"org.apache.atlas.exception.AtlasBaseException:
org.apache.atlas.repository.graphdb.AtlasSchemaViolationException:
com.thinkaurelius.titan.core.SchemaViolationException: Value [rand_str] is not
an instance of the expected data type for property key [tag1.attrib1] and
cannot be converted. Expected: class java.lang.Long, found: class
java.lang.String"}
{code}
Following is the inconsistency observed :
Entity is not imported into the cluster2 , but the type definition of tag1 in
cluster2 had 3 attributes now (attrib1 : date , attrib2:Integer ,
attrib3:Integer) and 500 Internal server error is thrown.
Normally, when a datatype of an attribute is attempted to be updated , Atlas
throws the following exception and the type is not updated.
{code}
{"errorCode":"ATLAS-400-00-029","errorMessage":"Data type update for attribute
is not supported"}
{code}
Expected the same to happen while importing (i.e) Import failing with Bad
request with the proper error message.
was:
1.Created a tag tag1 on cluster1 with attributes :
* attrib1 : string
* attrib2 : integer
2.Created a tag with same name on cluster2 with attributes:
*attrib1: date
*attrib3: integer
(Note the tag names are same , and attrib1 is same but datatypes of attrib1 are
different in both the clusters)
3. On cluster1 , created an entity and associated the tag1 to the entity with
attribute values
*attrib1: "randstr"
*attrib2: 5
and exported the entity into zip file .
4.Tried to import the entity into cluster2.
Import failed with 500 Internal server error and with following exception :
{code}
{"errorCode":"ATLAS-500-00-001","errorMessage":"org.apache.atlas.exception.AtlasBaseException:
org.apache.atlas.repository.graphdb.AtlasSchemaViolationException:
com.thinkaurelius.titan.core.SchemaViolationException: Value [rand_str] is not
an instance of the expected data type for property key [tag1.attrib1] and
cannot be converted. Expected: class java.lang.Long, found: class
java.lang.String"}
{code}
Following is the inconsistency observed :
Entity is not imported into the cluster2 , but the type definition of tag1 in
cluster2 had 3 attributes now (attrib1 : string , attrib2:Integer ,
attrib3:Integer) and 500 Internal server error is thrown.
Normally, when a datatype of an attribute is attempted to be updated , Atlas
throws the following exception and the type is not updated.
{code}
{"errorCode":"ATLAS-400-00-029","errorMessage":"Data type update for attribute
is not supported"}
{code}
Expected the same to happen while importing (i.e) Import failing with Bad
request with the proper error message.
> Inconsistency in Importing already existing types on backup cluster with new
> definition.
>
>
> Key: ATLAS-2120
> URL: https://issues.apache.org/jira/browse/ATLAS-2120
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Priority: Critical
>
> 1.Created a tag tag1 on cluster1 with attributes :
> * attrib1 : string
> * attrib2 : integer
> 2.Created a tag with same name on cluster2 with attributes:
> *attrib1: date
> *attrib3: integer
> (Note the tag names are same , and attrib1 is same but datatypes of attrib1
> are different in both the clusters)
> 3. On cluster1 , created an entity and associated the tag1 to the entity with
> attribute values
> *attrib1: "randstr"
> *attrib2: 5
> and exported the entity into zip file .
> 4.Tried to import the entity into cluster2.
> Import failed with 500 Internal server error and with following exception :
> {code}
>
