[jira] [Updated] (ATLAS-1406) kafka NotificationException

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1406:

Fix Version/s: (was: 0.8-incubating)

> kafka NotificationException
> ---
>
> Key: ATLAS-1406
> URL: https://issues.apache.org/jira/browse/ATLAS-1406
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: roxia
>Priority: Major
>
> when i create a entities ,the application.log is :
> org.apache.atlas.notification.NotificationException: 
> java.util.concurrent.ExecutionException: 
> org.apache.kafka.common.errors.TimeoutException: Failed to update metadata 
> after 6 ms
> my atlas_application.properties is :
> atlas.notification.embedded=false
> atlas.kafka.data=${sys:atlas.home}/data/kafka
> atlas.kafka.zookeeper.connect=hadoop-s1:2181,hadoop-s2:2181,hadoop-s3:2181
> atlas.kafka.bootstrap.servers=10.224.2.233:9093
> atlas.kafka.zookeeper.session.timeout.ms=600
> atlas.kafka.zookeeper.connection.timeout.ms=300
> atlas.kafka.zookeeper.sync.time.ms=20
> atlas.kafka.auto.commit.interval.ms=1000
> atlas.kafka.auto.offset.reset=smallest
> atlas.kafka.hook.group.id=atlas
> atlas.kafka.auto.commit.enable=false
> atlas.notification.create.topics=true
> atlas.notification.replicas=1
> atlas.notification.topics=ATLAS_HOOK,ATLAS_ENTITIES
> atlas.notification.log.failed.messages=true
> atlas.notification.consumer.retry.interval=500
> atlas.notification.hook.retry.interval=1000



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1381) issue in eclipse when compiling incubator-atlas project

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1381:

Fix Version/s: (was: 0.7-incubating)

> issue in eclipse when compiling incubator-atlas project
> ---
>
> Key: ATLAS-1381
> URL: https://issues.apache.org/jira/browse/ATLAS-1381
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.7-incubating
> Environment: eclipse maven git
>Reporter: carmelo zhang
>Priority: Major
>
> atlas is an open source project ,and I import an maven atlas project with 
> version 0.7 into eclipse,then many issues appears within these 
> projects(includes dependency projects e.g. atlas-notification,atlas-catalog) 
> . 1.pom.xml error
> 2.project(e.g. atlas-typesystem) lack java file(e.g. 
> org.apache.atlas.typesystem.TypesDef) that used by other project
> beacuse of these two types error ,compilng can`t accomplish.
> so I need experts help to resovle these issues so that i can recode atlas 
> project. thank you very much



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1360) Actual UnitTests instead of ITs disguised as UTs

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1360:

Fix Version/s: (was: 0.8-incubating)

> Actual UnitTests instead of ITs disguised as UTs
> 
>
> Key: ATLAS-1360
> URL: https://issues.apache.org/jira/browse/ATLAS-1360
> Project: Atlas
>  Issue Type: Wish
>Affects Versions: 0.8-incubating
>Reporter: Apoorv Naik
>Priority: Major
>
> Currently all Unit test do actual module injection and they act more like 
> integration tests. Actual unit tests should only test a single class or unit 
> and all the dependencies should be mocked.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1413) create Sub-term

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1413:

Fix Version/s: (was: 0.8-incubating)

> create Sub-term
> ---
>
> Key: ATLAS-1413
> URL: https://issues.apache.org/jira/browse/ATLAS-1413
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: roxia
>Priority: Major
>
> when i create Sub-term,i can not query the result i have created at Atlas UI .
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1375) Handle Map datatype of attributes while Create/Edit entities from UI.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1375:

Fix Version/s: (was: 0.8-incubating)

> Handle Map datatype of attributes while Create/Edit entities from UI. 
> --
>
> Key: ATLAS-1375
> URL: https://issues.apache.org/jira/browse/ATLAS-1375
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Kalyani Kashikar
>Priority: Major
>
> Currently Map datatype of attributes are not handled in create 
> entities feature. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1124) Seach tab as landing page after Atlas login

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1124:

Fix Version/s: (was: 0.8-incubating)

> Seach tab as landing page after Atlas login
> ---
>
> Key: ATLAS-1124
> URL: https://issues.apache.org/jira/browse/ATLAS-1124
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Vimal Sharma
>Priority: Major
>
> After login to Atlas, user is redirected to Taxonomy tab. Most often, user 
> logs in to search for Atlas metadata. It makes sense to make search tab the 
> default landing page after login



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1208) DSL query optimisation

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1208:

Fix Version/s: (was: 0.8-incubating)

> DSL query optimisation
> --
>
> Key: ATLAS-1208
> URL: https://issues.apache.org/jira/browse/ATLAS-1208
> Project: Atlas
>  Issue Type: Bug
>Reporter: Sharmadha Sainath
>Priority: Major
>
> DSL queries always have the type. The DSL query is transformed into gremlin 
> of the form: {{g.V().has(type, ).has(name, )}}. This is not 
> efficient as the first has clause returns many vertices. Instead, if we 
> generate the gremlin query as {{g.V().has(name, ).has(type, )}}, 
> the query should execute faster as the first predicate will filter more 
> vertices



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1069) Enable enunciate on java8

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1069:

Fix Version/s: (was: 0.8-incubating)

> Enable enunciate on java8
> -
>
> Key: ATLAS-1069
> URL: https://issues.apache.org/jira/browse/ATLAS-1069
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Priority: Major
>
> Enunciate plugin which generates REST API docs was disabled on java8 as 
> enunciate 1.x was not working on java8. 
> https://github.com/stoicflame/enunciate/wiki/Enunciate-2 available for java8



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1186) Add Glossary Category

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1186:

Fix Version/s: (was: 0.8-incubating)

> Add Glossary Category
> -
>
> Key: ATLAS-1186
> URL: https://issues.apache.org/jira/browse/ATLAS-1186
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 0.8-incubating
>Reporter: David Radley
>Assignee: David Radley
>Priority: Major
>  Labels: features
> Attachments: rb54430(2).patch
>
>
> Add Glossary Category, which would have a name and description and be hung 
> off a taxonomy. The category would contain (composition type) sub categories. 
> Categories can contain terms.  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1016) Support for composite unique attributes for a type.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1016:

Fix Version/s: (was: 0.8-incubating)

> Support for composite unique attributes for a type.
> ---
>
> Key: ATLAS-1016
> URL: https://issues.apache.org/jira/browse/ATLAS-1016
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.8-incubating
>Reporter: Satish Duggana
>Priority: Major
>
> Currently atlas types support attributes containing unique attributes. 
> Enhance this to support composite unique attributes. 
> For example,
> DeviceInfo has attributes like name, model, version and timestamp. Any of 
> these attributes can be configured unique constraint. There should be a way 
> to set composite unique constraint on both model and version fields so that 
> it should not allow storing entities having same set of values for both model 
> and version.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1015) ClassCastException: scala.math.BigInt cannot be cast to java.lang.Long for an attribute with data type as Long.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1015:

Fix Version/s: (was: 0.8-incubating)

> ClassCastException: scala.math.BigInt cannot be cast to java.lang.Long for an 
> attribute with data type as Long.
> ---
>
> Key: ATLAS-1015
> URL: https://issues.apache.org/jira/browse/ATLAS-1015
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Satish Duggana
>Priority: Critical
>
> A type is created with the below info. An entity is created with respective 
> attributes including the Long value for timestamp. But when that stored 
> entity is retrieved, it returns a Referenceable with timestamp attribute 
> containing   scala.math.BigInt type instead of java.lang.Long type 
> {code:java}
> TypesUtil.createClassTypeDef(
> DeviceInfo.NAME_SPACE, null,
> TypesUtil.createUniqueRequiredAttrDef(DeviceInfo.NAME, 
> DataTypes.STRING_TYPE),
> TypesUtil.createUniqueRequiredAttrDef(DeviceInfo.XID, 
> DataTypes.STRING_TYPE),
> attrDef(DeviceInfo.TIMESTAMP, DataTypes.LONG_TYPE),
> attrDef(DeviceInfo.VERSION, DataTypes.STRING_TYPE)
> );
> {code}
> You can look at the test code 
> [here|https://github.com/satishd/incubator-atlas/blob/types-poc/samples/src/test/java/org/apache/atlas/sample/AtlasMetadataServiceTest.java]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1013) DefaultMetadataService#getEntityDefinitionReference(String entityType, String attribute, String value) takes attribute value as a String instead of an Object.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1013:

Fix Version/s: (was: 0.8-incubating)

> DefaultMetadataService#getEntityDefinitionReference(String entityType, String 
> attribute, String value)  takes attribute value as a String instead of an 
> Object.
> ---
>
> Key: ATLAS-1013
> URL: https://issues.apache.org/jira/browse/ATLAS-1013
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Satish Duggana
>Priority: Major
>
> https://github.com/apache/incubator-atlas/blob/master/repository/src/main/java/org/apache/atlas/services/DefaultMetadataService.java#L393
>  takes attribute value as a String instead of an Object. This API should be 
> changed to take Object as attributeValue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-1012) DefaultMetadataService#getEntityDefinition(String guid) returns a deleted instance with SoftDeleteHandler

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-1012:

Fix Version/s: (was: 0.8-incubating)

> DefaultMetadataService#getEntityDefinition(String guid) returns a deleted 
> instance with SoftDeleteHandler
> -
>
> Key: ATLAS-1012
> URL: https://issues.apache.org/jira/browse/ATLAS-1012
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Satish Duggana
>Priority: Major
>
> `DefaultMetadataService#getEntityDefinition(String guid)` returns a deleted 
> instance when atlas.DeleteHandler.impl is configured with 
> `org.apache.atlas.repository.graph.SoftDeleteHandler`
> Main reason seems to be about not checking for a valid state of the instance 
> before it is returned.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-994) MapType doesn't allow null in value

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-994:
---
Fix Version/s: (was: 0.8-incubating)

> MapType doesn't allow null in value
> ---
>
> Key: ATLAS-994
> URL: https://issues.apache.org/jira/browse/ATLAS-994
> Project: Atlas
>  Issue Type: Bug
>Reporter: Vimal Sharma
>Priority: Major
>
> MapType in Atlas TypeSystem doesn't allow null in values.
> MapType uses ImmutableMap which has a check for null in value.
> Following exception is encountered:
> java.lang.NullPointerException: null value in entry: b=null
> at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:235)
> at com.google.common.collect.ImmutableMap.entryOf(ImmutableMap.java:144)
> at com.google.common.collect.ImmutableMap$Builder.put(ImmutableMap.java:182)
> at 
> org.apache.atlas.typesystem.types.DataTypes$MapType.convert(DataTypes.java:588)
> at 
> org.apache.atlas.typesystem.types.DataTypes$MapType.convert(DataTypes.java:552)
> One solution is to use Java HashMap which allows null values.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-960) UI: Associating tags/terms is not allowed for deleted entities.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-960:
---
Fix Version/s: (was: 0.7-incubating)

> UI: Associating tags/terms is not allowed for deleted entities.
> ---
>
> Key: ATLAS-960
> URL: https://issues.apache.org/jira/browse/ATLAS-960
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Ayub Pathan
>Priority: Major
>
> Associating tag/terms to deleted entities is not allowed through UI, which it 
> should as per ATLAS-670.
> snapshot: https://monosnap.com/file/9QGJh0EwdPnEZyvCi7ohoF6znOu6ES



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-999) Build and install with jdk8

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-999:
---
Fix Version/s: (was: 0.8-incubating)

> Build and install with jdk8
> ---
>
> Key: ATLAS-999
> URL: https://issues.apache.org/jira/browse/ATLAS-999
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Priority: Major
>
> During the 0.7 release voting, some reported that the build fails with jdk 
> 1.8. Creating this to track it



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-3279) Performance regression after recent updates to disable full-text index

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-3279:

Fix Version/s: (was: 2.1.0)

> Performance regression after recent updates to disable full-text index
> --
>
> Key: ATLAS-3279
> URL: https://issues.apache.org/jira/browse/ATLAS-3279
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: ATLAS-3279.patch
>
>
> With recent search enhancements in ATLAS-3100 and ATLAS-3246, full-text index 
> is no more needed; and ATLAS-3262 disabled populating full-text index. After 
> this change, Atlas server takes a longer time to send entity notifications; 
> the cache used by the notification module was earlier populated while 
> computing full-text index string; now, this is done by 
> AtlasInstanceConverter, which retrieves entity-with-extended-info (to be used 
> only to send V1 style notifications), which resulted in performance 
> regression in processing notifications.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-3280) Hive Hook creates lineage incorrectly when alter external table or view

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-3280:

Fix Version/s: (was: 1.1.0)
   (was: 1.0.0)

> Hive Hook creates lineage incorrectly when alter external table or view
> ---
>
> Key: ATLAS-3280
> URL: https://issues.apache.org/jira/browse/ATLAS-3280
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0, 1.1.0
>Reporter: Jiaqi Shan
>Priority: Major
> Attachments: 0001-ATLAS-3280.patch, alter_lineage.jpg, lineage.png
>
>
> When altering an external table or a view, Hive Hook will create lineage 
> incorrectly as follows 
>  !alter_lineage.jpg! 
>  
> So we propose to add a parameter {{ignoreProcessEntity}} to 
> {{CreateTable.getEntites}}. When set to true, Hive Hook won’t create lineage 
> to external table or view. We also add the parameter to {{AlterTable}} 
> accordingly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-3281) Allow excluding lineage related to deleted entities

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-3281:

Fix Version/s: (was: 1.1.0)

> Allow excluding lineage related to deleted entities
> ---
>
> Key: ATLAS-3281
> URL: https://issues.apache.org/jira/browse/ATLAS-3281
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 1.1.0
>Reporter: Jiaqi Shan
>Priority: Major
> Attachments: ATLAS-3281.patch, screenshot-1.png, screenshot-2.png
>
>
> If a hive_table was deleted, {{EntityLineageService.getAtlasLineageInfo}} 
> will still return hive_process related to the table. But in some scenarios, 
> we don't want to display hive_process related to deleted entities in web UI. 
> So we propose to add a parameter {{excludeDeletedEndpoints}} to 
> {{getLineageQuery.getLineageQuery}}. When set to true, the function will 
> exclude lineages related to deleted entities. We also add the parameter to 
> {{AtlasLineageService}}, 
> {{AtlasGremlinQueryProvider}},{{AtlasGremlin3QueryProvider}} and 
> {{LineageREST}} accordingly.
> When {{excludeDeletedEndpoints}} is set to false, the lineage is displayed as 
> follow:
>  !screenshot-1.png!
> When {{excludeDeletedEndpoints}} is set to true, the lineage is displayed as 
> follow:
>  !screenshot-2.png!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2753) Able to associate/update tags for DELETED entities through REST APIs

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2753:

Fix Version/s: (was: 1.2.0)

[~sarath.ku...@gmail.com] - can you please review the branch(es) this fix has 
landed in and update fixVersion field?

> Able to associate/update tags for DELETED entities through REST APIs
> 
>
> Key: ATLAS-2753
> URL: https://issues.apache.org/jira/browse/ATLAS-2753
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.1.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
>
> Requests to associate classification / edit classification on a DELETED 
> entity through REST results in success.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2800) UI - In Advance search an additional API request is fire when any column is drag and droped

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2800:

Fix Version/s: (was: 1.2.0)
   (was: 0.8.2)
   (was: trunk)

> UI - In Advance search an additional API request is fire when any column is 
> drag and droped
> ---
>
> Key: ATLAS-2800
> URL: https://issues.apache.org/jira/browse/ATLAS-2800
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8.1, 1.0.0, 2.0.0
>Reporter: Tejas Rawool
>Assignee: Keval Bhatt
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2841) Regression, Tag Propagation : When a table is moved from database1 to database2 , tag propagated from db1 still propagated to table.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2841:

Fix Version/s: (was: 1.2.0)

> Regression, Tag Propagation : When a table is moved from database1 to 
> database2 , tag propagated from db1 still propagated to table.
> 
>
> Key: ATLAS-2841
> URL: https://issues.apache.org/jira/browse/ATLAS-2841
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Attachments: ATLAS-2841.1.patch
>
>
> 1. Create databases db1,db2
> 2. Create table1 in db1.
> 3. Modify relationship between db1 and table1 such that tags associated to 
> db1 are propagated to table1.
> 4. Add tag1 to db1.
> 5. Add tag2 to db2.
> 6. Rename table from db1.table1 to db2.table1.
> 7. Earlier behavior is , tag1 propagated from db1 is removed from table and 
> tag2 is propagated to table1 from db2. But currently , both tag1 and tag2 are 
> propagated to table1.
> In relationship response between db1 and table, status is marked DELETED.
> tag1 is not added to propagatedClassifications array in the response of the 
> relationship ,but still tag1 is propagated to table.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2851) Retrieving entity with SET attribute contains duplicate entries if attribute type updated from LIST to SET

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2851:

Fix Version/s: (was: 1.2.0)

[~sarath.ku...@gmail.com] - can you please review the branch(es) this fix has 
landed in and update fixVersion field?

> Retrieving entity with SET attribute contains duplicate entries if attribute 
> type updated from LIST to SET
> --
>
> Key: ATLAS-2851
> URL: https://issues.apache.org/jira/browse/ATLAS-2851
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.1.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Attachments: ATLAS-2851.1.patch
>
>
> Retrieving entity with SET attribute type contains duplicate entries if 
> attribute type updated from LIST to SET



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2859) Basic search loads atlas internal type entities when searched with _NOT_CLASSIFIED classification paramter

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2859:

Fix Version/s: (was: 1.2.0)

> Basic search loads atlas internal type entities when searched with 
> _NOT_CLASSIFIED classification paramter
> --
>
> Key: ATLAS-2859
> URL: https://issues.apache.org/jira/browse/ATLAS-2859
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 1.0.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: trunk
>
> Attachments: 
> 0001-ATLAS-2859-Fix-to-not-loads-atlas-internal-type-enti.patch, 
> _NOT_CLASSIFIED.png
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2880) Update classification-propagation documentation for deleted entities

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2880:

Fix Version/s: (was: 1.2.0)

> Update classification-propagation documentation for deleted entities
> 
>
> Key: ATLAS-2880
> URL: https://issues.apache.org/jira/browse/ATLAS-2880
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Nixon Rodrigues
>Assignee: Sarath Subramanian
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2896) Enhance Atlas Client V2 java api to add glossary terms

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2896:

Fix Version/s: (was: 1.2.0)

> Enhance Atlas Client V2 java api to add glossary terms
> --
>
> Key: ATLAS-2896
> URL: https://issues.apache.org/jira/browse/ATLAS-2896
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Reporter: Ayush Nigam
>Assignee: Ayush Nigam
>Priority: Major
>  Labels: patch
>
> Enhance V2 Java client to add glossary terms,categories



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2893) Atlas Column Lineage of Hive Hook to support the hive old version (before hive version 1.2.1 after the patch for HIVE-13112)

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2893:

Fix Version/s: (was: 1.2.0)

> Atlas Column Lineage of Hive Hook to support the hive old version (before 
> hive version 1.2.1 after the patch for HIVE-13112)
> 
>
> Key: ATLAS-2893
> URL: https://issues.apache.org/jira/browse/ATLAS-2893
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-intg
>Affects Versions: 1.0.0
>Reporter: aflyary
>Priority: Major
> Attachments: ATLAS-2893.001.patch
>
>
>         Right now atlas hook for apache hive of column lineage is limited, 
> only "Column level lineage works with Hive version 1.2.1 after the patch for 
> HIVE-13112 is applied to Hive source" could support the hive column lineage.
>         In some product env, hive version still very old, but we should also 
> support the hive column lineage.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2928) Namespace entity relationship-attribute names to avoid conflict with entity attributes

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2928:

Fix Version/s: (was: 1.2.0)

> Namespace entity relationship-attribute names to avoid conflict with entity 
> attributes
> --
>
> Key: ATLAS-2928
> URL: https://issues.apache.org/jira/browse/ATLAS-2928
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0, 1.1.0
>Reporter: Madhan Neethiraj
>Assignee: Le Ma
>Priority: Critical
> Fix For: trunk
>
>
> Apache Atlas 1.0 introduced relationships as first-class types. A 
> relationship effectively 'injects' an attribute on the entities at each end. 
> For example, assignment of a glossary term to an entity is captured by 
> relationship AtlasGlossarySemanticAssignment (in 
> -Area0/0011-glossary_model.json). This relationship adds following 
> attributes:
> - Referceable.meanings: set
> - AtlasGlossaryTerm.assignedEntities: set
> This works fine as long as the entity-types involved in the relationship, or 
> their sub-types don't have an attribute with the same name as the attribute 
> injected by the relationships. Once such instance was reported by [~bolke], 
> about relationship attribute DataSet.schema introduced by 
> avro_schema_associatedEntities - which conflicts with spark_table.schema, 
> since spark_table type is a sub-type of DataSet.
> Such name conflicts can be avoided by prefixing relationship-attribute names 
> with a prefix like "r:".



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2932) Update DSL to use Java Traversal API

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2932:

Fix Version/s: (was: 1.2.0)

> Update DSL to use Java Traversal API
> 
>
> Key: ATLAS-2932
> URL: https://issues.apache.org/jira/browse/ATLAS-2932
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0, trunk
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Attachments: 
> 0002-ATLAS-2932-Update-DSL-to-use-Tinkerpop-Java-APIs-ins.patch
>
>
> Change DSL code to use Java Tinkerpop Traversals instead of 
> GremlinScriptEngine



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ATLAS-3028) UI - If a column is deleted then user needs to stop and start the server to see the change in Statistics count

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj resolved ATLAS-3028.
-
   Resolution: Duplicate
Fix Version/s: (was: 1.2.0)
   (was: trunk)

> UI - If a column is deleted then user needs to stop and start the server to 
> see the change in Statistics count
> --
>
> Key: ATLAS-3028
> URL: https://issues.apache.org/jira/browse/ATLAS-3028
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.2.0, 2.0.0
>Reporter: Tejas Rawool
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-3255) UI: IE 10 - Page Limit button gets displaced after clicking it.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-3255:

Fix Version/s: (was: 1.2.0)
   1.3.0

> UI: IE 10 - Page Limit button gets displaced after clicking it.
> ---
>
> Key: ATLAS-3255
> URL: https://issues.apache.org/jira/browse/ATLAS-3255
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Rahul Kurup
>Assignee: Keval Bhatt
>Priority: Minor
> Fix For: 2.1.0, 3.0.0, 1.3.0
>
>
> In IE 10, the Page Limit button position gets displaced and moves to the 
> middle of the search results page after clicking it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ATLAS-3299) Release Atlas 0.8.4

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj resolved ATLAS-3299.
-
Resolution: Done

> Release Atlas 0.8.4
> ---
>
> Key: ATLAS-3299
> URL: https://issues.apache.org/jira/browse/ATLAS-3299
> Project: Atlas
>  Issue Type: Task
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 0.8.4
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2437) When using org.apache.atlas:falcon-bridge:0.8.2, conflicting classes are introduced from two different JARs:

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2437:

Fix Version/s: (was: 0.8.4)

> When using org.apache.atlas:falcon-bridge:0.8.2, conflicting classes are 
> introduced from two different JARs: 
> ,
>  which caused NoSuchMethodError
> --
>
> Key: ATLAS-2437
> URL: https://issues.apache.org/jira/browse/ATLAS-2437
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8.2
>Reporter: PandaMonkey
>Priority: Major
>
> When our project using org.apache.atlas:falcon-bridge:0.8.2, conflicting 
> classes are introduced from two different JARs: 
> ,
>  which leaded to our project throw *NoSuchMethodException.* Conflicting 
> classes mean that the classes with same name but have different 
> implementations. Then the JVM only load the classes present first on the 
> classpath and shadow the other duplicate ones. This is the main reason why 
> our program crashed. By analyzing the source code, the we found the 
> conflicting details as follows. To avoid the downstream projects encounter 
> the same problem, please notice this issue.
> 1. Risk for 
> jar-pair:<*javax.xml.stream:stax-api:1.0-2*:><*stax:stax-api:1.0.1*:>
>  Methods that only exist in javax.xml.stream:stax-api:1.0-2:: 
> [neu.lab:findbug:0.0.1-SNAPSHOT:->org.apache.atlas:falcon-bridge:0.8.2:->org.apache.atlas:hive-bridge:0.8.2:->org.apache.hadoop:hadoop-client:2.7.1:->org.apache.hadoop:hadoop-mapreduce-client-core:2.7.1:->org.apache.hadoop:hadoop-yarn-common:2.7.1:->javax.xml.bind:jaxb-api:2.2.2:->javax.xml.stream:stax-api:1.0-2:]
>  {color:#ff} javax.xml.stream.XMLInputFactory 
> newInstance(java.lang.String,java.lang.ClassLoader)>{color}
>  {color:#ff} methods that only exist in stax:stax-api:1.0.1:: 
> [neu.lab:findbug:0.0.1-SNAPSHOT:->org.apache.atlas:falcon-bridge:0.8.2:->org.apache.atlas:atlas-typesystem:0.8.2:->org.codehaus.jettison:jettison:1.3.7:->stax:stax-api:1.0.1:]{color}
>  {color:#ff}  class$(java.lang.String)>{color}
>  {color:#ff}  javax.xml.stream.XMLOutputFactory 
> newInstance(java.lang.String,java.lang.ClassLoader)>{color}
> 2. Risk for jar-pair:<*stax:stax-api:1.0.1*:><*xml-apis:xml-apis:1.3.04*:>
>  Methods that only exist in xml-apis:xml-apis:1.3.04:: 
> [neu.lab:findbug:0.0.1-SNAPSHOT:->org.apache.atlas:falcon-bridge:0.8.2:->org.apache.atlas:hive-bridge:0.8.2:->org.apache.hadoop:hadoop-client:2.7.1:->org.apache.hadoop:hadoop-hdfs:2.7.1:->xerces:xercesImpl:2.9.1:->xml-apis:xml-apis:1.3.04:]
>  {color:#ff} readObject(java.io.ObjectInputStream)>{color}
>  {color:#ff} ()>{color}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ATLAS-2842) Entities with different guids does not get referenced in array with SET cardinality

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj resolved ATLAS-2842.
-
Resolution: Fixed

> Entities with different guids does not get referenced in array with SET 
> cardinality
> ---
>
> Key: ATLAS-2842
> URL: https://issues.apache.org/jira/browse/ATLAS-2842
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Affects Versions: 0.8.2
>Reporter: Daniel Kelencz
>Priority: Major
> Fix For: 0.8.4
>
> Attachments: 0001-fix-faulty-AtlasObjectId-equals.patch, 
> apache_repro_simple_set.json, apache_repro_simple_set_data.json, 
> simple_set.json, simple_set_data.json
>
>
> With type definitions [^apache_repro_simple_set.json] and 
> [^apache_repro_simple_set_data.json]. Using the REST API call 
> /api/atlas/v2/entity/bulk with [^simple_set_data.json]  [^simple_set.json] 
> only the first simple_set_data gets referenced in the set entity instead of 3 
> references.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2850) Atlas Sqoop hook throws NPE

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2850:

Fix Version/s: (was: 0.8.4)

> Atlas Sqoop hook throws NPE
> ---
>
> Key: ATLAS-2850
> URL: https://issues.apache.org/jira/browse/ATLAS-2850
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Affects Versions: 0.8.2
>Reporter: Daniel Kelencz
>Priority: Major
>
> When trying to import tables into hive with Atlas hooks configured, the 
> following throws NPE:
> {noformat}
> ./sqoop import-all-tables --connect jdbc:mysql://sql.server/mydb --username 
> sqooptest --password sqooptest -m 1 --warehouse-dir /user/sqoop --hive-import 
> --verbose{noformat}
> the output contains:
> {noformat}
> 18/08/30 06:55:51 WARN mapreduce.PublishJobData: Unable to publish import 
> data to publisher SqoopHook.publish() failed.
> org.apache.atlas.hook.AtlasHookException: SqoopHook.publish() failed.
>         at org.apache.atlas.sqoop.hook.SqoopHook.publish(SqoopHook.java:96)
>         at org.apache.atlas.sqoop.hook.SqoopHook.publish(SqoopHook.java:51)
>         at 
> org.apache.sqoop.mapreduce.PublishJobData.publishJobData(PublishJobData.java:52)
>         at 
> org.apache.sqoop.mapreduce.ImportJobBase.runImport(ImportJobBase.java:284)
>         at 
> org.apache.sqoop.manager.SqlManager.importTable(SqlManager.java:692)
>         at 
> org.apache.sqoop.manager.MySQLManager.importTable(MySQLManager.java:127)
>         at org.apache.sqoop.tool.ImportTool.importTable(ImportTool.java:507)
>         at 
> org.apache.sqoop.tool.ImportAllTablesTool.run(ImportAllTablesTool.java:111)
>         at org.apache.sqoop.Sqoop.run(Sqoop.java:147)
>         at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
>         at org.apache.sqoop.Sqoop.runSqoop(Sqoop.java:183)
>         at org.apache.sqoop.Sqoop.runTool(Sqoop.java:225)
>         at org.apache.sqoop.Sqoop.runTool(Sqoop.java:234)
>         at org.apache.sqoop.Sqoop.main(Sqoop.java:243)
> Caused by: java.lang.NullPointerException
>         at 
> org.apache.atlas.hive.bridge.HiveMetaStoreBridge.getTableQualifiedName(HiveMetaStoreBridge.java:747)
>         at 
> org.apache.atlas.hive.bridge.HiveMetaStoreBridge.getTableQualifiedName(HiveMetaStoreBridge.java:766)
>         at 
> org.apache.atlas.sqoop.hook.SqoopHook.createHiveTableInstance(SqoopHook.java:113)
>         at org.apache.atlas.sqoop.hook.SqoopHook.publish(SqoopHook.java:83)
>         ... 13 more{noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2855) StructInsance.setNull does not handle enum types

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2855:

Fix Version/s: (was: 0.8.4)

> StructInsance.setNull does not handle enum types
> 
>
> Key: ATLAS-2855
> URL: https://issues.apache.org/jira/browse/ATLAS-2855
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8.2
>Reporter: Daniel Kelencz
>Priority: Major
>
> When trying to:
> POST /api/atlas/v2/entity/bulk
> {noformat}
> {
>   "entities": [
> {
>   "typeName": "hive_db",
>   "attributes": {
> "qualifiedName": "findme",
> "name": "findme",
> "clusterName": 
>   },
>   "status": "ACTIVE",
>   "createdBy": "admin",
>   "updatedBy": "admin",
>   "createTime": 1489585008165,
>   "updateTime": 1489585008801,
>   "version": 0,
>   "classifications": [],
>   "superTypes": []
> }
>   ],
>   "referredEntities": {}
> }{noformat}
> The following occurs in the logs:
> {noformat}
> Caused by: org.apache.atlas.AtlasException: Unknown datatype 
> {name=hive_principal_type, description=hive_principal_type}
> at 
> org.apache.atlas.typesystem.persistence.StructInstance.setNull(StructInstance.java:274)
> 
> at 
> org.apache.atlas.repository.audit.EntityAuditListener.clearAttributeValues(EntityAuditListener.java:175)
> 
> at 
> org.apache.atlas.repository.audit.EntityAuditListener.getAuditEventDetail(EntityAuditListener.java:158)
>   
> at 
> org.apache.atlas.repository.audit.EntityAuditListener.createEvent(EntityAuditListener.java:133)
> 
> at 
> org.apache.atlas.repository.audit.EntityAuditListener.onEntitiesAdded(EntityAuditListener.java:63)
> 
> at 
> org.apache.atlas.repository.store.graph.v1.AtlasEntityChangeNotifier.notifyListeners(AtlasEntityChangeNotifier.java:164)
> ... 101 more   {noformat}
> This is because the hive_db contains hive_principal_type which is an enum, 
> and StructInstance.setNull does not handle enum types.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2944) Import: fail fast if required meta files are not found in imported zip

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2944:

Fix Version/s: (was: 0.8.4)

> Import: fail fast if required meta files are not found in imported zip
> --
>
> Key: ATLAS-2944
> URL: https://issues.apache.org/jira/browse/ATLAS-2944
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.8.2, 0.8.3, trunk
>Reporter: Daniel Kelencz
>Priority: Major
> Fix For: trunk
>
>
> Importing a zip file without any of the currently required meta files ( 
> namely ATLAS_EXPORT_INFO_NAME("atlas-export-info"),
> ATLAS_EXPORT_ORDER_NAME("atlas-export-order"),
> ATLAS_TYPESDEF_NAME("atlas-typesdef"))
> will fail the import during json deserialization. It would greatly help 
> future debugging efforts if the lack of any of these files is detected as 
> soon as possible and a reasonable exception would be thrown.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-3049) Avoid repeated calls to property-key encoding while reading vertex properties

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-3049:

Fix Version/s: (was: 0.8.4)

> Avoid repeated calls to property-key encoding while reading vertex properties
> -
>
> Key: ATLAS-3049
> URL: https://issues.apache.org/jira/browse/ATLAS-3049
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.8.3
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Attachments: ATLAS-3049.patch
>
>
> While accessing vertex property values, the property name is checked for 
> presence of special characters and when found they are escaped appropriately. 
> By caching the escaped property names, repeated calls to check/escape can be 
> avoided - which can result in improved performance.
>  
> ATLAS-2836 fixed such repeated calls to check/escape - but for V2 API path; 
> similar fixes are needed for V1 API paths, which are used to create 
> notifications and audits. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-3119) Dependency Conflict: duplicate classes "org.apache.log4j.Logger" in different JARs, have different implementations

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-3119:

Fix Version/s: (was: 0.8.4)

> Dependency Conflict: duplicate classes "org.apache.log4j.Logger" in different 
> JARs, have different implementations
> --
>
> Key: ATLAS-3119
> URL: https://issues.apache.org/jira/browse/ATLAS-3119
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8.3
>Reporter: Hello CoCooo
>Priority: Major
> Attachments: t.png, y.png
>
>
> Hi, in *incubator-atlas-release-0.8.3* (*\addons\storm-bridge-shim* module), 
> duplicate classes with the same fully-qualified name 
> _*org.apache.log4j.Logger*_ are included in two different libraries, i.e., 
> *org.slf4j:log4j-over-slf4j:1.6.6* and *log4j:log4j:1.2.17*.
> According to _"first declaration wins"_ class loading strategy, only this 
> class in *org.slf4j:log4j-over-slf4j:1.6.6* can be loaded, and that in 
> *log4j:log4j:1.2.17* will be shadowed.
> By further analyzing, your project expects to invoke method 
> ** in 
> *log4j:log4j:1.2.17*. As it has been shadowed, so that this method defined in 
> *org.slf4j:log4j-over-slf4j:1.6.**_6_* is actually forced to be referenced 
> via the following invocation path:
> {code:java}
> // code placeholder
> ()> 
> D:\testcase\TestProject\incubator-atlas-release-0.8-rc1\addons\storm-bridge-shim\target\classes
>  
> D:\cEnvironment\repository\org\slf4j\slf4j-api\1.7.21\slf4j-api-1.7.21.jar
>  
> D:\cEnvironment\repository\org\slf4j\slf4j-api\1.7.21\slf4j-api-1.7.21.jar
>  getLogger(java.lang.String)> 
> D:\cEnvironment\repository\org\slf4j\slf4j-log4j12\1.7.21\slf4j-log4j12-1.7.21.jar
> (org.apache.log4j.Logger)> 
> D:\cEnvironment\repository\org\slf4j\slf4j-log4j12\1.7.21\slf4j-log4j12-1.7.21.jar
>  
> D:\cEnvironment\repository\org\slf4j\slf4j-log4j12\1.7.21\slf4j-log4j12-1.7.21.jar
> 
> {code}
> Although both of these two conflicting classes contain the referenced methods 
> (with the same signature), they have different implementations. This issue 
> will not lead to runtime crashes, but it can introduce inconsistent semantic 
> hehavior by changing the control flows and data flows.
> *_Workaround solution:_*
>  An easy way to workaround the problem is *_reversing the declaration order_* 
> of these two libraries i n pom file.
>  Then, according to *_"first declaration wins"_* class loading strategy, 
> class *org.apache.log4j.Logger* in *log4j:log4j:1.2.17* can be loaded (the 
> version that *incubator-atlas* expects to reference by static analysis).
>  This fix will not affect other libraries or class, except the above 
> duplicate class.
>  
> *Dependency tree--*
> [INFO] — maven-dependency-plugin:2.10:tree (default-cli) @ storm-bridge-shim —
> [INFO] org.apache.atlas:storm-bridge-shim:jar:0.8-incubating
> [INFO] +- org.apache.atlas:atlas-plugin-classloader:jar:0.8-incubating:compile
> [INFO] +- org.apache.storm:storm-core:jar:1.0.0:compile
> [INFO] |  +- com.esotericsoftware:kryo:jar:3.0.3:compile
> [INFO] |  |  +- com.esotericsoftware:reflectasm:jar:1.10.1:compile
> [INFO] |  |  |  - org.ow2.asm:asm:jar:5.0.3:compile
> [INFO] |  |  +- com.esotericsoftware:minlog:jar:1.3.0:compile
> [INFO] |  |  - org.objenesis:objenesis:jar:2.1:compile
> [INFO] |  +- org.clojure:clojure:jar:1.7.0:compile
> [INFO] |  +- com.lmax:disruptor:jar:3.3.2:compile
> [INFO] |  +- org.apache.logging.log4j:log4j-api:jar:2.1:compile
> [INFO] |  +- org.apache.logging.log4j:log4j-core:jar:2.1:compile
> [INFO] |  +- org.apache.logging.log4j:log4j-slf4j-impl:jar:2.1:compile
> [INFO] |  +- _*org.slf4j:log4j-over-slf4j:jar:1.6.6:compile*_
> [INFO] |  - javax.servlet:servlet-api:jar:2.5:compile
> [INFO] +- org.slf4j:slf4j-api:jar:1.7.21:compile
> [INFO] +- org.slf4j:slf4j-log4j12:jar:1.7.21:compile
> [INFO] |  - _*log4j:log4j:jar:1.2.17:compile*_
> [INFO] - org.slf4j:jul-to-slf4j:jar:1.7.21:compile
>  
> Thank you very much.
>  Best,
>  Coco



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-3255) UI: IE 10 - Page Limit button gets displaced after clicking it.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-3255:

Fix Version/s: (was: 0.8.4)

> UI: IE 10 - Page Limit button gets displaced after clicking it.
> ---
>
> Key: ATLAS-3255
> URL: https://issues.apache.org/jira/browse/ATLAS-3255
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Rahul Kurup
>Assignee: Keval Bhatt
>Priority: Minor
> Fix For: 1.2.0, 2.1.0, 3.0.0
>
>
> In IE 10, the Page Limit button position gets displaced and moves to the 
> middle of the search results page after clicking it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ATLAS-3297) Cache created/updated entities in request context for use in entity-change listeners

[Madhan Neethiraj (JIRA)]

Madhan Neethiraj created ATLAS-3297:
---

 Summary: Cache created/updated entities in request context for use 
in entity-change listeners
 Key: ATLAS-3297
 URL: https://issues.apache.org/jira/browse/ATLAS-3297
 Project: Atlas
  Issue Type: Improvement
  Components:  atlas-core
Affects Versions: 2.0.0
Reporter: Madhan Neethiraj
Assignee: Madhan Neethiraj


After performing entity create/update operations, Atlas calls change-listeners 
who handle tasks like create audit logs and send notifications. Change 
listeners retrieve entities from the store, which could be avoided by caching 
the entities during create/update phase. This can result in significant 
improvements in entity create/update operations.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-3277) Add default atlas conf path in the import-* scripts

[Madhan Neethiraj (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16866966#comment-16866966
 ] 

Madhan Neethiraj commented on ATLAS-3277:
-

+1 for the patch. Thanks [~vishal.suvagia]!

> Add default atlas conf path in the import-* scripts
> ---
>
> Key: ATLAS-3277
> URL: https://issues.apache.org/jira/browse/ATLAS-3277
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 2.0.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
>Priority: Minor
> Attachments: ATLAS-3277.01.patch, ATLAS-3277.patch
>
>
> Update Atlas import-* scripts to add default atlas conf path, in case if 
> atlas-application.properties is not available in the hook component-conf path



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ATLAS-3279) Performance regression after recent updates to disable full-text index

[Madhan Neethiraj (JIRA)]

Madhan Neethiraj created ATLAS-3279:
---

 Summary: Performance regression after recent updates to disable 
full-text index
 Key: ATLAS-3279
 URL: https://issues.apache.org/jira/browse/ATLAS-3279
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 2.0.0
Reporter: Madhan Neethiraj
Assignee: Madhan Neethiraj


With recent search enhancements in ATLAS-3100 and ATLAS-3246, full-text index 
is no more needed; and ATLAS-3262 disabled populating full-text index. After 
this change, Atlas server takes a longer time to send entity notifications; the 
cache used by the notification module was earlier populated while computing 
full-text index string; now, this is done by AtlasInstanceConverter, which 
retrieves entity-with-extended-info (to be used only to send V1 style 
notifications), which resulted in performance regression in processing 
notifications.

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ATLAS-3246) Improve the free text search functionality to not depend on solrconfig.xml and schema.xml files.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj resolved ATLAS-3246.
-
   Resolution: Fixed
Fix Version/s: 3.0.0

> Improve the free text search functionality to not depend on solrconfig.xml 
> and schema.xml files.
> 
>
> Key: ATLAS-3246
> URL: https://issues.apache.org/jira/browse/ATLAS-3246
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Sridhar
>Assignee: Sridhar
>Priority: Major
> Fix For: 3.0.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-3254) Atlas entity with large array of refs causes performance issues for lineage

[Madhan Neethiraj (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16859241#comment-16859241
 ] 

Madhan Neethiraj commented on ATLAS-3254:
-

[~arempter] - which version of Atlas do you see this issue in? Atlas 1.1.0 and 
2.0.0 include a fix to address slowness issue in UI - ATLAS-2815.

If you are already on one of this version (or a later), can you please share 
scripts or Kafka messages to create AWS entities? It will help very much to 
investigate the issue.

> Atlas entity with large array of refs causes performance issues for lineage
> ---
>
> Key: ATLAS-3254
> URL: https://issues.apache.org/jira/browse/ATLAS-3254
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Affects Versions: 1.0.0, 2.0.0
>Reporter: Adam Rempter
>Priority: Major
>  Labels: performance
>
> We use “aws_s3_pseudo_dir” type from 3020-aws_s3_typedefs.json model.
> It has following property: 
> "name":    "s3Objects",
> "typeName":    "array"
>  
> Now in AWS buckets you can have thousands of objects. This causes that 
> s3Objects array grows quite quickly, causing aws_s3_pseudo_dir entity Json to 
> rich easly few MBs.
>  
> Then we start seeing problems like:
>  * UI is dying on displaying entity properties or lineage
>  * Error in logs: audit record too long: entityType=aws_s3_pseudo_dir, 
> guid=24398271-6ba0-4db5-adfa-38e432dc55ce, size=1053931; maxSize=1048576. 
> entity attribute values not stored in audit (EntityAuditListenerV2:234)
>  * Some errors with write to HBase (java.lang.IllegalArgumentException: 
> KeyValue size too large, as workaround we set hbase.client.keyvalue.maxsize 
> param to 0)
>  * kafka consumer errors (we can of course set some parameters on consumer, 
> but I think it is just workaround)
> …
> Exception in NotificationHookConsumer (NotificationHookConsumer:332)
> org.apache.kafka.clients.consumer.CommitFailedException: Commit cannot be 
> completed since the group has already rebalanced and assigned the partitions 
> to another member. This means that the time between subsequen
> t calls to poll() was longer than the configured max.poll.interval.ms, which 
> typically implies that the poll loop is spending too much time message 
> processing. You can address this either by increasing the sessio
> n timeout or by reducing the maximum size of batches returned in poll() with 
> max.poll.records.
> …
> Specifying pseudo_dir is required for s3objects:
> name": "pseudoDirectory",
> "typeName": "aws_s3_pseudo_dir",
> "cardinality": "SINGLE",
> "isIndexable": false,
> *"isOptional": false,*
> "isUnique": false,
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-3219) Implemented new serviceType Rest API

[Madhan Neethiraj (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16859230#comment-16859230
 ] 

Madhan Neethiraj commented on ATLAS-3219:
-

[~Zep] - following method can be used to retrieve typedefs for a given 
serviceType, by specifying it in SearchFilter. If further API changes are 
needed, can you please add details?

{code}
public class AtlasClientV2 .. {
  ...
  public AtlasTypesDef getAllTypeDefs(SearchFilter searchFilter) {
  ...
}
{code}

> Implemented new serviceType Rest API
> 
>
> Key: ATLAS-3219
> URL: https://issues.apache.org/jira/browse/ATLAS-3219
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-intg
>Affects Versions: 2.0.0
> Environment: all
>Reporter: Diego Marino Monetti
>Priority: Major
> Fix For: trunk
>
>  Time Spent: 3h
>  Remaining Estimate: 0h
>
> This pull request supersedes the pull request ATLAS-3180.
> The new basic attribute serviceType, introduced by Atlas Team, has no use if 
> it is not searchable ina any way. This pull request solves this problem by 
> adding the following REST APIs.
> GET / typedef / servicetype / \{servicetype}
> GET / typedefs / headers? Servicetype = \{serviceType}
> GET / typedefs? Servicetype = \{servicetype}
> GET / enumdef / servicetype / \{servicetype}
> GET / entitydef / servicetype / \{servicetype}
> GET / structdef / servicetype / \{servicetype}
> GET / relationshipdef / servicetype / \{servicetype}
> DELETE / typedef / servicetype / \{servicetype}
> The APIs were tested on ATLAS 2.0 and on the new SNAPSHOT 3.0



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ATLAS-3271) Investigate and fix test failures in atlas-distro module

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj resolved ATLAS-3271.
-
   Resolution: Fixed
Fix Version/s: 3.0.0

This test failure was caused by recent changes in ATLAS-3246.

> Investigate and fix test failures in atlas-distro module
> 
>
> Key: ATLAS-3271
> URL: https://issues.apache.org/jira/browse/ATLAS-3271
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: ATLAS-3271.001.patch
>
>
> Fix failing test:
> {code}
> ==
> FAIL: test_main_embedded (TestMetadata.TestMetadata)
> --
> Traceback (most recent call last):
>   File 
> "/home/jenkins/jenkins-slave/workspace/Atlas-master-AllTests/distro/src/test/mock/mock.py",
>  line 1199, in patched
> return func(*args, **keywargs)
>   File 
> "/home/jenkins/jenkins-slave/workspace/Atlas-master-AllTests/distro/src/test/python/scripts/TestMetadata.py",
>  line 121, in test_main_embedded
> runProcess_mock.assert_has_calls(calls)
>   File 
> "/home/jenkins/jenkins-slave/workspace/Atlas-master-AllTests/distro/src/test/mock/mock.py",
>  line 861, in assert_has_calls
> 'Actual: %r' % (calls, self.mock_calls)
> AssertionError: Calls not found.
> Expected: [call(['atlas_home/hbase/bin/hbase-daemon.sh', '--config', 
> 'atlas_home/hbase/conf', 'start', 'master'], 'atlas_home/logs', False, True), 
> call(['atlas_home/solr/bin/solr', 'start', '-z', 'localhost:9838', '-p', 
> '9838'], 'atlas_home/logs', False, True), call(['atlas_home/solr/bin/solr', 
> 'create', '-c', 'vertex_index', '-d', 'atlas_home/conf/solr', '-shards', '1', 
> '-replicationFactor', '1'], 'atlas_home/logs', False, True), 
> call(['atlas_home/solr/bin/solr', 'create', '-c', 'edge_index', '-d', 
> 'atlas_home/conf/solr', '-shards', '1', '-replicationFactor', '1'], 
> 'atlas_home/logs', False, True), call(['atlas_home/solr/bin/solr', 'create', 
> '-c', 'fulltext_index', '-d', 'atlas_home/conf/solr', '-shards', '1', 
> '-replicationFactor', '1'], 'atlas_home/logs', False, True)]
> Actual: [call(['atlas_home/hbase/bin/hbase-daemon.sh', '--config', 
> 'atlas_home/hbase/conf', 'start', 'master'], 'atlas_home/logs', False, True),
>  call(['atlas_home/solr/bin/solr', 'start', '-z', 'localhost:9838', '-p', 
> '9838'], 'atlas_home/logs', False, True),
>  call(['atlas_home/solr/bin/solr', 'create', '-c', 'vertex_index', '-d', 
> 'atlas_home/solr/server/solr/configsets/_default/conf', '-shards', '1', 
> '-replicationFactor', '1'], 'atlas_home/logs', False, True),
>  call(['atlas_home/solr/bin/solr', 'create', '-c', 'edge_index', '-d', 
> 'atlas_home/solr/server/solr/configsets/_default/conf', '-shards', '1', 
> '-replicationFactor', '1'], 'atlas_home/logs', False, True),
>  call(['atlas_home/solr/bin/solr', 'create', '-c', 'fulltext_index', '-d', 
> 'atlas_home/solr/server/solr/configsets/_default/conf', '-shards', '1', 
> '-replicationFactor', '1'], 'atlas_home/logs', False, True)]
> {code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-3271) Investigate and fix test failures in atlas-distro module

[Madhan Neethiraj (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16859062#comment-16859062
 ] 

Madhan Neethiraj commented on ATLAS-3271:
-

+1 for the patch. Thanks Sarath!

> Investigate and fix test failures in atlas-distro module
> 
>
> Key: ATLAS-3271
> URL: https://issues.apache.org/jira/browse/ATLAS-3271
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Attachments: ATLAS-3271.001.patch
>
>
> Fix failing test:
> {code}
> ==
> FAIL: test_main_embedded (TestMetadata.TestMetadata)
> --
> Traceback (most recent call last):
>   File 
> "/home/jenkins/jenkins-slave/workspace/Atlas-master-AllTests/distro/src/test/mock/mock.py",
>  line 1199, in patched
> return func(*args, **keywargs)
>   File 
> "/home/jenkins/jenkins-slave/workspace/Atlas-master-AllTests/distro/src/test/python/scripts/TestMetadata.py",
>  line 121, in test_main_embedded
> runProcess_mock.assert_has_calls(calls)
>   File 
> "/home/jenkins/jenkins-slave/workspace/Atlas-master-AllTests/distro/src/test/mock/mock.py",
>  line 861, in assert_has_calls
> 'Actual: %r' % (calls, self.mock_calls)
> AssertionError: Calls not found.
> Expected: [call(['atlas_home/hbase/bin/hbase-daemon.sh', '--config', 
> 'atlas_home/hbase/conf', 'start', 'master'], 'atlas_home/logs', False, True), 
> call(['atlas_home/solr/bin/solr', 'start', '-z', 'localhost:9838', '-p', 
> '9838'], 'atlas_home/logs', False, True), call(['atlas_home/solr/bin/solr', 
> 'create', '-c', 'vertex_index', '-d', 'atlas_home/conf/solr', '-shards', '1', 
> '-replicationFactor', '1'], 'atlas_home/logs', False, True), 
> call(['atlas_home/solr/bin/solr', 'create', '-c', 'edge_index', '-d', 
> 'atlas_home/conf/solr', '-shards', '1', '-replicationFactor', '1'], 
> 'atlas_home/logs', False, True), call(['atlas_home/solr/bin/solr', 'create', 
> '-c', 'fulltext_index', '-d', 'atlas_home/conf/solr', '-shards', '1', 
> '-replicationFactor', '1'], 'atlas_home/logs', False, True)]
> Actual: [call(['atlas_home/hbase/bin/hbase-daemon.sh', '--config', 
> 'atlas_home/hbase/conf', 'start', 'master'], 'atlas_home/logs', False, True),
>  call(['atlas_home/solr/bin/solr', 'start', '-z', 'localhost:9838', '-p', 
> '9838'], 'atlas_home/logs', False, True),
>  call(['atlas_home/solr/bin/solr', 'create', '-c', 'vertex_index', '-d', 
> 'atlas_home/solr/server/solr/configsets/_default/conf', '-shards', '1', 
> '-replicationFactor', '1'], 'atlas_home/logs', False, True),
>  call(['atlas_home/solr/bin/solr', 'create', '-c', 'edge_index', '-d', 
> 'atlas_home/solr/server/solr/configsets/_default/conf', '-shards', '1', 
> '-replicationFactor', '1'], 'atlas_home/logs', False, True),
>  call(['atlas_home/solr/bin/solr', 'create', '-c', 'fulltext_index', '-d', 
> 'atlas_home/solr/server/solr/configsets/_default/conf', '-shards', '1', 
> '-replicationFactor', '1'], 'atlas_home/logs', False, True)]
> {code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ATLAS-3269) basic-search for entities with no-classifications and a search string returns empty result

[Madhan Neethiraj (JIRA)]

Madhan Neethiraj created ATLAS-3269:
---

 Summary: basic-search for entities with no-classifications and a 
search string returns empty result
 Key: ATLAS-3269
 URL: https://issues.apache.org/jira/browse/ATLAS-3269
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Madhan Neethiraj
Assignee: Madhan Neethiraj


ATLAS-2775 introduced basic-search enhancements to search for entities having 
no classification associated. However, such a search along with a free-text 
search string, returns empty result. For example, search with 
{{query=hive_table, classificationName=_NOT_CLASSIFIED}} returns empty results, 
though Atlas has a number of hive_table entities having no classification 
associated.

Please note however that the search for entities having any classification 
return correct results i.e {{query=hive_table, classificationName=_CLASSIFIED}} 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ATLAS-3262) disable full-text index population when free-text is enabled

[Madhan Neethiraj (JIRA)]

Madhan Neethiraj created ATLAS-3262:
---

 Summary: disable full-text index population when free-text is 
enabled
 Key: ATLAS-3262
 URL: https://issues.apache.org/jira/browse/ATLAS-3262
 Project: Atlas
  Issue Type: Improvement
  Components:  atlas-core
Affects Versions: 2.1.0
Reporter: Madhan Neethiraj
Assignee: Madhan Neethiraj


Free-text search introduced/updated in ATLAS-3100 and ATLAS-3246 uses Solr 
index fields of entity attributes to perform text searches. When free-text 
search is enabled (i.e. when Solr is the index backend), full-text collection 
is not used, hence should not be updated during entity create/update. This is 
likely to result in sizable time in processing notifications, in addition to 
reducing the load on Solr.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-3258) Update apache-rat-plugin to 0.13

[Madhan Neethiraj (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16855741#comment-16855741
 ] 

Madhan Neethiraj commented on ATLAS-3258:
-

+1 for the patch.

> Update apache-rat-plugin to 0.13
> 
>
> Key: ATLAS-3258
> URL: https://issues.apache.org/jira/browse/ATLAS-3258
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-intg, atlas-webui
>Affects Versions: 3.0.0
>Reporter: Diego Marino Monetti
>Assignee: Sarath Subramanian
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: ATLAS-3258.001.patch
>
>
> Is it possible use the rat-check module 0.13 ? It's not essential but on 
> Eclipse I get a lot of annoying warnings / errors solved by 0.13. I tried 
> using 0.13 and it seems not to create regressions. Thanks



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-3227) Bulk delete does not delete the indexes properly

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-3227:

Fix Version/s: 0.8.4

> Bulk delete does not delete the indexes properly
> 
>
> Key: ATLAS-3227
> URL: https://issues.apache.org/jira/browse/ATLAS-3227
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
> Environment: All
>Reporter: Diego Marino Monetti
>Assignee: Madhan Neethiraj
>Priority: Major
>  Labels: pull-request-available
> Fix For: 0.8.4, 1.2.0, 2.1.0, 3.0.0
>
> Attachments: ATLAS-3227-2.patch, ATLAS-3227-branch-0.8.patch, 
> ATLAS-3227.patch, application-with-patch.log, application-without-patch.log, 
> bulkCreateType, bulkDeleteType, sample_type.json
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently the Bulk Delete, first clears the cache and then does physical 
> deletion from Janus of the required types. At the end of this operation it 
> cycles through the attributes of the deleted types and for those attributes 
> for which it is possible to have indexes, built-ins, enums and structs, marks 
> the indexes as deleted. Since for each attribute the routine goes back to the 
> type of attribute using the typeRegistry, that is the cache, if this 
> attribute is a custom type the attribute was deleted before and the bulk 
> delete partially fails.
> In particular, for each attribute in which this error does not occur, for 
> example because built-in type, a label delete is added to the property key 
> with the number of occurrences with which this property key is present in the 
> store. Something like property_key_deleted_0. In fact, if you try to reload 
> the same types and re-delete,  the property keys are now marked as 
> property_key_deleted_1.
> If, however, for the aforementioned reason the search for the type in the 
> cache fails the property key is not marked and remains fully active, which, 
> from what I can understand at this level of my knowledge, generates at least 
> some MEMORY LEAKs.
> If I reload the types with the same entities and attributes it seems to be 
> all right, but if I change some attributes, in my opinion, the result is 
> unpredictable.
> This path tested on version 2.0 and SNAPSHOT 3.0 would resolve this issue.
> In attachment there is a small example that shows this behavior with and 
> without this patch



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-3227) Bulk delete does not delete the indexes properly

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-3227:

Attachment: ATLAS-3227-branch-0.8.patch

> Bulk delete does not delete the indexes properly
> 
>
> Key: ATLAS-3227
> URL: https://issues.apache.org/jira/browse/ATLAS-3227
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
> Environment: All
>Reporter: Diego Marino Monetti
>Assignee: Madhan Neethiraj
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.2.0, 2.1.0, 3.0.0
>
> Attachments: ATLAS-3227-2.patch, ATLAS-3227-branch-0.8.patch, 
> ATLAS-3227.patch, application-with-patch.log, application-without-patch.log, 
> bulkCreateType, bulkDeleteType, sample_type.json
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently the Bulk Delete, first clears the cache and then does physical 
> deletion from Janus of the required types. At the end of this operation it 
> cycles through the attributes of the deleted types and for those attributes 
> for which it is possible to have indexes, built-ins, enums and structs, marks 
> the indexes as deleted. Since for each attribute the routine goes back to the 
> type of attribute using the typeRegistry, that is the cache, if this 
> attribute is a custom type the attribute was deleted before and the bulk 
> delete partially fails.
> In particular, for each attribute in which this error does not occur, for 
> example because built-in type, a label delete is added to the property key 
> with the number of occurrences with which this property key is present in the 
> store. Something like property_key_deleted_0. In fact, if you try to reload 
> the same types and re-delete,  the property keys are now marked as 
> property_key_deleted_1.
> If, however, for the aforementioned reason the search for the type in the 
> cache fails the property key is not marked and remains fully active, which, 
> from what I can understand at this level of my knowledge, generates at least 
> some MEMORY LEAKs.
> If I reload the types with the same entities and attributes it seems to be 
> all right, but if I change some attributes, in my opinion, the result is 
> unpredictable.
> This path tested on version 2.0 and SNAPSHOT 3.0 would resolve this issue.
> In attachment there is a small example that shows this behavior with and 
> without this patch



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-3227) Bulk delete does not delete the indexes properly

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-3227:

Fix Version/s: 1.2.0

> Bulk delete does not delete the indexes properly
> 
>
> Key: ATLAS-3227
> URL: https://issues.apache.org/jira/browse/ATLAS-3227
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
> Environment: All
>Reporter: Diego Marino Monetti
>Assignee: Madhan Neethiraj
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.2.0, 2.1.0, 3.0.0
>
> Attachments: ATLAS-3227-2.patch, ATLAS-3227.patch, 
> application-with-patch.log, application-without-patch.log, bulkCreateType, 
> bulkDeleteType, sample_type.json
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently the Bulk Delete, first clears the cache and then does physical 
> deletion from Janus of the required types. At the end of this operation it 
> cycles through the attributes of the deleted types and for those attributes 
> for which it is possible to have indexes, built-ins, enums and structs, marks 
> the indexes as deleted. Since for each attribute the routine goes back to the 
> type of attribute using the typeRegistry, that is the cache, if this 
> attribute is a custom type the attribute was deleted before and the bulk 
> delete partially fails.
> In particular, for each attribute in which this error does not occur, for 
> example because built-in type, a label delete is added to the property key 
> with the number of occurrences with which this property key is present in the 
> store. Something like property_key_deleted_0. In fact, if you try to reload 
> the same types and re-delete,  the property keys are now marked as 
> property_key_deleted_1.
> If, however, for the aforementioned reason the search for the type in the 
> cache fails the property key is not marked and remains fully active, which, 
> from what I can understand at this level of my knowledge, generates at least 
> some MEMORY LEAKs.
> If I reload the types with the same entities and attributes it seems to be 
> all right, but if I change some attributes, in my opinion, the result is 
> unpredictable.
> This path tested on version 2.0 and SNAPSHOT 3.0 would resolve this issue.
> In attachment there is a small example that shows this behavior with and 
> without this patch



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-3180) New Bulk retrieval API with servicetype parameter

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-3180:

Fix Version/s: 1.2.0

>  New Bulk retrieval API with servicetype parameter
> --
>
> Key: ATLAS-3180
> URL: https://issues.apache.org/jira/browse/ATLAS-3180
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.2.0, 2.0.0
> Environment: All OS
>Reporter: Diego Marino Monetti
>Assignee: Diego Marino Monetti
>Priority: Major
> Fix For: 1.2.0, 2.1.0, 3.0.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The Bulk api retrieval returns all defined types or filtered types by name, 
> type and supertype. With the addition of the service type among the basic 
> attributes of the Atlas types it is necessary to have the possibility to 
> search also for service type through a http request of the type:
> {quote}[http://host:port/api/atlas/V2/types/typedefs?serviceType|http://hostport/]
>  = requested-service-type
> {quote}
> to search only for types related to a specific service type.
>  This pull request solves this problem
> l[https://github.com/apache/atlas/pull/49]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (ATLAS-3227) Bulk delete does not delete the indexes properly

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj reassigned ATLAS-3227:
---

   Resolution: Fixed
 Assignee: Madhan Neethiraj
Fix Version/s: (was: trunk)
   3.0.0
   2.1.0

> Bulk delete does not delete the indexes properly
> 
>
> Key: ATLAS-3227
> URL: https://issues.apache.org/jira/browse/ATLAS-3227
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
> Environment: All
>Reporter: Diego Marino Monetti
>Assignee: Madhan Neethiraj
>Priority: Major
>  Labels: pull-request-available
> Fix For: 2.1.0, 3.0.0
>
> Attachments: ATLAS-3227-2.patch, ATLAS-3227.patch, 
> application-with-patch.log, application-without-patch.log, bulkCreateType, 
> bulkDeleteType, sample_type.json
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently the Bulk Delete, first clears the cache and then does physical 
> deletion from Janus of the required types. At the end of this operation it 
> cycles through the attributes of the deleted types and for those attributes 
> for which it is possible to have indexes, built-ins, enums and structs, marks 
> the indexes as deleted. Since for each attribute the routine goes back to the 
> type of attribute using the typeRegistry, that is the cache, if this 
> attribute is a custom type the attribute was deleted before and the bulk 
> delete partially fails.
> In particular, for each attribute in which this error does not occur, for 
> example because built-in type, a label delete is added to the property key 
> with the number of occurrences with which this property key is present in the 
> store. Something like property_key_deleted_0. In fact, if you try to reload 
> the same types and re-delete,  the property keys are now marked as 
> property_key_deleted_1.
> If, however, for the aforementioned reason the search for the type in the 
> cache fails the property key is not marked and remains fully active, which, 
> from what I can understand at this level of my knowledge, generates at least 
> some MEMORY LEAKs.
> If I reload the types with the same entities and attributes it seems to be 
> all right, but if I change some attributes, in my opinion, the result is 
> unpredictable.
> This path tested on version 2.0 and SNAPSHOT 3.0 would resolve this issue.
> In attachment there is a small example that shows this behavior with and 
> without this patch



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ATLAS-3180) New Bulk retrieval API with servicetype parameter

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj resolved ATLAS-3180.
-
   Resolution: Fixed  (was: Abandoned)
 Assignee: Diego Marino Monetti
Fix Version/s: (was: 1.2.0)
   (was: trunk)
   3.0.0
   2.1.0

>  New Bulk retrieval API with servicetype parameter
> --
>
> Key: ATLAS-3180
> URL: https://issues.apache.org/jira/browse/ATLAS-3180
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.2.0, 2.0.0
> Environment: All OS
>Reporter: Diego Marino Monetti
>Assignee: Diego Marino Monetti
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> The Bulk api retrieval returns all defined types or filtered types by name, 
> type and supertype. With the addition of the service type among the basic 
> attributes of the Atlas types it is necessary to have the possibility to 
> search also for service type through a http request of the type:
> {quote}[http://host:port/api/atlas/V2/types/typedefs?serviceType|http://hostport/]
>  = requested-service-type
> {quote}
> to search only for types related to a specific service type.
>  This pull request solves this problem
> l[https://github.com/apache/atlas/pull/49]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-3245) Swap build order of impala-bridge and impala-bridge-shim maven module

[Madhan Neethiraj (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851460#comment-16851460
 ] 

Madhan Neethiraj commented on ATLAS-3245:
-

+1 for the patch. This makes it consistent with other hooks & their 
corresponding shim.

> Swap build order of impala-bridge and impala-bridge-shim maven module
> -
>
> Key: ATLAS-3245
> URL: https://issues.apache.org/jira/browse/ATLAS-3245
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: ATLAS-3245.01.patch
>
>
> Currently the build order builds:
>  * impala-bridge
>  * impala-bridge-shim
> but impala-bridge has a dependency on shim module and hence shim module needs 
> to be build before impala-bridge.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-3227) Bulk delete does not delete the indexes properly

[Madhan Neethiraj (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16849174#comment-16849174
 ] 

Madhan Neethiraj commented on ATLAS-3227:
-

bq. What is the trunk release ?
2.0.0 was released on May-14-12019. Hence updated the fixVersion to trunk. Next 
trunk release, from master branch, will be 3.0.0.

> Bulk delete does not delete the indexes properly
> 
>
> Key: ATLAS-3227
> URL: https://issues.apache.org/jira/browse/ATLAS-3227
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
> Environment: All
>Reporter: Diego Marino Monetti
>Priority: Major
>  Labels: pull-request-available
> Fix For: trunk
>
> Attachments: ATLAS-3227.patch, application-with-patch.log, 
> application-without-patch.log, bulkCreateType, bulkDeleteType, 
> sample_type.json
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently the Bulk Delete, first clears the cache and then does physical 
> deletion from Janus of the required types. At the end of this operation it 
> cycles through the attributes of the deleted types and for those attributes 
> for which it is possible to have indexes, built-ins, enums and structs, marks 
> the indexes as deleted. Since for each attribute the routine goes back to the 
> type of attribute using the typeRegistry, that is the cache, if this 
> attribute is a custom type the attribute was deleted before and the bulk 
> delete partially fails.
> In particular, for each attribute in which this error does not occur, for 
> example because built-in type, a label delete is added to the property key 
> with the number of occurrences with which this property key is present in the 
> store. Something like property_key_deleted_0. In fact, if you try to reload 
> the same types and re-delete,  the property keys are now marked as 
> property_key_deleted_1.
> If, however, for the aforementioned reason the search for the type in the 
> cache fails the property key is not marked and remains fully active, which, 
> from what I can understand at this level of my knowledge, generates at least 
> some MEMORY LEAKs.
> If I reload the types with the same entities and attributes it seems to be 
> all right, but if I change some attributes, in my opinion, the result is 
> unpredictable.
> This path tested on version 2.0 and SNAPSHOT 3.0 would resolve this issue.
> In attachment there is a small example that shows this behavior with and 
> without this patch



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2928) Namespace entity relationship-attribute names to avoid conflict with entity attributes

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2928:

Fix Version/s: (was: 2.0.0)
   trunk

> Namespace entity relationship-attribute names to avoid conflict with entity 
> attributes
> --
>
> Key: ATLAS-2928
> URL: https://issues.apache.org/jira/browse/ATLAS-2928
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0, 1.1.0
>Reporter: Madhan Neethiraj
>Assignee: Le Ma
>Priority: Critical
> Fix For: 1.2.0, trunk
>
>
> Apache Atlas 1.0 introduced relationships as first-class types. A 
> relationship effectively 'injects' an attribute on the entities at each end. 
> For example, assignment of a glossary term to an entity is captured by 
> relationship AtlasGlossarySemanticAssignment (in 
> -Area0/0011-glossary_model.json). This relationship adds following 
> attributes:
> - Referceable.meanings: set
> - AtlasGlossaryTerm.assignedEntities: set
> This works fine as long as the entity-types involved in the relationship, or 
> their sub-types don't have an attribute with the same name as the attribute 
> injected by the relationships. Once such instance was reported by [~bolke], 
> about relationship attribute DataSet.schema introduced by 
> avro_schema_associatedEntities - which conflicts with spark_table.schema, 
> since spark_table type is a sub-type of DataSet.
> Such name conflicts can be avoided by prefixing relationship-attribute names 
> with a prefix like "r:".



--
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

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-3232:

Fix Version/s: (was: 2.0.0)
   trunk

> 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: trunk
>
>
> 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] [Updated] (ATLAS-2859) Basic search loads atlas internal type entities when searched with _NOT_CLASSIFIED classification paramter

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2859:

Fix Version/s: (was: 2.0.0)
   trunk

> Basic search loads atlas internal type entities when searched with 
> _NOT_CLASSIFIED classification paramter
> --
>
> Key: ATLAS-2859
> URL: https://issues.apache.org/jira/browse/ATLAS-2859
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 1.0.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 1.2.0, trunk
>
> Attachments: 
> 0001-ATLAS-2859-Fix-to-not-loads-atlas-internal-type-enti.patch, 
> _NOT_CLASSIFIED.png
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-3198) update/delete/truncate operations ATLAS_HOOK and ATLAS_ENTITIES improvements

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-3198:

Fix Version/s: (was: 2.0.0)
   trunk

> update/delete/truncate operations ATLAS_HOOK and ATLAS_ENTITIES improvements 
> -
>
> Key: ATLAS-3198
> URL: https://issues.apache.org/jira/browse/ATLAS-3198
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 2.0.0
>Reporter: Umesh Padashetty
>Assignee: Yu-Hsin Chang
>Priority: Critical
> Fix For: trunk
>
> Attachments: ATLAS_HOOK and ATLAS_ENTITIES messages.xlsx
>
>
> With the recent changes, we have now stopped ingesting simple insert 
> operations since with this operation, there is no change in the metadata. 
> Ideally, we should be doing similar improvements w.r.t. update, delete and 
> truncate operations too. 
> Currently, for update/delete/truncate, we are pushing messages in both 
> ATLAS_HOOK as well as ATLAS_ENTITIES topic, which can be avoided. 
> If we stop ingesting updates/deletes/truncates, it will further help us 
> reduce the burden on Kafka and save CPU cycles
> I have created and attached an excel sheet, with the list of operations and 
> the corresponding messages generated in ATLAS_HOOK and ATLAS_ENTITIES topic, 
> along with suitable comments. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-3086) Regression : Atlas Hive Hook doesn't capture insert into table values() queries

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-3086:

Fix Version/s: (was: 2.0.0)
   trunk

> 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
>Priority: Major
> Fix For: trunk
>
>
> 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] [Updated] (ATLAS-3219) Implemented new serviceType Rest API

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-3219:

Fix Version/s: (was: 2.0.0)
   trunk

> Implemented new serviceType Rest API
> 
>
> Key: ATLAS-3219
> URL: https://issues.apache.org/jira/browse/ATLAS-3219
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-intg
>Affects Versions: 2.0.0
> Environment: all
>Reporter: Diego Marino Monetti
>Priority: Major
> Fix For: trunk
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> This pull request supersedes the pull request ATLAS-3180.
> The new basic attribute serviceType, introduced by Atlas Team, has no use if 
> it is not searchable ina any way. This pull request solves this problem by 
> adding the following REST APIs.
> GET / typedef / servicetype / \{servicetype}
> GET / typedefs / headers? Servicetype = \{serviceType}
> GET / typedefs? Servicetype = \{servicetype}
> GET / enumdef / servicetype / \{servicetype}
> GET / entitydef / servicetype / \{servicetype}
> GET / structdef / servicetype / \{servicetype}
> GET / relationshipdef / servicetype / \{servicetype}
> DELETE / typedef / servicetype / \{servicetype}
> The APIs were tested on ATLAS 2.0 and on the new SNAPSHOT 3.0



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-3161) Add support for Java11

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-3161:

Fix Version/s: (was: 2.0.0)
   trunk

> Add support for Java11
> --
>
> Key: ATLAS-3161
> URL: https://issues.apache.org/jira/browse/ATLAS-3161
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Diego Marino Monetti
>Priority: Major
> Fix For: trunk
>
>
> To support Java11 distribution needs add javax.annotation to atlas-common 
> project



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-3012) Import of hive_db fails to create deleted column entity which was recreated again.

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-3012:

Fix Version/s: (was: 2.0.0)
   trunk

> Import of hive_db fails to create deleted column entity which was recreated 
> again. 
> ---
>
> Key: ATLAS-3012
> URL: https://issues.apache.org/jira/browse/ATLAS-3012
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-intg
>Affects Versions: 1.1.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: trunk
>
> Attachments: ATLAS-3012.patch, response.zip
>
>
>  *Following is the test scenario:*
> In the source cluster :
> 1. create table with 3 columns (id,name,dob)
> 2. drop column dob
> 3. add the same dob column again.
> Now table has 3 ACTIVE columns and 1 DELETED column.
> Export the db into the target cluster.
> In the target cluster :
> only 2 ACTIVE (id,name) and 1 DELETED (dob) column is present. The ACTIVE 
> column (dob) is not present.
> The exported zip contains both the DELETED and the ACTIVE dob column entity.
> In the source cluster ,
> if GUID1 is GUID of ACTIVE dob entity , and GUID2 is GUID of deleted dob 
> entity.
> In the target cluster , 
> GUID1 is GUID of DELETED entity.
> Example : 
> *In source :*
> ACTIVE: 
> [https://atlas_source_host/index.html#!/detailPage/7cca7064-8519-4db3-aab5-ebd446d15070|https://ctr-e139-1542663976389-33282-01-08.hwx.site:21443/index.html#!/detailPage/7cca7064-8519-4db3-aab5-ebd446d15070]
> DELETED:[https://|https://ctr-e139-1542663976389-33282-01-08.hwx.site:21443/index.html#!/detailPage/f7686214-7585-4da3-875f-3e5223875289]
>  
> [atlas_source_host|https://ctr-e139-1542663976389-33282-01-08.hwx.site:21443/index.html#!/detailPage/7cca7064-8519-4db3-aab5-ebd446d15070]
>  
> [/index.html#!/detailPage/f7686214-7585-4da3-875f-3e5223875289|https://ctr-e139-1542663976389-33282-01-08.hwx.site:21443/index.html#!/detailPage/f7686214-7585-4da3-875f-3e5223875289]
> *In target :*
> DELETED : 
> [https://|https://ctr-e139-1542663976389-33282-01-07.hwx.site:21443/index.html#!/detailPage/7cca7064-8519-4db3-aab5-ebd446d15070]
>  
> [atlas_target_host|https://ctr-e139-1542663976389-33282-01-08.hwx.site:21443/index.html#!/detailPage/7cca7064-8519-4db3-aab5-ebd446d15070]
>  
> [/index.html#!/detailPage/7cca7064-8519-4db3-aab5-ebd446d15070|https://ctr-e139-1542663976389-33282-01-07.hwx.site:21443/index.html#!/detailPage/7cca7064-8519-4db3-aab5-ebd446d15070]
> *{color:#d04437}Entity with GUID f7686214-7585-4da3-875f-3e5223875289 is not 
> found.{color}*
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2964) Unit TestCases for Exporting multiple hdfs_path

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2964:

Fix Version/s: (was: 2.0.0)
   trunk

> Unit TestCases for Exporting multiple hdfs_path
> ---
>
> Key: ATLAS-2964
> URL: https://issues.apache.org/jira/browse/ATLAS-2964
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Kapildeo Nayak
>Assignee: Kapildeo Nayak
>Priority: Major
> Fix For: trunk
>
> Attachments: 
> 0001-ATLAS-2964-Unit-TestCases-for-Exporting-multiple-hdf.patch
>
>
> Modified: HdfsPathEntityHandler.java returned path instead of name in 
> toPath() method.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-3163) Incorrect syntax for combine-children in repository pom

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-3163:

Fix Version/s: (was: 2.0.0)
   trunk

> Incorrect syntax for combine-children in repository pom
> ---
>
> Key: ATLAS-3163
> URL: https://issues.apache.org/jira/browse/ATLAS-3163
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Diego Marino Monetti
>Priority: Major
> Fix For: trunk
>
>
> in atlas-repository the syntax 
> org.apache.maven.plugins
>  maven-surefire-plugin
>  
>  
> is incorrect.
> The correct syntax is
> org.apache.maven.plugins
>  maven-surefire-plugin
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-3227) Bulk delete does not delete the indexes properly

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-3227:

Fix Version/s: (was: 2.0.0)
   trunk

> Bulk delete does not delete the indexes properly
> 
>
> Key: ATLAS-3227
> URL: https://issues.apache.org/jira/browse/ATLAS-3227
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
> Environment: All
>Reporter: Diego Marino Monetti
>Priority: Major
>  Labels: pull-request-available
> Fix For: trunk
>
> Attachments: ATLAS-3227.patch, application-with-patch.log, 
> application-without-patch.log, bulkCreateType, bulkDeleteType, 
> sample_type.json
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently the Bulk Delete, first clears the cache and then does physical 
> deletion from Janus of the required types. At the end of this operation it 
> cycles through the attributes of the deleted types and for those attributes 
> for which it is possible to have indexes, built-ins, enums and structs, marks 
> the indexes as deleted. Since for each attribute the routine goes back to the 
> type of attribute using the typeRegistry, that is the cache, if this 
> attribute is a custom type the attribute was deleted before and the bulk 
> delete partially fails.
> In particular, for each attribute in which this error does not occur, for 
> example because built-in type, a label delete is added to the property key 
> with the number of occurrences with which this property key is present in the 
> store. Something like property_key_deleted_0. In fact, if you try to reload 
> the same types and re-delete,  the property keys are now marked as 
> property_key_deleted_1.
> If, however, for the aforementioned reason the search for the type in the 
> cache fails the property key is not marked and remains fully active, which, 
> from what I can understand at this level of my knowledge, generates at least 
> some MEMORY LEAKs.
> If I reload the types with the same entities and attributes it seems to be 
> all right, but if I change some attributes, in my opinion, the result is 
> unpredictable.
> This path tested on version 2.0 and SNAPSHOT 3.0 would resolve this issue.
> In attachment there is a small example that shows this behavior with and 
> without this patch



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-3042) Add relationship notification on drop table/column while processing hook message

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-3042:

Fix Version/s: (was: 2.0.0)
   trunk

> Add relationship notification on drop table/column while processing hook 
> message
> 
>
> Key: ATLAS-3042
> URL: https://issues.apache.org/jira/browse/ATLAS-3042
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: trunk
>Reporter: Nixon Rodrigues
>Priority: Major
> Fix For: trunk
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-3177) Regression , Export : changeMarker is not set right - set to older value compared to entity's lastModifedTime

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-3177:

Fix Version/s: (was: 2.0.0)
   trunk

> 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] [Updated] (ATLAS-3094) UniqueAttributes are not populating in relationship notification message

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-3094:

Fix Version/s: (was: 2.0.0)
   trunk

> UniqueAttributes are not populating in relationship notification message
> 
>
> Key: ATLAS-3094
> URL: https://issues.apache.org/jira/browse/ATLAS-3094
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Nikhil Bonte
>Assignee: Nikhil Bonte
>Priority: Major
> Fix For: trunk
>
> Attachments: 
> ATLAS-3094-UniqueAttributes-are-not-populating-in-re.patch
>
>
> UniqueAttributes are not populating in relationship notification message.
>  
> e.g. refer end2 which is not having uniqueAttributes :
>  
> {code:java}
> {
>  ...,
>  "message": {
>  "type": "ENTITY_NOTIFICATION_V2",
>  "relationship": {
>  "typeName": "hive_table_columns",
>  "guid": "3d3cec1f-e057-43a3-a167-cac69a1248a6",
>  "status": "ACTIVE",
>  "label": "__hive_table.columns",
>  "end1": {
>"guid": "c44a1dda-5c89-4b3c-9679-9b368ae9f18a",
>"typeName": "hive_table",
>"uniqueAttributes":{ 
>   "qualifiedName": "new_db.new_tbl_12@07012019" 
> }
>   },
>   "end2":{ 
> "guid": "85bf3819-8289-46ed-9279-34b28a4dbe35",
> "typeName": "hive_column" 
>   }
>  },
>  "operationType": "RELATIONSHIP_CREATE",
>  "eventTime": 1548828513837
>  }
> }
> {code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-3199) **/bin/** in .gitignore is commented

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-3199:

Fix Version/s: (was: 2.0.0)
   trunk

> **/bin/** in .gitignore is commented
> 
>
> Key: ATLAS-3199
> URL: https://issues.apache.org/jira/browse/ATLAS-3199
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
> Environment: all
>Reporter: Diego Marino Monetti
>Priority: Major
> Fix For: trunk
>
>
> I have no idea why, but thinking of some reason related to the development 
> team I didn't correct it. Can it be corrected? Create lots of untracked files 
> and confusion possibilities



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2800) UI - In Advance search an additional API request is fire when any column is drag and droped

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2800:

Fix Version/s: (was: 2.0.0)
   trunk

> UI - In Advance search an additional API request is fire when any column is 
> drag and droped
> ---
>
> Key: ATLAS-2800
> URL: https://issues.apache.org/jira/browse/ATLAS-2800
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8.1, 1.0.0, 2.0.0
>Reporter: Tejas Rawool
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 0.8.2, 1.2.0, trunk
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-3233) Relationships, Export & Import : Issue with ACTIVE and DELETED relationship-def instances

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-3233:

Fix Version/s: (was: 2.0.0)
   trunk

> 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
>Priority: Major
> Fix For: trunk
>
>
> 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] [Commented] (ATLAS-3125) Update version in branch-2.0 to 2.1.0-SNAPSHOT

[Madhan Neethiraj (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16839878#comment-16839878
 ] 

Madhan Neethiraj commented on ATLAS-3125:
-

+1 for the patch.

> Update version in branch-2.0 to 2.1.0-SNAPSHOT
> --
>
> Key: ATLAS-3125
> URL: https://issues.apache.org/jira/browse/ATLAS-3125
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: 
> 0001-ATLAS-3125-Update-version-in-branch-2.0-to-2.1.0-SNA.patch
>
>
> After Apache Atlas 2.0.0 has been released, update branch-2.0 to use version 
> 2.1.0-SNAPSHOT



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-3124) Update version in master branch to 3.0.0-SNAPSHOT

[Madhan Neethiraj (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16839876#comment-16839876
 ] 

Madhan Neethiraj commented on ATLAS-3124:
-

+1 for the patch.

> Update version in master branch to 3.0.0-SNAPSHOT
> -
>
> Key: ATLAS-3124
> URL: https://issues.apache.org/jira/browse/ATLAS-3124
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: 
> 0001-ATLAS-3124-Update-version-in-master-branch-to-3.0.0-.patch
>
>
> After Apache Atlas 2.0.0 has been released, update master branch to use 
> version 3.0.0-SNAPSHOT



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ATLAS-3135) delete null data from typedefs results in messy data

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj resolved ATLAS-3135.
-
   Resolution: Fixed
 Assignee: Madhan Neethiraj
Fix Version/s: (was: 1.1.0)
   trunk
   1.2.0
   0.8.4

> delete null data from typedefs results in messy data
> 
>
> Key: ATLAS-3135
> URL: https://issues.apache.org/jira/browse/ATLAS-3135
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.1.0
>Reporter: caoxuewen
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 0.8.4, 1.2.0, trunk
>
> Attachments: ATLAS-3135.patch, image-2019-04-13-11-45-12-868.png, 
> image-2019-04-13-11-45-20-381.png, image-2019-04-13-11-45-32-642.png, 
> image-2019-04-13-11-45-39-847.png, image-2019-04-13-11-45-47-698.png, 
> image-2019-04-13-11-46-23-779.png
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> Currently, when we use 
> [http://IP:21000/api/atlas/v2/types/typedefs/|http://ip:21000/api/atlas/v2/types/typedefs/],
>  deleting the data of typedefs is empty 
> (\{"enumDefs":[],"structDefs":[],"classificationDefs":[],"entityDefs":[],"relationshipDefs":[]}),
>  it will lead to messy data, and basic search error, so the atlas system must 
> be restarted in order to recover the data.
> Correct data:
> !image-2019-04-13-11-45-12-868.png!
> !image-2019-04-13-11-45-20-381.png!
>  
> exec 
> [http://IP:21000/api/atlas/v2/types/typedefs/|http://ip:21000/api/atlas/v2/types/typedefs/],
>  json data: 
> \{"enumDefs":[],"structDefs":[],"classificationDefs":[],"entityDefs":[],"relationshipDefs":[]}
> atlas entity data is: （basic search is error）
> !image-2019-04-13-11-45-32-642.png!
> messy data:
> !image-2019-04-13-11-45-39-847.png!
> !image-2019-04-13-11-46-23-779.png!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-3202) Hive hook: getStorageDescEntity() throws NPE if bucketCols is null

[Madhan Neethiraj (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835980#comment-16835980
 ] 

Madhan Neethiraj commented on ATLAS-3202:
-

+1 for the patch.

> Hive hook: getStorageDescEntity() throws NPE if bucketCols is null
> --
>
> Key: ATLAS-3202
> URL: https://issues.apache.org/jira/browse/ATLAS-3202
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Minor
> Fix For: trunk
>
> Attachments: 
> 0001-ATLAS-3202-Hive-hook-getStorageDescEntity-throws-NPE.patch
>
>
> Null check needs to be added when we create a storageDesc entity in hive hook.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-3135) delete null data from typedefs results in messy data

[Madhan Neethiraj (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835325#comment-16835325
 ] 

Madhan Neethiraj commented on ATLAS-3135:
-

[~heary-cao] - thanks for reporting the issue and the details. I was able to 
reproduce the issue. Here is background/root cause for the issue:
- an instance of AtlasTypeRegistry is used to perform consistency checks 
(resolve references between types) and cache the types in-memory
- for any typedef changes (add/update/delete of types):
## Atlas creates a transient-type-registry with copy of types in 
AtaslTypeResgistry
## perform the necessary changes in the transient-type-registry
## resolve references to ensure that type changes don't break consistency
## copy the types from transient-type-registry to AtlasTypeRegistry
- when delete is called with empty typesdef, #3 above is not performed, 
resulting in AtlasTypeRegistry in unresolved state - which causes the issues 
reported in this JIRA.

So, the correct fix will be to resolve-references (#3 above) in all typedef 
update calls. Attached patch file  [^ATLAS-3135.patch] has this fix; I verified 
that this addresses the issue reported here. While the patch you provided 
addresses the issue with empty typesdef, the fix in  [^ATLAS-3135.patch] 
handles all calls that can update types-registry. Please review this patch and 
let me know your feedback.

> delete null data from typedefs results in messy data
> 
>
> Key: ATLAS-3135
> URL: https://issues.apache.org/jira/browse/ATLAS-3135
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.1.0
>Reporter: caoxuewen
>Priority: Major
> Fix For: 1.1.0
>
> Attachments: ATLAS-3135.patch, image-2019-04-13-11-45-12-868.png, 
> image-2019-04-13-11-45-20-381.png, image-2019-04-13-11-45-32-642.png, 
> image-2019-04-13-11-45-39-847.png, image-2019-04-13-11-45-47-698.png, 
> image-2019-04-13-11-46-23-779.png
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> Currently, when we use 
> [http://IP:21000/api/atlas/v2/types/typedefs/|http://ip:21000/api/atlas/v2/types/typedefs/],
>  deleting the data of typedefs is empty 
> (\{"enumDefs":[],"structDefs":[],"classificationDefs":[],"entityDefs":[],"relationshipDefs":[]}),
>  it will lead to messy data, and basic search error, so the atlas system must 
> be restarted in order to recover the data.
> Correct data:
> !image-2019-04-13-11-45-12-868.png!
> !image-2019-04-13-11-45-20-381.png!
>  
> exec 
> [http://IP:21000/api/atlas/v2/types/typedefs/|http://ip:21000/api/atlas/v2/types/typedefs/],
>  json data: 
> \{"enumDefs":[],"structDefs":[],"classificationDefs":[],"entityDefs":[],"relationshipDefs":[]}
> atlas entity data is: （basic search is error）
> !image-2019-04-13-11-45-32-642.png!
> messy data:
> !image-2019-04-13-11-45-39-847.png!
> !image-2019-04-13-11-46-23-779.png!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-3135) delete null data from typedefs results in messy data

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-3135:

Attachment: ATLAS-3135.patch

> delete null data from typedefs results in messy data
> 
>
> Key: ATLAS-3135
> URL: https://issues.apache.org/jira/browse/ATLAS-3135
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.1.0
>Reporter: caoxuewen
>Priority: Major
> Fix For: 1.1.0
>
> Attachments: ATLAS-3135.patch, image-2019-04-13-11-45-12-868.png, 
> image-2019-04-13-11-45-20-381.png, image-2019-04-13-11-45-32-642.png, 
> image-2019-04-13-11-45-39-847.png, image-2019-04-13-11-45-47-698.png, 
> image-2019-04-13-11-46-23-779.png
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> Currently, when we use 
> [http://IP:21000/api/atlas/v2/types/typedefs/|http://ip:21000/api/atlas/v2/types/typedefs/],
>  deleting the data of typedefs is empty 
> (\{"enumDefs":[],"structDefs":[],"classificationDefs":[],"entityDefs":[],"relationshipDefs":[]}),
>  it will lead to messy data, and basic search error, so the atlas system must 
> be restarted in order to recover the data.
> Correct data:
> !image-2019-04-13-11-45-12-868.png!
> !image-2019-04-13-11-45-20-381.png!
>  
> exec 
> [http://IP:21000/api/atlas/v2/types/typedefs/|http://ip:21000/api/atlas/v2/types/typedefs/],
>  json data: 
> \{"enumDefs":[],"structDefs":[],"classificationDefs":[],"entityDefs":[],"relationshipDefs":[]}
> atlas entity data is: （basic search is error）
> !image-2019-04-13-11-45-32-642.png!
> messy data:
> !image-2019-04-13-11-45-39-847.png!
> !image-2019-04-13-11-46-23-779.png!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ATLAS-3187) Regression, Relationship updates : In GET entity definition of a deleted table, columns,sd etc., are empty

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj resolved ATLAS-3187.
-
Resolution: Fixed

> 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
>Priority: Critical
> 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] [Commented] (ATLAS-3155) UI - IE-11 - Name entry not clickable

[Madhan Neethiraj (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16832252#comment-16832252
 ] 

Madhan Neethiraj commented on ATLAS-3155:
-

+1 for  [^ATLAS-3155-2.patch]. Thanks [~kevalbhatt] for the patch.

> UI - IE-11 - Name entry not clickable
> -
>
> Key: ATLAS-3155
> URL: https://issues.apache.org/jira/browse/ATLAS-3155
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Rahul Kurup
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
> Attachments: ATLAS-3155-2.patch, ATLAS-3155.patch, ie11_name_issue.jpg
>
>
> In the search results page, when we try to click the 'Name' column value of 
> any entry, nothing happens.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-3033) ATLAS Hive hook fails for CTAS query involving UDFs

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-3033:

Attachment: ATLAS-3033-branch-2.0.patch

> ATLAS Hive hook fails for CTAS query involving UDFs
> ---
>
> Key: ATLAS-3033
> URL: https://issues.apache.org/jira/browse/ATLAS-3033
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8.3
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 0.8.4
>
> Attachments: ATLAS-3033-branch-2.0.patch, ATLAS-3033-master.patch, 
> ATLAS-3033.patch
>
>
> ATLAS Hive Hook fails to notify for CTAS queries involving UDFs, Hook fails 
> with the exception as below
> {code}
> org.apache.hadoop.hive.ql.metadata.InvalidTableException: Table not found 
> _dummy_table
> {code}
> complete stack trace.
> {code}
> 2018-12-26 12:15:22,234 ERROR [HiveServer2-Background-Pool: Thread-339]: 
> metadata.Hive (Hive.java:getTable(1220)) - Table _dummy_table not found: 
> _dummy_database._
> dummy_table table not found
> 2018-12-26 12:15:22,234 ERROR [HiveServer2-Background-Pool: Thread-339]: 
> hook.HiveHook (HiveHook.java:run(160)) - HiveHook.run(): failed to process 
> operation CREAT
> ETABLE_AS_SELECT
> org.apache.hadoop.hive.ql.metadata.InvalidTableException: Table not found 
> _dummy_table
> at org.apache.hadoop.hive.ql.metadata.Hive.getTable(Hive.java:1221)
> at org.apache.hadoop.hive.ql.metadata.Hive.getTable(Hive.java:1191)
> at 
> org.apache.atlas.hive.hook.events.BaseHiveEvent.toAtlasEntity(BaseHiveEvent.java:225)
> at 
> org.apache.atlas.hive.hook.events.BaseHiveEvent.getInputOutputEntity(BaseHiveEvent.java:203)
> at 
> org.apache.atlas.hive.hook.events.CreateHiveProcess.getEntities(CreateHiveProcess.java:84)
> at 
> org.apache.atlas.hive.hook.events.CreateHiveProcess.getNotificationMessages(CreateHiveProcess.java:59)
> at org.apache.atlas.hive.hook.HiveHook.run(HiveHook.java:157)
> at org.apache.atlas.hive.hook.HiveHook.run(HiveHook.java:52)
> at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1619)
> at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1303)
> at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1170)
> at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1165)
> at 
> org.apache.hive.service.cli.operation.SQLOperation.runQuery(SQLOperation.java:197)
> at 
> org.apache.hive.service.cli.operation.SQLOperation.access$300(SQLOperation.java:76)
> at 
> org.apache.hive.service.cli.operation.SQLOperation$2$1.run(SQLOperation.java:255)
> 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:1869)
> at 
> org.apache.hive.service.cli.operation.SQLOperation$2.run(SQLOperation.java:266)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 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)
> 2018-12-26 12:15:22,234 INFO  [HiveServer2-Background-Pool: Thread-339]: 
> log.PerfLogger (PerfLogger.java:PerfLogEnd(177)) -  method=PostHook.org.apache.atlas.hive.hook.HiveHook start=154582659 
> end=1545826522234 duration=5 from=org.apache.hadoop.hive.ql.Driver>
> {code}
> The problem looks to be appearing as result being stored for UDF in temporary 
> table _dummy_database._dummy_table and while creating a Lineage the process 
> fails.
> Steps to reproduce is running below SQL.
> {code}
> create table masktest11 as select stack(2, "eddie", "111", "ravi", "222") as 
> (name, ssn);
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-3033) ATLAS Hive hook fails for CTAS query involving UDFs

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-3033:

Fix Version/s: 2.0.0
   1.2.0

> ATLAS Hive hook fails for CTAS query involving UDFs
> ---
>
> Key: ATLAS-3033
> URL: https://issues.apache.org/jira/browse/ATLAS-3033
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8.3
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 0.8.4, 1.2.0, 2.0.0
>
> Attachments: ATLAS-3033-branch-2.0.patch, ATLAS-3033-master.patch, 
> ATLAS-3033.patch
>
>
> ATLAS Hive Hook fails to notify for CTAS queries involving UDFs, Hook fails 
> with the exception as below
> {code}
> org.apache.hadoop.hive.ql.metadata.InvalidTableException: Table not found 
> _dummy_table
> {code}
> complete stack trace.
> {code}
> 2018-12-26 12:15:22,234 ERROR [HiveServer2-Background-Pool: Thread-339]: 
> metadata.Hive (Hive.java:getTable(1220)) - Table _dummy_table not found: 
> _dummy_database._
> dummy_table table not found
> 2018-12-26 12:15:22,234 ERROR [HiveServer2-Background-Pool: Thread-339]: 
> hook.HiveHook (HiveHook.java:run(160)) - HiveHook.run(): failed to process 
> operation CREAT
> ETABLE_AS_SELECT
> org.apache.hadoop.hive.ql.metadata.InvalidTableException: Table not found 
> _dummy_table
> at org.apache.hadoop.hive.ql.metadata.Hive.getTable(Hive.java:1221)
> at org.apache.hadoop.hive.ql.metadata.Hive.getTable(Hive.java:1191)
> at 
> org.apache.atlas.hive.hook.events.BaseHiveEvent.toAtlasEntity(BaseHiveEvent.java:225)
> at 
> org.apache.atlas.hive.hook.events.BaseHiveEvent.getInputOutputEntity(BaseHiveEvent.java:203)
> at 
> org.apache.atlas.hive.hook.events.CreateHiveProcess.getEntities(CreateHiveProcess.java:84)
> at 
> org.apache.atlas.hive.hook.events.CreateHiveProcess.getNotificationMessages(CreateHiveProcess.java:59)
> at org.apache.atlas.hive.hook.HiveHook.run(HiveHook.java:157)
> at org.apache.atlas.hive.hook.HiveHook.run(HiveHook.java:52)
> at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1619)
> at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1303)
> at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1170)
> at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1165)
> at 
> org.apache.hive.service.cli.operation.SQLOperation.runQuery(SQLOperation.java:197)
> at 
> org.apache.hive.service.cli.operation.SQLOperation.access$300(SQLOperation.java:76)
> at 
> org.apache.hive.service.cli.operation.SQLOperation$2$1.run(SQLOperation.java:255)
> 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:1869)
> at 
> org.apache.hive.service.cli.operation.SQLOperation$2.run(SQLOperation.java:266)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 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)
> 2018-12-26 12:15:22,234 INFO  [HiveServer2-Background-Pool: Thread-339]: 
> log.PerfLogger (PerfLogger.java:PerfLogEnd(177)) -  method=PostHook.org.apache.atlas.hive.hook.HiveHook start=154582659 
> end=1545826522234 duration=5 from=org.apache.hadoop.hive.ql.Driver>
> {code}
> The problem looks to be appearing as result being stored for UDF in temporary 
> table _dummy_database._dummy_table and while creating a Lineage the process 
> fails.
> Steps to reproduce is running below SQL.
> {code}
> create table masktest11 as select stack(2, "eddie", "111", "ravi", "222") as 
> (name, ssn);
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-3033) ATLAS Hive hook fails for CTAS query involving UDFs

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-3033:

Attachment: ATLAS-3033-master.patch

> ATLAS Hive hook fails for CTAS query involving UDFs
> ---
>
> Key: ATLAS-3033
> URL: https://issues.apache.org/jira/browse/ATLAS-3033
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8.3
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 0.8.4
>
> Attachments: ATLAS-3033-master.patch, ATLAS-3033.patch
>
>
> ATLAS Hive Hook fails to notify for CTAS queries involving UDFs, Hook fails 
> with the exception as below
> {code}
> org.apache.hadoop.hive.ql.metadata.InvalidTableException: Table not found 
> _dummy_table
> {code}
> complete stack trace.
> {code}
> 2018-12-26 12:15:22,234 ERROR [HiveServer2-Background-Pool: Thread-339]: 
> metadata.Hive (Hive.java:getTable(1220)) - Table _dummy_table not found: 
> _dummy_database._
> dummy_table table not found
> 2018-12-26 12:15:22,234 ERROR [HiveServer2-Background-Pool: Thread-339]: 
> hook.HiveHook (HiveHook.java:run(160)) - HiveHook.run(): failed to process 
> operation CREAT
> ETABLE_AS_SELECT
> org.apache.hadoop.hive.ql.metadata.InvalidTableException: Table not found 
> _dummy_table
> at org.apache.hadoop.hive.ql.metadata.Hive.getTable(Hive.java:1221)
> at org.apache.hadoop.hive.ql.metadata.Hive.getTable(Hive.java:1191)
> at 
> org.apache.atlas.hive.hook.events.BaseHiveEvent.toAtlasEntity(BaseHiveEvent.java:225)
> at 
> org.apache.atlas.hive.hook.events.BaseHiveEvent.getInputOutputEntity(BaseHiveEvent.java:203)
> at 
> org.apache.atlas.hive.hook.events.CreateHiveProcess.getEntities(CreateHiveProcess.java:84)
> at 
> org.apache.atlas.hive.hook.events.CreateHiveProcess.getNotificationMessages(CreateHiveProcess.java:59)
> at org.apache.atlas.hive.hook.HiveHook.run(HiveHook.java:157)
> at org.apache.atlas.hive.hook.HiveHook.run(HiveHook.java:52)
> at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1619)
> at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1303)
> at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1170)
> at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1165)
> at 
> org.apache.hive.service.cli.operation.SQLOperation.runQuery(SQLOperation.java:197)
> at 
> org.apache.hive.service.cli.operation.SQLOperation.access$300(SQLOperation.java:76)
> at 
> org.apache.hive.service.cli.operation.SQLOperation$2$1.run(SQLOperation.java:255)
> 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:1869)
> at 
> org.apache.hive.service.cli.operation.SQLOperation$2.run(SQLOperation.java:266)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 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)
> 2018-12-26 12:15:22,234 INFO  [HiveServer2-Background-Pool: Thread-339]: 
> log.PerfLogger (PerfLogger.java:PerfLogEnd(177)) -  method=PostHook.org.apache.atlas.hive.hook.HiveHook start=154582659 
> end=1545826522234 duration=5 from=org.apache.hadoop.hive.ql.Driver>
> {code}
> The problem looks to be appearing as result being stored for UDF in temporary 
> table _dummy_database._dummy_table and while creating a Lineage the process 
> fails.
> Steps to reproduce is running below SQL.
> {code}
> create table masktest11 as select stack(2, "eddie", "111", "ravi", "222") as 
> (name, ssn);
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-3167) Exception while starting Atlas with Cassandra

[Madhan Neethiraj (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827740#comment-16827740
 ] 

Madhan Neethiraj commented on ATLAS-3167:
-

If no specific profile is provides, the build generates for 
"external-hbase-solr" - see the following in distro/pom.xml:

{code}

external-hbase-solr

true


{code}

I suggest to add necessary profiles for Cassandra - like 
"external-cassandra-solr", and override guava version for these profiles.

> Exception while starting Atlas with Cassandra
> -
>
> Key: ATLAS-3167
> URL: https://issues.apache.org/jira/browse/ATLAS-3167
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Chaitra Rao
>Assignee: Madhan Neethiraj
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: ATLAS-3167.patch
>
>
> When I try to start Atlas (2.0.0-SNAPSHOT), I get the following error - 
> ==
> 019-04-23 19:11:37,094 ERROR - [MemtableFlushWriter:1:] ~ Exception in thread 
> Thread[MemtableFlushWriter:1,5,main] (CassandraDaemon$1:223)
> java.lang.NoSuchMethodError: 
> com.google.common.util.concurrent.MoreExecutors.sameThreadExecutor()Lcom/google/common/util/concurrent/ListeningExecutorService;
>         at 
> org.apache.cassandra.db.ColumnFamilyStore$Flush.run(ColumnFamilyStore.java:1127)
>         at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>         at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>         at java.lang.Thread.run(Thread.java:748)
>  
> ==
> Guava jar - com.google.guava:guava:jar:25.1 is used throughout. Do not see 
> any conflicting guava jars, except for com.google.guava:guava:jar:12.0.1 from 
> kafka-bridge pom. Excluding this did not work as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (ATLAS-3167) Exception while starting Atlas with Cassandra

[Madhan Neethiraj (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827740#comment-16827740
 ] 

Madhan Neethiraj edited comment on ATLAS-3167 at 4/27/19 8:17 PM:
--

If no specific profile is provided, the build generates for 
"external-hbase-solr" - see the following in distro/pom.xml:

{code}

external-hbase-solr

true


{code}

I suggest to add necessary profiles for Cassandra - like 
"external-cassandra-solr", and override guava version for these profiles.


was (Author: madhan.neethiraj):
If no specific profile is provides, the build generates for 
"external-hbase-solr" - see the following in distro/pom.xml:

{code}

external-hbase-solr

true


{code}

I suggest to add necessary profiles for Cassandra - like 
"external-cassandra-solr", and override guava version for these profiles.

> Exception while starting Atlas with Cassandra
> -
>
> Key: ATLAS-3167
> URL: https://issues.apache.org/jira/browse/ATLAS-3167
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Chaitra Rao
>Assignee: Madhan Neethiraj
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: ATLAS-3167.patch
>
>
> When I try to start Atlas (2.0.0-SNAPSHOT), I get the following error - 
> ==
> 019-04-23 19:11:37,094 ERROR - [MemtableFlushWriter:1:] ~ Exception in thread 
> Thread[MemtableFlushWriter:1,5,main] (CassandraDaemon$1:223)
> java.lang.NoSuchMethodError: 
> com.google.common.util.concurrent.MoreExecutors.sameThreadExecutor()Lcom/google/common/util/concurrent/ListeningExecutorService;
>         at 
> org.apache.cassandra.db.ColumnFamilyStore$Flush.run(ColumnFamilyStore.java:1127)
>         at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>         at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>         at java.lang.Thread.run(Thread.java:748)
>  
> ==
> Guava jar - com.google.guava:guava:jar:25.1 is used throughout. Do not see 
> any conflicting guava jars, except for com.google.guava:guava:jar:12.0.1 from 
> kafka-bridge pom. Excluding this did not work as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-3167) Exception while starting Atlas with Cassandra

[Madhan Neethiraj (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827736#comment-16827736
 ] 

Madhan Neethiraj commented on ATLAS-3167:
-

[~vasanthkumar] - 'embedded-cassandra-solr' is the only profile that uses 
Cassandra backend; hence guava version override is done only for this profile.

> Exception while starting Atlas with Cassandra
> -
>
> Key: ATLAS-3167
> URL: https://issues.apache.org/jira/browse/ATLAS-3167
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Chaitra Rao
>Assignee: Madhan Neethiraj
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: ATLAS-3167.patch
>
>
> When I try to start Atlas (2.0.0-SNAPSHOT), I get the following error - 
> ==
> 019-04-23 19:11:37,094 ERROR - [MemtableFlushWriter:1:] ~ Exception in thread 
> Thread[MemtableFlushWriter:1,5,main] (CassandraDaemon$1:223)
> java.lang.NoSuchMethodError: 
> com.google.common.util.concurrent.MoreExecutors.sameThreadExecutor()Lcom/google/common/util/concurrent/ListeningExecutorService;
>         at 
> org.apache.cassandra.db.ColumnFamilyStore$Flush.run(ColumnFamilyStore.java:1127)
>         at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>         at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>         at java.lang.Thread.run(Thread.java:748)
>  
> ==
> Guava jar - com.google.guava:guava:jar:25.1 is used throughout. Do not see 
> any conflicting guava jars, except for com.google.guava:guava:jar:12.0.1 from 
> kafka-bridge pom. Excluding this did not work as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-3167) Exception while starting Atlas with Cassandra

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-3167:

Fix Version/s: (was: trunk)

> Exception while starting Atlas with Cassandra
> -
>
> Key: ATLAS-3167
> URL: https://issues.apache.org/jira/browse/ATLAS-3167
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Chaitra Rao
>Assignee: Madhan Neethiraj
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: ATLAS-3167.patch
>
>
> When I try to start Atlas (2.0.0-SNAPSHOT), I get the following error - 
> ==
> 019-04-23 19:11:37,094 ERROR - [MemtableFlushWriter:1:] ~ Exception in thread 
> Thread[MemtableFlushWriter:1,5,main] (CassandraDaemon$1:223)
> java.lang.NoSuchMethodError: 
> com.google.common.util.concurrent.MoreExecutors.sameThreadExecutor()Lcom/google/common/util/concurrent/ListeningExecutorService;
>         at 
> org.apache.cassandra.db.ColumnFamilyStore$Flush.run(ColumnFamilyStore.java:1127)
>         at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>         at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>         at java.lang.Thread.run(Thread.java:748)
>  
> ==
> Guava jar - com.google.guava:guava:jar:25.1 is used throughout. Do not see 
> any conflicting guava jars, except for com.google.guava:guava:jar:12.0.1 from 
> kafka-bridge pom. Excluding this did not work as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (ATLAS-3167) Exception while starting Atlas with Cassandra

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj reassigned ATLAS-3167:
---

  Assignee: Madhan Neethiraj
Attachment: ATLAS-3167.patch

- verified that the patch addresses the failure while using Cassandra, by 
building and running with 'embedded-cassandra-solr' profile

> Exception while starting Atlas with Cassandra
> -
>
> Key: ATLAS-3167
> URL: https://issues.apache.org/jira/browse/ATLAS-3167
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Chaitra Rao
>Assignee: Madhan Neethiraj
>Priority: Critical
> Fix For: 2.0.0, trunk
>
> Attachments: ATLAS-3167.patch
>
>
> When I try to start Atlas (2.0.0-SNAPSHOT), I get the following error - 
> ==
> 019-04-23 19:11:37,094 ERROR - [MemtableFlushWriter:1:] ~ Exception in thread 
> Thread[MemtableFlushWriter:1,5,main] (CassandraDaemon$1:223)
> java.lang.NoSuchMethodError: 
> com.google.common.util.concurrent.MoreExecutors.sameThreadExecutor()Lcom/google/common/util/concurrent/ListeningExecutorService;
>         at 
> org.apache.cassandra.db.ColumnFamilyStore$Flush.run(ColumnFamilyStore.java:1127)
>         at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>         at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>         at java.lang.Thread.run(Thread.java:748)
>  
> ==
> Guava jar - com.google.guava:guava:jar:25.1 is used throughout. Do not see 
> any conflicting guava jars, except for com.google.guava:guava:jar:12.0.1 from 
> kafka-bridge pom. Excluding this did not work as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ATLAS-3160) AtlasRelationshipDef throws useless Atlas exceptions in costructors

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj resolved ATLAS-3160.
-
   Resolution: Fixed
Fix Version/s: 1.2.0

[~Zep] - thanks for the patch.

> AtlasRelationshipDef throws useless Atlas exceptions in costructors
> ---
>
> Key: ATLAS-3160
> URL: https://issues.apache.org/jira/browse/ATLAS-3160
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Affects Versions: 2.0.0
> Environment: All OS
>Reporter: Diego Marino Monetti
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
>
> This exception is raised by the default constructor and by another one but 
> none of these two constructors call functions that can give rise to these 
> exceptions. The  problem is not blocking but it is annoying if someone wants 
> to subclass this class.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (ATLAS-3172) Atlas Hive Hook lack of Jackson dependency

[Madhan Neethiraj (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827665#comment-16827665
 ] 

Madhan Neethiraj edited comment on ATLAS-3172 at 4/27/19 4:59 PM:
--

[~theHarpers] - hook-bin/import-hive.sh picks up Jackson libraries from 
hook/hive/atlas-hive-plugin-impl directory i.e. it adds all the libraries 
present under hook/hive/atlas-hive-plugin-impl/ in its CLASSPATH. I verified 
this by successfully completing import with command hook-bin/import-hive.sh. 
Can you please verify that hook/hive/atlas-hive-plugin-impl directory is 
present in your environment? If it is not, please copy this directory as well 
and run import-hive.sh.

If import-hive.sh fails even when hook/hive/atlas-hive-plugin-impl directory is 
present, please add details of the errors/logs, to help troubleshoot the issue.


was (Author: madhan.neethiraj):
[~theHarpers] - hook-bin/import-hive.sh picks up Jackson libraries from 
hook/hive/atlas-hive-plugin-impl directory i.e. it adds all the libraries 
present under hook/hive/atlas-hive-plugin-impl/ in its CLASSPATH. I verified 
this by successfully completing import with command hook-bin/import-hive.sh. 
Can you please verify that in hook/hive/atlas-hive-plugin-impl directory is 
present in your environment? If it is not, please copy this directory as well 
and run import-hive.sh.

> Atlas Hive Hook lack of Jackson dependency
> --
>
> Key: ATLAS-3172
> URL: https://issues.apache.org/jira/browse/ATLAS-3172
> Project: Atlas
>  Issue Type: Bug
>Reporter: jianxiong zhao
>Priority: Major
>
> After copying Hive Hook to ${ATLAS_HOME}, executing `hook-bin/import-hive.sh` 
> always fails with lack of Jackson.XXX dependencies



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-3172) Atlas Hive Hook lack of Jackson dependency

[Madhan Neethiraj (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827665#comment-16827665
 ] 

Madhan Neethiraj commented on ATLAS-3172:
-

[~theHarpers] - hook-bin/import-hive.sh picks up Jackson libraries from 
hook/hive/atlas-hive-plugin-impl directory i.e. it adds all the libraries 
present under hook/hive/atlas-hive-plugin-impl/ in its CLASSPATH. I verified 
this by successfully completing import with command hook-bin/import-hive.sh. 
Can you please verify that in hook/hive/atlas-hive-plugin-impl directory is 
present in your environment? If it is not, please copy this directory as well 
and run import-hive.sh.

> Atlas Hive Hook lack of Jackson dependency
> --
>
> Key: ATLAS-3172
> URL: https://issues.apache.org/jira/browse/ATLAS-3172
> Project: Atlas
>  Issue Type: Bug
>Reporter: jianxiong zhao
>Priority: Major
>
> After copying Hive Hook to ${ATLAS_HOME}, executing `hook-bin/import-hive.sh` 
> always fails with lack of Jackson.XXX dependencies



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-3081) Expose Gremlin Search API

[Madhan Neethiraj (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826409#comment-16826409
 ] 

Madhan Neethiraj commented on ATLAS-3081:
-

[~bolke] - enhancing DSL is the approach we, the Atlas community, should 
discuss (instead of simply exposing graph level access). I would suggest to 
file JIRAs with details of the enhancements; and better yet, contribute patches 
with the enhancements.

> Expose Gremlin Search API
> -
>
> Key: ATLAS-3081
> URL: https://issues.apache.org/jira/browse/ATLAS-3081
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Ayush Nigam
>Assignee: Ayush Nigam
>Priority: Minor
> Attachments: ATLAS_3081.patch
>
>
> Expose Gremlin Search API to solve more complex usecases.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-3081) Expose Gremlin Search API

[Madhan Neethiraj (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826223#comment-16826223
 ] 

Madhan Neethiraj commented on ATLAS-3081:
-

[~bolke] - (repeating my earlier comment) most applications that use RDBMS as 
backend store will not expose schema details to its users, and will not allow 
execution of arbitrary queries from its users. There are a lot of good reasons 
for taking such a hard stance; and all of them apply for Atlas as well. 
Specifically I would like to call out few points:
- Atlas has strong authorization model, which enable restricting users from 
accessing/updating entity data - based on 
entity-type/entity-id/entity-classifications/.. Allowing direct access to 
Gremlin will bye-pass such authorization controls
- Using Gremlin, it is possible update the graph status (create/update/delete 
vertices/properties) - which again can violate authorization controls in place, 
in addition will result in change notifications from Atlas server to be skipped
- Details of vertex and edge (labels, property-names, ..) are internal to Atlas 
and can change across versions. Users should not write applications that depend 
on internal implementation details

With DSL approach, Atlas has complete control - on kind of operations are 
allowed, on what entities, for what users; will ensure that undesired 
operations are kept out. I would strongly suggest enhancements to DSL.

Once again, I would strongly suggest to look at the analogy of applications 
allowing arbitrary user-given SQL on its schema.

> Expose Gremlin Search API
> -
>
> Key: ATLAS-3081
> URL: https://issues.apache.org/jira/browse/ATLAS-3081
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Ayush Nigam
>Assignee: Ayush Nigam
>Priority: Minor
> Attachments: ATLAS_3081.patch
>
>
> Expose Gremlin Search API to solve more complex usecases.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ATLAS-3165) Re-enable gremlin search

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj resolved ATLAS-3165.
-
Resolution: Duplicate

[~bolke] - this is tracked via ATLAS-3081. In short: exposing "gremlin" is not 
a supportable approach, as the details of vertex properties, edge names are 
implementation details which users of Atlas should not rely on.

> Re-enable gremlin search
> 
>
> Key: ATLAS-3165
> URL: https://issues.apache.org/jira/browse/ATLAS-3165
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Bolke de Bruin
>Priority: Major
>
> .We are integrating Atlas with Lyft’s Amundsen 
> ([https://github.com/lyft/amundsenfrontendlibrary)] and we are finding that 
> the standard search DSL is limited in such a way that it does not support 
> simple useful queries like
> ```Column where name like '*amount*' groupby(table) select count()```
> Or
> ```Column where name like '*amount*' select count(table)```
>  
> This can be done by using a gremlin query but the interface was removed in 
> ATLAS-2229 for some reason. We think it should be reinstated.
> Limiting access to this interface could be done by Ranger policies.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ATLAS-3151) incorrect return type for AtlasClientV2.getRelationshipByGuid()

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj resolved ATLAS-3151.
-
   Resolution: Fixed
Fix Version/s: 2.0.0
   1.2.0

> incorrect return type for AtlasClientV2.getRelationshipByGuid()
> ---
>
> Key: ATLAS-3151
> URL: https://issues.apache.org/jira/browse/ATLAS-3151
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Affects Versions: 1.1.0, 2.0.0
>Reporter: Madhan Neethiraj
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
>
> Reported by jxzhao via [https://github.com/apache/atlas/pull/42.]
> AtlasClientV2.getRelationshipByGuid() method returns AtlasRelationship; 
> however the REST API from Atlas server returns AtlasRelationshipWithExtInfo. 
> The client should be updated to match the server API.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ATLAS-3147) Atlas server should log stats/metrics periodically in log file

[Madhan Neethiraj (JIRA)]

Madhan Neethiraj created ATLAS-3147:
---

 Summary: Atlas server should log stats/metrics periodically in log 
file
 Key: ATLAS-3147
 URL: https://issues.apache.org/jira/browse/ATLAS-3147
 Project: Atlas
  Issue Type: Improvement
  Components:  atlas-core
Reporter: Madhan Neethiraj
Assignee: Madhan Neethiraj


With enhancements introduced in ATLAS-3071, Atlas collects a bunch of metrics - 
especially on notification processing. Having these metrics periodically (every 
hour?) logged in Atlas server log files will be helpful for troubleshooting and 
other analysis.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)