[jira] [Resolved] (ATLAS-4187) Jackson-databind version 2.10.0 doesn't match with Hive version 3.1.2 on EMR 6.X

2021-04-05 Thread Ricardo (Jira)


 [ 
https://issues.apache.org/jira/browse/ATLAS-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ricardo resolved ATLAS-4187.

Fix Version/s: 2.1.0
   Resolution: Not A Problem

On EMR 6.1 Atlas 2.1 works fine.

>  Jackson-databind version 2.10.0 doesn't match with Hive version 3.1.2 on EMR 
> 6.X 
> --
>
> Key: ATLAS-4187
> URL: https://issues.apache.org/jira/browse/ATLAS-4187
> Project: Atlas
>  Issue Type: Bug
>  Components: hive-integration
>Affects Versions: 2.1.0
>Reporter: Ricardo
>Priority: Major
> Fix For: 2.1.0
>
>
>  After create the link jackson-databind-2.10.0.jar to /usr/lib/hive/lib 
> hiveserver2 stops to work and return this log:
> 2021-03-05T20:44:58,774 INFO [main([])]: server.HiveServer2 
> (HiveServer2.java:startHiveServer2(1020)) - Starting HiveServer2
> 2021-03-05T20:44:58,893 INFO [main([])]: SessionState (:()) - Hive Session ID 
> = 1c43f577-8747-4058-b96f-dbf15e388f87
> 2021-03-05T20:44:59,842 INFO [main([])]: session.SessionState (:()) - Created 
> HDFS directory: /tmp/hive/hive/1c43f577-8747-4058-b96f-dbf15e388f87
> 2021-03-05T20:44:59,868 INFO [main([])]: session.SessionState (:()) - Created 
> local directory: /mnt/tmp/hive/1c43f577-8747-4058-b96f-dbf15e388f87
> 2021-03-05T20:44:59,871 INFO [main([])]: session.SessionState (:()) - Created 
> HDFS directory: 
> /tmp/hive/hive/1c43f577-8747-4058-b96f-dbf15e388f87/_tmp_space.db
> 2021-03-05T20:44:59,892 INFO [main([])]: sqlstd.SQLStdHiveAccessController 
> (:()) - Created SQLStdHiveAccessController for session context : 
> HiveAuthzSessionContext [sessionString=1c43f577-8747-4058-b96f-dbf15e388f87, 
> clientType=HIVESERVER2]
> 2021-03-05T20:44:59,896 WARN [main([])]: session.SessionState (:()) - 
> METASTORE_FILTER_HOOK will be ignored, since 
> hive.security.authorization.manager is set to instance of 
> HiveAuthorizerFactory.
> 2021-03-05T20:45:00,660 INFO [main([])]: server.HiveServer2 
> (HiveServer2.java:stop(900)) - Shutting down HiveServer2
> 2021-03-05T20:45:00,661 INFO [main([])]: server.HiveServer2 
> (HiveServer2.java:stopOrDisconnectTezSessions(877)) - Stopping/Disconnecting 
> tez sessions.
> 2021-03-05T20:45:00,661 WARN [main([])]: server.HiveServer2 
> (HiveServer2.java:startHiveServer2(1064)) - Error starting HiveServer2 on 
> attempt 1, will retry in 6ms
> java.lang.VerifyError: Stack map does not match the one at exception handler 
> 77
> Exception Details:
>  Location:
>  
> com/fasterxml/jackson/databind/deser/std/StdDeserializer._parseDate(Lcom/fasterxml/jackson/core/JsonParser;Lcom/fasterxml/jackson/databind/DeserializationContext;)Ljava/util/Date;
>  @77: astore
>  Reason:
>  Type 'com/fasterxml/jackson/core/JsonParseException' (current frame, 
> stack[0]) is not assignable to 
> 'com/fasterxml/jackson/core/exc/StreamReadException' (stack map, stack[0])
>  Current Frame:
>  bci: @69
>  flags: \{ }
>  locals: \{ 'com/fasterxml/jackson/databind/deser/std/StdDeserializer', 
> 'com/fasterxml/jackson/core/JsonParser', 
> 'com/fasterxml/jackson/databind/DeserializationContext' }
>  stack: \{ 'com/fasterxml/jackson/core/JsonParseException' }
>  Stackmap Frame:
>  bci: @77
>  flags: \{ }
>  locals: \{ 'com/fasterxml/jackson/databind/deser/std/StdDeserializer', 
> 'com/fasterxml/jackson/core/JsonParser', 
> 'com/fasterxml/jackson/databind/DeserializationContext' }
>  stack: \{ 'com/fasterxml/jackson/core/exc/StreamReadException' }
>  Bytecode:
>  0x000: 2bb6 0035 aa00   0081  0003
>  0x010:  000b  007a  0081  0081
>  0x020:  0034  0041  0081  0081
>  0x030:  0081  0071 2a2b b600 11b6 0012
>  0x040: 2cb6 006b b02b b600 4742 a700 223a 052c
>  0x050: 2ab4 0002 2bb6 006e 126f 03bd 0004 b600
>  0x060: 70c0 002d 3a06 1906 b600 4c42 bb00 7159
>  0x070: 21b7 0072 b02a 2cb6 0073 c000 71b0 2a2b
>  0x080: 2cb6 0074 b02c 2ab4 0002 2bb6 0025 c000
>  0x090: 71b0
>  Exception Handler Table:
>  bci [69, 74] => handler: 77
>  bci [69, 74] => handler: 77
>  Stackmap Table:
>  same_frame(@56)
>  same_frame(@69)
>  same_locals_1_stack_item_frame(@77,Object[#359])
>  append_frame(@108,Long)
>  chop_frame(@117,1)
>  same_frame(@126)
>  same_frame(@133)
> at 
> com.fasterxml.jackson.databind.deser.std.JdkDeserializers.(JdkDeserializers.java:26)
>  ~[jackson-databind-2.10.0.jar:2.10.0]
>  at 
> com.fasterxml.jackson.databind.deser.BasicDeserializerFactory.findDefaultDeserializer(BasicDeserializerFactory.java:1852)
>  ~[jackson-databind-2.10.0.jar:2.10.0]
>  at 
> com.fasterxml.jackson.databind.deser.BeanDeserializerFactory.findStdDeserializer(BeanDeserializerFactory.java:167)
>  ~[jackson-databind-2.10.0.jar:2.10.0]
>  at 
> 

[jira] [Assigned] (ATLAS-4235) [Atlas: Audits] When business metadata attribute or user defined attribute of an entity is updated, action is appearing as "Entity updated" in v1 api response

2021-04-05 Thread Mandar Ambawane (Jira)


 [ 
https://issues.apache.org/jira/browse/ATLAS-4235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mandar Ambawane reassigned ATLAS-4235:
--

Assignee: Mandar Ambawane

> [Atlas: Audits] When business metadata attribute or user defined attribute of 
> an entity is updated, action is appearing as "Entity updated" in v1 api 
> response
> --
>
> Key: ATLAS-4235
> URL: https://issues.apache.org/jira/browse/ATLAS-4235
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
>
> Case 1:
> When business metadata attribute of an entity is updated, action is appearing 
> as "Entity updated" in v1 api response
> {code:java}
> {u'action': u'ENTITY_UPDATE',
>  u'details': u'Updated business attributes: 
> {"typeName":"eibqk_bm","attributes":{"attrib_1":"111kezor","attrib_2":"222kezor"}}',
>  u'entityId': u'29068c0c-8573-4cf2-bddc-ddefd4d38281',
>  u'eventKey': 
> u'29068c0c-8573-4cf2-bddc-ddefd4d38281:1617296650400:0:1617296650414',
>  u'timestamp': 1617296650400,
>  u'user': u'hrt_qa'} {code}
> As seen in the response, the *details* displays the right data "*Updated 
> business attributes*" but *action* displays "*ENTITY_UPDATE*"
> Case 2:
> When user-defined attribute  of an entity is updated, action is appearing as 
> "Entity updated" in v1 api response
> {code:java}
> {u'action': u'ENTITY_UPDATE',
>  u'details': u'Updated custom attribute: 
> {"typeName":"entity_type_jmgur","guid":"a5770082-21b5-48ad-9540-0b2b7073359d","isIncomplete":false,"provenanceType":0,"version":0,"customAttributes":{"obtsv":"test
>  value 2","mjfid":"test value 3","qlomc":"test value 1"},"proxy":false}',
>  u'entityId': u'a5770082-21b5-48ad-9540-0b2b7073359d',
>  u'eventKey': 
> u'a5770082-21b5-48ad-9540-0b2b7073359d:1617297493442:0:1617297493450',
>  u'timestamp': 1617297493442,
>  u'user': u'hrt_qa'} {code}
> As seen in the response, the *details* displays the right data "*Updated 
> custom attribute*" but *action* displays "*ENTITY_UPDATE*"
> *Minor:*
> Also it will be better if
> *"Updated custom attribute"* is updated as ** 
> *"**Updated custom attributes"* **
> Please not the 's' at the end to keep it consistent 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (ATLAS-4186) Black icons on lineage tab in case of type has spaces

2021-04-05 Thread Nixon Rodrigues (Jira)


 [ 
https://issues.apache.org/jira/browse/ATLAS-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nixon Rodrigues resolved ATLAS-4186.

Fix Version/s: 2.2.0
   3.0.0
   Resolution: Fixed

> Black icons on lineage tab in case of type has spaces 
> --
>
> Key: ATLAS-4186
> URL: https://issues.apache.org/jira/browse/ATLAS-4186
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 2.1.0
>Reporter: Roman Hres
>Priority: Minor
> Fix For: 3.0.0, 2.2.0
>
> Attachments: DataSetEntities.json, ProcessEntity.json, Test Entity 
> Defs.json, black_icons.png
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Currently there is an UI issue which can be found on Apache Atlas lineage UI 
> in case when entity type definition has space in the name. As it is possible 
> to create such a type definition I assume that it is a valid use case. 
> Steps to reproduce:
>  # Create following type defs (example of test definitions: [^Test Entity 
> Defs.json]):
>  ## a new type with space in name. DataSet is used as superType
>  ## a new type with space in name. DataSet is used as superType
>  ## a new type with space in name. Process is used as superType
>  # Create several entities for created types (example: 
> [^DataSetEntities.json])
>  # Create process entity which use one of the created entities as input and 
> the other one as output (example: [^ProcessEntity.json])
> Actual result:
> There are black icons instead inside lineage graph
> !black_icons.png|width=784,height=371!
> Expected result:
> There are normal apache atlas icons 
>  
> *Additional note:*
> During investigation, I found out that this issue related to encoding of the 
> fill attribute in the html. Adding encodeURI before setting fill attribute 
> helped with this issue.
> Details of the fix can be found here: https://github.com/apache/atlas/pull/124
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)