[jira] [Updated] (ATLAS-3832) Atlas Hook not consuming from Azure Event Hub

[Kenny (Jira)]

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

Kenny updated ATLAS-3832:
-
Description: 
I have followed the instructions in the article to configure Atlas in local 
mode to point to Azure Event Hub: 
[https://medium.com/@reenugrewal/data-lineage-tracking-using-spline-on-atlas-via-event-hub-6816be0fd5c7]

I can see incoming message being sent to the atlas_hook topic, but Atlas is not 
consuming these messages. The application.log shows no errors. I've attached 
the application.log that shows successful start up of the consumer hook.

I'm not sure why the topic isn't being consumed by atlas and have no idea where 
I should be looking to troubleshoot.

  was:
I have followed the instructions in the article to configure Atlas in local 
mode to point to Azure Event Hub: 
[https://medium.com/@reenugrewal/data-lineage-tracking-using-spline-on-atlas-via-event-hub-6816be0fd5c7]

I can see a message being sent to the atlas_hook topic, but Atlas is not 
consuming these messages. The application.log shows no errors. I've attached 
the application.log that shows successful start up of the consumer hook.

I'm not sure why the topic isn't being consumed by atlas and have no idea where 
I should be looking to troubleshoot.


> Atlas Hook not consuming from Azure Event Hub
> -
>
> Key: ATLAS-3832
> URL: https://issues.apache.org/jira/browse/ATLAS-3832
> Project: Atlas
>  Issue Type: Bug
>  Components: kafka-integration
>Affects Versions: 2.0.0
>Reporter: Kenny
>Priority: Major
>  Labels: documentation, newbie
> Attachments: application.log
>
>
> I have followed the instructions in the article to configure Atlas in local 
> mode to point to Azure Event Hub: 
> [https://medium.com/@reenugrewal/data-lineage-tracking-using-spline-on-atlas-via-event-hub-6816be0fd5c7]
> I can see incoming message being sent to the atlas_hook topic, but Atlas is 
> not consuming these messages. The application.log shows no errors. I've 
> attached the application.log that shows successful start up of the consumer 
> hook.
> I'm not sure why the topic isn't being consumed by atlas and have no idea 
> where I should be looking to troubleshoot.



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

[jira] [Updated] (ATLAS-3832) Atlas Hook not consuming from Azure Event Hub

[Kenny (Jira)]

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

Kenny updated ATLAS-3832:
-
Description: 
I have followed the instructions in the article to configure Atlas in local 
mode to point to Azure Event Hub: 
[https://medium.com/@reenugrewal/data-lineage-tracking-using-spline-on-atlas-via-event-hub-6816be0fd5c7]

I can see incoming message being sent to the atlas_hook topic, but Atlas is not 
consuming these messages. The application.log shows no errors. I've attached 
the application.log that shows successful start up of the consumer hook.

I'm not sure why the topic isn't being consumed by atlas and have no idea where 
I should be looking to troubleshoot.

I spun up a standalone zookeeper but according to the logs the 
atlas.kafka.zookeeper.connect isn't being used and there are no errors being 
thrown about it so I don't think that is a problem.

Environment setup:
 * atlas 2.0.0-rc2
 * spline 0.3.6 jars
 * databricks runtime 5.5. LTS

  was:
I have followed the instructions in the article to configure Atlas in local 
mode to point to Azure Event Hub: 
[https://medium.com/@reenugrewal/data-lineage-tracking-using-spline-on-atlas-via-event-hub-6816be0fd5c7]

I can see incoming message being sent to the atlas_hook topic, but Atlas is not 
consuming these messages. The application.log shows no errors. I've attached 
the application.log that shows successful start up of the consumer hook.

I'm not sure why the topic isn't being consumed by atlas and have no idea where 
I should be looking to troubleshoot.


> Atlas Hook not consuming from Azure Event Hub
> -
>
> Key: ATLAS-3832
> URL: https://issues.apache.org/jira/browse/ATLAS-3832
> Project: Atlas
>  Issue Type: Bug
>  Components: kafka-integration
>Affects Versions: 2.0.0
>Reporter: Kenny
>Priority: Major
>  Labels: documentation, newbie
> Attachments: application.log
>
>
> I have followed the instructions in the article to configure Atlas in local 
> mode to point to Azure Event Hub: 
> [https://medium.com/@reenugrewal/data-lineage-tracking-using-spline-on-atlas-via-event-hub-6816be0fd5c7]
> I can see incoming message being sent to the atlas_hook topic, but Atlas is 
> not consuming these messages. The application.log shows no errors. I've 
> attached the application.log that shows successful start up of the consumer 
> hook.
> I'm not sure why the topic isn't being consumed by atlas and have no idea 
> where I should be looking to troubleshoot.
> I spun up a standalone zookeeper but according to the logs the 
> atlas.kafka.zookeeper.connect isn't being used and there are no errors being 
> thrown about it so I don't think that is a problem.
> Environment setup:
>  * atlas 2.0.0-rc2
>  * spline 0.3.6 jars
>  * databricks runtime 5.5. LTS



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

[jira] [Created] (ATLAS-3832) Atlas Hook not consuming from Azure Event Hub

[Kenny (Jira)]

Kenny created ATLAS-3832:


 Summary: Atlas Hook not consuming from Azure Event Hub
 Key: ATLAS-3832
 URL: https://issues.apache.org/jira/browse/ATLAS-3832
 Project: Atlas
  Issue Type: Bug
  Components: kafka-integration
Affects Versions: 2.0.0
Reporter: Kenny
 Attachments: application.log

I have followed the instructions in the article to configure Atlas in local 
mode to point to Azure Event Hub: 
[https://medium.com/@reenugrewal/data-lineage-tracking-using-spline-on-atlas-via-event-hub-6816be0fd5c7]

I can see a message being sent to the atlas_hook topic, but Atlas is not 
consuming these messages. The application.log shows no errors. I've attached 
the application.log that shows successful start up of the consumer hook.

I'm not sure why the topic isn't being consumed by atlas and have no idea where 
I should be looking to troubleshoot.



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

[jira] [Updated] (ATLAS-3832) Atlas not consuming from atlas_hook topic on Azure Event Hub

[Kenny (Jira)]

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

Kenny updated ATLAS-3832:
-
Summary: Atlas not consuming from atlas_hook topic on Azure Event Hub  
(was: Atlas Hook kafka consumer not consuming from Azure Event Hub)

> Atlas not consuming from atlas_hook topic on Azure Event Hub
> 
>
> Key: ATLAS-3832
> URL: https://issues.apache.org/jira/browse/ATLAS-3832
> Project: Atlas
>  Issue Type: Bug
>  Components: kafka-integration
>Affects Versions: 2.0.0
>Reporter: Kenny
>Priority: Major
>  Labels: documentation, newbie
> Attachments: application.log
>
>
> I have followed the instructions in the article to configure Atlas (local 
> deployment) to point to Azure Event Hub: 
> [https://medium.com/@reenugrewal/data-lineage-tracking-using-spline-on-atlas-via-event-hub-6816be0fd5c7]
> I can see incoming message being sent to the atlas_hook topic, but Atlas is 
> not consuming these messages. The application.log shows no errors. I've 
> attached the application.log that shows successful start up of the consumer 
> hook.
> I'm not sure why the topic isn't being consumed by atlas and have no idea 
> where I should be looking to troubleshoot.
> I spun up a standalone zookeeper but according to the logs the 
> atlas.kafka.zookeeper.connect isn't being used and there are no errors being 
> thrown about it so I don't think that is a problem.
> Environment setup:
>  * atlas 2.0.0-rc2 with embedded HBase and Solr
>  ** CentOS 7 with latest VirtualBox
>  * databricks runtime 5.5. LTS
>  ** spline 0.3.6 jars



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

[jira] [Updated] (ATLAS-3832) Atlas Hook kafka consumer not consuming from Azure Event Hub

[Kenny (Jira)]

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

Kenny updated ATLAS-3832:
-
Summary: Atlas Hook kafka consumer not consuming from Azure Event Hub  
(was: Atlas Hook not consuming from Azure Event Hub)

> Atlas Hook kafka consumer not consuming from Azure Event Hub
> 
>
> Key: ATLAS-3832
> URL: https://issues.apache.org/jira/browse/ATLAS-3832
> Project: Atlas
>  Issue Type: Bug
>  Components: kafka-integration
>Affects Versions: 2.0.0
>Reporter: Kenny
>Priority: Major
>  Labels: documentation, newbie
> Attachments: application.log
>
>
> I have followed the instructions in the article to configure Atlas (local 
> deployment) to point to Azure Event Hub: 
> [https://medium.com/@reenugrewal/data-lineage-tracking-using-spline-on-atlas-via-event-hub-6816be0fd5c7]
> I can see incoming message being sent to the atlas_hook topic, but Atlas is 
> not consuming these messages. The application.log shows no errors. I've 
> attached the application.log that shows successful start up of the consumer 
> hook.
> I'm not sure why the topic isn't being consumed by atlas and have no idea 
> where I should be looking to troubleshoot.
> I spun up a standalone zookeeper but according to the logs the 
> atlas.kafka.zookeeper.connect isn't being used and there are no errors being 
> thrown about it so I don't think that is a problem.
> Environment setup:
>  * atlas 2.0.0-rc2 with embedded HBase and Solr
>  ** CentOS 7 with latest VirtualBox
>  * databricks runtime 5.5. LTS
>  ** spline 0.3.6 jars



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

[jira] [Updated] (ATLAS-3832) Atlas Hook not consuming from Azure Event Hub

[Kenny (Jira)]

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

Kenny updated ATLAS-3832:
-
Description: 
I have followed the instructions in the article to configure Atlas (local 
deployment) to point to Azure Event Hub: 
[https://medium.com/@reenugrewal/data-lineage-tracking-using-spline-on-atlas-via-event-hub-6816be0fd5c7]

I can see incoming message being sent to the atlas_hook topic, but Atlas is not 
consuming these messages. The application.log shows no errors. I've attached 
the application.log that shows successful start up of the consumer hook.

I'm not sure why the topic isn't being consumed by atlas and have no idea where 
I should be looking to troubleshoot.

I spun up a standalone zookeeper but according to the logs the 
atlas.kafka.zookeeper.connect isn't being used and there are no errors being 
thrown about it so I don't think that is a problem.

Environment setup:
 * atlas 2.0.0-rc2 with embedded HBase and Solr
 ** CentOS 7 with latest VirtualBox
 * databricks runtime 5.5. LTS
 ** spline 0.3.6 jars

  was:
I have followed the instructions in the article to configure Atlas in local 
mode to point to Azure Event Hub: 
[https://medium.com/@reenugrewal/data-lineage-tracking-using-spline-on-atlas-via-event-hub-6816be0fd5c7]

I can see incoming message being sent to the atlas_hook topic, but Atlas is not 
consuming these messages. The application.log shows no errors. I've attached 
the application.log that shows successful start up of the consumer hook.

I'm not sure why the topic isn't being consumed by atlas and have no idea where 
I should be looking to troubleshoot.

I spun up a standalone zookeeper but according to the logs the 
atlas.kafka.zookeeper.connect isn't being used and there are no errors being 
thrown about it so I don't think that is a problem.

Environment setup:
 * atlas 2.0.0-rc2
 * spline 0.3.6 jars
 * databricks runtime 5.5. LTS


> Atlas Hook not consuming from Azure Event Hub
> -
>
> Key: ATLAS-3832
> URL: https://issues.apache.org/jira/browse/ATLAS-3832
> Project: Atlas
>  Issue Type: Bug
>  Components: kafka-integration
>Affects Versions: 2.0.0
>Reporter: Kenny
>Priority: Major
>  Labels: documentation, newbie
> Attachments: application.log
>
>
> I have followed the instructions in the article to configure Atlas (local 
> deployment) to point to Azure Event Hub: 
> [https://medium.com/@reenugrewal/data-lineage-tracking-using-spline-on-atlas-via-event-hub-6816be0fd5c7]
> I can see incoming message being sent to the atlas_hook topic, but Atlas is 
> not consuming these messages. The application.log shows no errors. I've 
> attached the application.log that shows successful start up of the consumer 
> hook.
> I'm not sure why the topic isn't being consumed by atlas and have no idea 
> where I should be looking to troubleshoot.
> I spun up a standalone zookeeper but according to the logs the 
> atlas.kafka.zookeeper.connect isn't being used and there are no errors being 
> thrown about it so I don't think that is a problem.
> Environment setup:
>  * atlas 2.0.0-rc2 with embedded HBase and Solr
>  ** CentOS 7 with latest VirtualBox
>  * databricks runtime 5.5. LTS
>  ** spline 0.3.6 jars



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

[jira] [Updated] (ATLAS-3832) Atlas notification consumer hook is not consuming from atlas_hook topic on Azure Event Hub

[Kenny (Jira)]

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

Kenny updated ATLAS-3832:
-
Summary: Atlas notification consumer hook is not consuming from atlas_hook 
topic on Azure Event Hub  (was: Atlas not consuming from atlas_hook topic on 
Azure Event Hub)

> Atlas notification consumer hook is not consuming from atlas_hook topic on 
> Azure Event Hub
> --
>
> Key: ATLAS-3832
> URL: https://issues.apache.org/jira/browse/ATLAS-3832
> Project: Atlas
>  Issue Type: Bug
>  Components: kafka-integration
>Affects Versions: 2.0.0
>Reporter: Kenny
>Priority: Major
>  Labels: documentation, newbie
> Attachments: application.log
>
>
> I have followed the instructions in the article to configure Atlas (local 
> deployment) to point to Azure Event Hub: 
> [https://medium.com/@reenugrewal/data-lineage-tracking-using-spline-on-atlas-via-event-hub-6816be0fd5c7]
> I can see incoming message being sent to the atlas_hook topic, but Atlas is 
> not consuming these messages. The application.log shows no errors. I've 
> attached the application.log that shows successful start up of the 
> notification consumer hook.
> I'm not sure why the topic isn't being consumed by atlas and have no idea 
> where I should be looking to troubleshoot.
> I spun up a standalone zookeeper but according to the logs the 
> atlas.kafka.zookeeper.connect isn't being used and there are no errors being 
> thrown about it so I don't think that is a problem.
> Environment setup:
>  * atlas 2.0.0-rc2 with embedded HBase and Solr
>  ** CentOS 7 with latest VirtualBox
>  * databricks runtime 5.5. LTS
>  ** spline 0.3.6 jars



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

[jira] [Updated] (ATLAS-3832) Atlas not consuming from atlas_hook topic on Azure Event Hub

[Kenny (Jira)]

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

Kenny updated ATLAS-3832:
-
Description: 
I have followed the instructions in the article to configure Atlas (local 
deployment) to point to Azure Event Hub: 
[https://medium.com/@reenugrewal/data-lineage-tracking-using-spline-on-atlas-via-event-hub-6816be0fd5c7]

I can see incoming message being sent to the atlas_hook topic, but Atlas is not 
consuming these messages. The application.log shows no errors. I've attached 
the application.log that shows successful start up of the notification consumer 
hook.

I'm not sure why the topic isn't being consumed by atlas and have no idea where 
I should be looking to troubleshoot.

I spun up a standalone zookeeper but according to the logs the 
atlas.kafka.zookeeper.connect isn't being used and there are no errors being 
thrown about it so I don't think that is a problem.

Environment setup:
 * atlas 2.0.0-rc2 with embedded HBase and Solr
 ** CentOS 7 with latest VirtualBox
 * databricks runtime 5.5. LTS
 ** spline 0.3.6 jars

  was:
I have followed the instructions in the article to configure Atlas (local 
deployment) to point to Azure Event Hub: 
[https://medium.com/@reenugrewal/data-lineage-tracking-using-spline-on-atlas-via-event-hub-6816be0fd5c7]

I can see incoming message being sent to the atlas_hook topic, but Atlas is not 
consuming these messages. The application.log shows no errors. I've attached 
the application.log that shows successful start up of the consumer hook.

I'm not sure why the topic isn't being consumed by atlas and have no idea where 
I should be looking to troubleshoot.

I spun up a standalone zookeeper but according to the logs the 
atlas.kafka.zookeeper.connect isn't being used and there are no errors being 
thrown about it so I don't think that is a problem.

Environment setup:
 * atlas 2.0.0-rc2 with embedded HBase and Solr
 ** CentOS 7 with latest VirtualBox
 * databricks runtime 5.5. LTS
 ** spline 0.3.6 jars


> Atlas not consuming from atlas_hook topic on Azure Event Hub
> 
>
> Key: ATLAS-3832
> URL: https://issues.apache.org/jira/browse/ATLAS-3832
> Project: Atlas
>  Issue Type: Bug
>  Components: kafka-integration
>Affects Versions: 2.0.0
>Reporter: Kenny
>Priority: Major
>  Labels: documentation, newbie
> Attachments: application.log
>
>
> I have followed the instructions in the article to configure Atlas (local 
> deployment) to point to Azure Event Hub: 
> [https://medium.com/@reenugrewal/data-lineage-tracking-using-spline-on-atlas-via-event-hub-6816be0fd5c7]
> I can see incoming message being sent to the atlas_hook topic, but Atlas is 
> not consuming these messages. The application.log shows no errors. I've 
> attached the application.log that shows successful start up of the 
> notification consumer hook.
> I'm not sure why the topic isn't being consumed by atlas and have no idea 
> where I should be looking to troubleshoot.
> I spun up a standalone zookeeper but according to the logs the 
> atlas.kafka.zookeeper.connect isn't being used and there are no errors being 
> thrown about it so I don't think that is a problem.
> Environment setup:
>  * atlas 2.0.0-rc2 with embedded HBase and Solr
>  ** CentOS 7 with latest VirtualBox
>  * databricks runtime 5.5. LTS
>  ** spline 0.3.6 jars



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

Re: Review Request 72566: ATLAS-1798 : Fix Findbugs problems in repository module

[Madhan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/72566/#review220984
---




repository/src/main/java/org/apache/atlas/query/antlr4/AtlasDSLLexer.java
Line 105 (original), 107 (patched)


I strongly suggest to avoid Arrays.copyOf(), since it can cause excessive 
memory usage. Consider ignoring EI_EXPOSE_REP with an entry in 
build-tools/src/main/resources/findbugs-exclude.xml.



repository/src/main/java/org/apache/atlas/repository/impexp/ZipSource.java
Lines 150 (patched)


Instead of hardcoding string "UTF-8", consider using 
StandardCharsets.UTF_8.name()



repository/src/main/java/org/apache/atlas/repository/impexp/ZipSourceDirect.java
Lines 282 (patched)


Instead of hardcoding string "UTF-8", consider using 
StandardCharsets.UTF_8.name()



repository/src/main/java/org/apache/atlas/repository/migration/DataMigrationService.java
Lines 132 (patched)


- verify that 'fs' is not null, before calling fs.close()
- also, consider avodinig a new 'try' (#128) by adding  'finally' for the 
'try' at #122



repository/src/main/java/org/apache/atlas/repository/migration/ZipFileMigrationImporter.java
Lines 139 (patched)


- verify that 'fs' is not null, before calling fs.close()
- also, consider avodinig a new 'try' (#130) by adding  'finally' for the 
'try' at #127



repository/src/main/java/org/apache/atlas/repository/store/bootstrap/AtlasTypeDefStoreInitializer.java
Line 1081 (original), 1080 (patched)


What was the findbug issue reported here? Can you please review if 
String.format() handles '{}' as placeholder for arguments?



repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasClassificationDefStoreV2.java
Lines 308 (patched)


To be consistent with rest of Atlas coding style, use spaces to seprate 
keywords and operations, like:
 if (ret != null) {



repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasStructDefStoreV2.java
Line 627 (original), 623 (patched)


isUnique can be null here, why is not neceessary to handle this case here?



repository/src/main/java/org/apache/atlas/repository/store/graph/v2/bulkimport/pc/EntityConsumer.java
Line 121 (original)


'result' is not used; however, wouldn't removing call to 
entityStoreBulk.createOrUpdateForImportNoCommit() cause no import to be 
performed??


- Madhan Neethiraj


On June 9, 2020, 12:44 p.m., mayank jain wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/72566/
> ---
> 
> (Updated June 9, 2020, 12:44 p.m.)
> 
> 
> Review request for atlas, Jayendra Parab, Madhan Neethiraj, Nixon Rodrigues, 
> and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-1798
> https://issues.apache.org/jira/browse/ATLAS-1798
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Currently Findbugs complaints about some problems (see attachment) in the 
> repository module. They should be fixed to get the code more reliable.
> 
> 
> Diffs
> -
> 
>   repository/src/main/java/org/apache/atlas/GraphTransactionInterceptor.java 
> 57e454a 
>   
> repository/src/main/java/org/apache/atlas/discovery/EntityDiscoveryService.java
>  dd4d1b4 
>   
> repository/src/main/java/org/apache/atlas/discovery/EntitySearchProcessor.java
>  56956e6 
>   
> repository/src/main/java/org/apache/atlas/discovery/SearchAggregatorImpl.java 
> e8f7dbc 
>   repository/src/main/java/org/apache/atlas/discovery/SearchProcessor.java 
> 804c694 
>   repository/src/main/java/org/apache/atlas/glossary/GlossaryService.java 
> d630f66 
>   repository/src/main/java/org/apache/atlas/glossary/GlossaryTermUtils.java 
> 2c84ec7 
>   repository/src/main/java/org/apache/atlas/glossary/GlossaryUtils.java 
> 2a2cebb 
>   repository/src/main/java/org/apache/atlas/query/AtlasDSL.java b8a744b 
>   repository/src/main/java/org/apache/atlas/query/GremlinQueryComposer.java 
> 801e898 
>   repository/src/main/java/org/apache/atlas/query/antlr4/AtlasDSLLexer.java 
> 142b9ca 
>   repository/src/main/java/org/apache/atlas/query/antlr4/AtlasDSLParser.java 
> 6b33edb 
>   
> repository/src/main/java/org/apache/atlas/repository/audit/AbstractStorageBasedAuditRepository.java
>  1aac375 
>   
> 

Re: Review Request 72566: ATLAS-1798 : Fix Findbugs problems in repository module

[mayank jain]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/72566/
---

(Updated June 9, 2020, 12:44 p.m.)


Review request for atlas, Jayendra Parab, Madhan Neethiraj, Nixon Rodrigues, 
and Sarath Subramanian.


Bugs: ATLAS-1798
https://issues.apache.org/jira/browse/ATLAS-1798


Repository: atlas


Description
---

Currently Findbugs complaints about some problems (see attachment) in the 
repository module. They should be fixed to get the code more reliable.


Diffs (updated)
-

  repository/src/main/java/org/apache/atlas/GraphTransactionInterceptor.java 
57e454a 
  
repository/src/main/java/org/apache/atlas/discovery/EntityDiscoveryService.java 
dd4d1b4 
  
repository/src/main/java/org/apache/atlas/discovery/EntitySearchProcessor.java 
56956e6 
  repository/src/main/java/org/apache/atlas/discovery/SearchAggregatorImpl.java 
e8f7dbc 
  repository/src/main/java/org/apache/atlas/discovery/SearchProcessor.java 
804c694 
  repository/src/main/java/org/apache/atlas/glossary/GlossaryService.java 
d630f66 
  repository/src/main/java/org/apache/atlas/glossary/GlossaryTermUtils.java 
2c84ec7 
  repository/src/main/java/org/apache/atlas/glossary/GlossaryUtils.java 2a2cebb 
  repository/src/main/java/org/apache/atlas/query/AtlasDSL.java b8a744b 
  repository/src/main/java/org/apache/atlas/query/GremlinQueryComposer.java 
801e898 
  repository/src/main/java/org/apache/atlas/query/antlr4/AtlasDSLLexer.java 
142b9ca 
  repository/src/main/java/org/apache/atlas/query/antlr4/AtlasDSLParser.java 
6b33edb 
  
repository/src/main/java/org/apache/atlas/repository/audit/AbstractStorageBasedAuditRepository.java
 1aac375 
  
repository/src/main/java/org/apache/atlas/repository/audit/EntityAuditListener.java
 69d373d 
  
repository/src/main/java/org/apache/atlas/repository/audit/EntityAuditListenerV2.java
 79527ac 
  
repository/src/main/java/org/apache/atlas/repository/audit/HBaseBasedAuditRepository.java
 9fca744 
  
repository/src/main/java/org/apache/atlas/repository/converters/AtlasArrayFormatConverter.java
 c335f0a 
  
repository/src/main/java/org/apache/atlas/repository/converters/AtlasInstanceConverter.java
 6fc0c65 
  
repository/src/main/java/org/apache/atlas/repository/converters/AtlasMapFormatConverter.java
 0eacd8e 
  
repository/src/main/java/org/apache/atlas/repository/converters/AtlasStructFormatConverter.java
 ae92b8b 
  
repository/src/main/java/org/apache/atlas/repository/graph/FullTextMapperV2.java
 497a877 
  
repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedSearchIndexer.java
 4a09b08 
  repository/src/main/java/org/apache/atlas/repository/graph/GraphHelper.java 
7b7ec65 
  
repository/src/main/java/org/apache/atlas/repository/impexp/AtlasServerService.java
 542106f 
  
repository/src/main/java/org/apache/atlas/repository/impexp/ExportService.java 
0491a85 
  
repository/src/main/java/org/apache/atlas/repository/impexp/ImportService.java 
1d29bf8 
  
repository/src/main/java/org/apache/atlas/repository/impexp/ImportTransforms.java
 a2f592c 
  repository/src/main/java/org/apache/atlas/repository/impexp/ZipSink.java 
6375454 
  repository/src/main/java/org/apache/atlas/repository/impexp/ZipSource.java 
812add9 
  
repository/src/main/java/org/apache/atlas/repository/impexp/ZipSourceDirect.java
 04342fa 
  
repository/src/main/java/org/apache/atlas/repository/impexp/ZipSourceWithBackingDirectory.java
 7963800 
  
repository/src/main/java/org/apache/atlas/repository/migration/DataMigrationService.java
 0a2257e 
  
repository/src/main/java/org/apache/atlas/repository/migration/ZipFileMigrationImporter.java
 d56261f 
  repository/src/main/java/org/apache/atlas/repository/ogm/AtlasServerDTO.java 
2f7ca11 
  
repository/src/main/java/org/apache/atlas/repository/store/bootstrap/AtlasTypeDefStoreInitializer.java
 8e7c1b3 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/DeleteHandlerV1.java
 3f8503a 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasClassificationDefStoreV2.java
 9ffede4 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasEntityChangeNotifier.java
 0dc3193 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasEntityDefStoreV2.java
 e5153de 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasEntityStoreV2.java
 89076c1 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasRelationshipStoreV2.java
 8d74489 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasStructDefStoreV2.java
 9a45f00 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasTypeDefGraphStoreV2.java
 ed17b92 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/BulkImporterImpl.java
 8e17fd4 
  

[jira] [Created] (ATLAS-3831) UI: Add entity icon for spark

[Keval Bhatt (Jira)]

Keval Bhatt created ATLAS-3831:
--

 Summary: UI: Add entity icon for spark
 Key: ATLAS-3831
 URL: https://issues.apache.org/jira/browse/ATLAS-3831
 Project: Atlas
  Issue Type: Bug
Reporter: Keval Bhatt
Assignee: Keval Bhatt
 Fix For: 2.1.0, 3.0.0






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

[jira] [Updated] (ATLAS-3830) UI: Business Metadata tab misalignment issue

[Durga Kadam (Jira)]

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

Durga Kadam updated ATLAS-3830:
---
Summary: UI: Business Metadata tab misalignment issue  (was: Business 
Metadata tab overlapping issue)

> UI: Business Metadata tab misalignment issue
> 
>
> Key: ATLAS-3830
> URL: https://issues.apache.org/jira/browse/ATLAS-3830
> Project: Atlas
>  Issue Type: Bug
>Reporter: Durga Kadam
>Priority: Minor
> Attachments: missalignment-due-to-business-metadata-selection.webm
>
>
> Misalignment happens when the drop-downs are closed and reopened from left 
> panel.
> Please find attached video clip for steps to reproduce.
>  



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

[jira] [Assigned] (ATLAS-3830) UI: Business Metadata tab misalignment issue

[Keval Bhatt (Jira)]

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

Keval Bhatt reassigned ATLAS-3830:
--

Assignee: Keval Bhatt

> UI: Business Metadata tab misalignment issue
> 
>
> Key: ATLAS-3830
> URL: https://issues.apache.org/jira/browse/ATLAS-3830
> Project: Atlas
>  Issue Type: Bug
>Reporter: Durga Kadam
>Assignee: Keval Bhatt
>Priority: Minor
> Attachments: missalignment-due-to-business-metadata-selection.webm
>
>
> Misalignment happens when the drop-downs are closed and reopened from left 
> panel.
> Please find attached video clip for steps to reproduce.
>  



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

[jira] [Commented] (ATLAS-3780) Change 'Status' from Classification System Attributes to EntityStatus

[ASF subversion and git services (Jira)]

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

ASF subversion and git services commented on ATLAS-3780:


Commit aebf7fd97e16956cd02489e44d089a4772512656 in atlas's branch 
refs/heads/branch-2.0 from Pinal Shah
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=aebf7fd ]

ATLAS-3780 : Change 'Status' from Classification System Attributes to 
EntityStatus

(cherry picked from commit 985264e129687e4d2c6bfaaa92f6a6550a106e89)


> Change 'Status' from Classification System Attributes to EntityStatus
> -
>
> Key: ATLAS-3780
> URL: https://issues.apache.org/jira/browse/ATLAS-3780
> Project: Atlas
>  Issue Type: Task
>  Components: atlas-intg
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: BasicSearch
> Fix For: 3.0.0
>
> Attachments: Screen Shot 2020-05-05 at 4.40.40 PM.png
>
>




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

Re: Review Request 72566: ATLAS-1798 : Fix Findbugs problems in repository module

[mayank jain]

> On June 8, 2020, 2:39 p.m., Madhan Neethiraj wrote:
> > repository/src/main/java/org/apache/atlas/discovery/EntitySearchProcessor.java
> > Line 265 (original)
> > 
> >
> > Why is this code block removed? If necessary, please rebase.

This code block was showing Dead Code by findbugs, initially line #276 was 
showing dead code so i removed and then the code above started showing dead 
code. That is why i had to remove the whole code block.


> On June 8, 2020, 2:39 p.m., Madhan Neethiraj wrote:
> > repository/src/main/java/org/apache/atlas/glossary/GlossaryService.java
> > Line 905 (original), 905 (patched)
> > 
> >
> > This update doesn't look right. Why is 'ret' initialized in #905, and 
> > have it reassinged in #915. What this the issue flagged for the existing 
> > code?

This code block was initially showing "Useless object stored in variable ret of 
method" I tried to make less changes to the existing code as possible  though i 
have made better changes now, please have a look.


> On June 8, 2020, 2:39 p.m., Madhan Neethiraj wrote:
> > repository/src/main/java/org/apache/atlas/query/antlr4/AtlasDSLLexer.java
> > Line 86 (original), 88 (patched)
> > 
> >
> > Use of Arrays.copyOf() could cause excessive memory allocation. Why is 
> > this necessary - in AtlasDSLLexer.java, AtlasDSLParser.java?

By statement "return tokenNames;" findBugs was throwing 
"org.apache.atlas.query.antlr4.AtlasDSLLexer.getTokenNames() may expose 
internal representation by returning AtlasDSLLexer.tokenNames 
[org.apache.atlas.query.antlr4.AtlasDSLLexer] At AtlasDSLLexer.java:[line 88] 
EI_EXPOSE_REP"
That is why i had to opt for this solution.


- mayank


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/72566/#review220966
---


On June 9, 2020, 12:44 p.m., mayank jain wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/72566/
> ---
> 
> (Updated June 9, 2020, 12:44 p.m.)
> 
> 
> Review request for atlas, Jayendra Parab, Madhan Neethiraj, Nixon Rodrigues, 
> and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-1798
> https://issues.apache.org/jira/browse/ATLAS-1798
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Currently Findbugs complaints about some problems (see attachment) in the 
> repository module. They should be fixed to get the code more reliable.
> 
> 
> Diffs
> -
> 
>   repository/src/main/java/org/apache/atlas/GraphTransactionInterceptor.java 
> 57e454a 
>   
> repository/src/main/java/org/apache/atlas/discovery/EntityDiscoveryService.java
>  dd4d1b4 
>   
> repository/src/main/java/org/apache/atlas/discovery/EntitySearchProcessor.java
>  56956e6 
>   
> repository/src/main/java/org/apache/atlas/discovery/SearchAggregatorImpl.java 
> e8f7dbc 
>   repository/src/main/java/org/apache/atlas/discovery/SearchProcessor.java 
> 804c694 
>   repository/src/main/java/org/apache/atlas/glossary/GlossaryService.java 
> d630f66 
>   repository/src/main/java/org/apache/atlas/glossary/GlossaryTermUtils.java 
> 2c84ec7 
>   repository/src/main/java/org/apache/atlas/glossary/GlossaryUtils.java 
> 2a2cebb 
>   repository/src/main/java/org/apache/atlas/query/AtlasDSL.java b8a744b 
>   repository/src/main/java/org/apache/atlas/query/GremlinQueryComposer.java 
> 801e898 
>   repository/src/main/java/org/apache/atlas/query/antlr4/AtlasDSLLexer.java 
> 142b9ca 
>   repository/src/main/java/org/apache/atlas/query/antlr4/AtlasDSLParser.java 
> 6b33edb 
>   
> repository/src/main/java/org/apache/atlas/repository/audit/AbstractStorageBasedAuditRepository.java
>  1aac375 
>   
> repository/src/main/java/org/apache/atlas/repository/audit/EntityAuditListener.java
>  69d373d 
>   
> repository/src/main/java/org/apache/atlas/repository/audit/EntityAuditListenerV2.java
>  79527ac 
>   
> repository/src/main/java/org/apache/atlas/repository/audit/HBaseBasedAuditRepository.java
>  9fca744 
>   
> repository/src/main/java/org/apache/atlas/repository/converters/AtlasArrayFormatConverter.java
>  c335f0a 
>   
> repository/src/main/java/org/apache/atlas/repository/converters/AtlasInstanceConverter.java
>  6fc0c65 
>   
> repository/src/main/java/org/apache/atlas/repository/converters/AtlasMapFormatConverter.java
>  0eacd8e 
>   
> repository/src/main/java/org/apache/atlas/repository/converters/AtlasStructFormatConverter.java
>  ae92b8b 
>   
> repository/src/main/java/org/apache/atlas/repository/graph/FullTextMapperV2.java
>  497a877 
>   
> 

[jira] [Updated] (ATLAS-3829) UI: Clicking on meanings from relationship tab should redirect to terms detail page.

[Keval Bhatt (Jira)]

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

Keval Bhatt updated ATLAS-3829:
---
Summary: UI: Clicking on meanings from relationship tab should redirect to 
terms detail page.  (was: UI: Relationship tab clicking on meanings should 
redirect to terms detail page.)

> UI: Clicking on meanings from relationship tab should redirect to terms 
> detail page.
> 
>
> Key: ATLAS-3829
> URL: https://issues.apache.org/jira/browse/ATLAS-3829
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: image-2020-06-09-17-14-17-856.png, 
> image-2020-06-09-17-14-17-989.png
>
>
> * Assign term to Entity
>  * Go to relationship tab click on meanings link
>  * It should redirect to term detail page not entity detail page.
>  
> !image-2020-06-09-17-14-17-989.png|width=564,height=343!!image-2020-06-09-17-14-17-856.png|width=555,height=334!



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

[jira] [Updated] (ATLAS-3829) UI: Clicking on meanings from relationship tab should redirect to terms details page.

[Keval Bhatt (Jira)]

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

Keval Bhatt updated ATLAS-3829:
---
Summary: UI: Clicking on meanings from relationship tab should redirect to 
terms details page.  (was: UI: Clicking on meanings from relationship tab 
should redirect to terms detail page.)

> UI: Clicking on meanings from relationship tab should redirect to terms 
> details page.
> -
>
> Key: ATLAS-3829
> URL: https://issues.apache.org/jira/browse/ATLAS-3829
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
> Attachments: image-2020-06-09-17-14-17-856.png, 
> image-2020-06-09-17-14-17-989.png
>
>
> * Assign term to Entity
>  * Go to relationship tab click on meanings link
>  * It should redirect to term detail page not entity detail page.
>  
> !image-2020-06-09-17-14-17-989.png|width=564,height=343!!image-2020-06-09-17-14-17-856.png|width=555,height=334!



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

[jira] [Updated] (ATLAS-3830) Business Metadata tab overlapping issue

[Durga Kadam (Jira)]

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

Durga Kadam updated ATLAS-3830:
---
Description: 
Misalignment happens when the drop-downs are closed and reopened from left 
panel.

Please find attached video clip for steps to reproduce.

 

  was:
Misalignment happens when closed and reopen the drop-downs from left panel.

Please find attached video clip for steps to reproduce.

 


> Business Metadata tab overlapping issue
> ---
>
> Key: ATLAS-3830
> URL: https://issues.apache.org/jira/browse/ATLAS-3830
> Project: Atlas
>  Issue Type: Bug
>Reporter: Durga Kadam
>Priority: Minor
> Attachments: missalignment-due-to-business-metadata-selection.webm
>
>
> Misalignment happens when the drop-downs are closed and reopened from left 
> panel.
> Please find attached video clip for steps to reproduce.
>  



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

[jira] [Updated] (ATLAS-3780) Change 'Status' from Classification System Attributes to EntityStatus

[Pinal (Jira)]

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

Pinal updated ATLAS-3780:
-
Fix Version/s: (was: 2.1.0)

> Change 'Status' from Classification System Attributes to EntityStatus
> -
>
> Key: ATLAS-3780
> URL: https://issues.apache.org/jira/browse/ATLAS-3780
> Project: Atlas
>  Issue Type: Task
>  Components: atlas-intg
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: BasicSearch
> Fix For: 3.0.0
>
> Attachments: Screen Shot 2020-05-05 at 4.40.40 PM.png
>
>




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

[jira] [Updated] (ATLAS-3831) UI: Add entity icon for spark

[Keval Bhatt (Jira)]

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

Keval Bhatt updated ATLAS-3831:
---
Issue Type: Improvement  (was: Bug)

> UI: Add entity icon for spark
> -
>
> Key: ATLAS-3831
> URL: https://issues.apache.org/jira/browse/ATLAS-3831
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
>




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

[jira] [Updated] (ATLAS-3827) UI: Use moment date format instead of default date format.

[Keval Bhatt (Jira)]

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

Keval Bhatt updated ATLAS-3827:
---
Summary: UI: Use moment date format instead of default date format.  (was: 
UI: Insted of default date format it should be moment format.)

> UI: Use moment date format instead of default date format.
> --
>
> Key: ATLAS-3827
> URL: https://issues.apache.org/jira/browse/ATLAS-3827
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0
>
>
> Date Format should be
> /MM/DD hh:mm:ss



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

[jira] [Created] (ATLAS-3829) UI: Relationship tab clicking on meanings should redirect to terms detail page.

[Keval Bhatt (Jira)]

Keval Bhatt created ATLAS-3829:
--

 Summary: UI: Relationship tab clicking on meanings should redirect 
to terms detail page.
 Key: ATLAS-3829
 URL: https://issues.apache.org/jira/browse/ATLAS-3829
 Project: Atlas
  Issue Type: Bug
Reporter: Keval Bhatt
Assignee: Keval Bhatt
 Fix For: 2.1.0, 3.0.0
 Attachments: image-2020-06-09-17-14-17-856.png, 
image-2020-06-09-17-14-17-989.png

* Assign term to Entity
 * Go to relationship tab click on meanings link
 * It should redirect to term detail page not entity detail page.

 

!image-2020-06-09-17-14-17-989.png|width=564,height=343!!image-2020-06-09-17-14-17-856.png|width=555,height=334!



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

[jira] [Created] (ATLAS-3830) Business Metadata tab overlapping issue

[Durga Kadam (Jira)]

Durga Kadam created ATLAS-3830:
--

 Summary: Business Metadata tab overlapping issue
 Key: ATLAS-3830
 URL: https://issues.apache.org/jira/browse/ATLAS-3830
 Project: Atlas
  Issue Type: Bug
Reporter: Durga Kadam
 Attachments: missalignment-due-to-business-metadata-selection.webm

Misalignment happens when closed and reopen the drop-downs from left panel.

Please find attached video clip for steps to reproduce.

 



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

Re: Seeking advice on Atlas XSS vulnerabilities

[Madhan Neethiraj]

Bolke,

> 1. Filtering input on arrival where the user cannot manipulate it anymore 
> (i.e. server)
It's not clear what you expect the server to do here? Should HTML characters be 
escaped in all inputs, before saving the data in its store? Can you give few 
examples of server-side manipulation due to unescaped HTML characters?

> 2. Encode data on output
I think asking the server side to escape all HTML characters in its response is 
a very bad idea. Consider forcing such a requirement on a RDBMS - wouldn't this 
mandate every client to un-escape every column value returned for queries? Can 
you add references to applications that perform HTML escape of all its REST API 
responses?.

> 3. Set correct Http content headers (e.g. application/json)
This is already being done. Do you find this missing for any specific usecases?

> 4. Set correct Content Security Policy.
This is being looked into.

Regards,
Madhan


On 6/9/20, 12:49 AM, "Bolke de Bruin"  wrote:

Hi Madhan,

I don’t think solving this on the front-end is sufficient and the defense 
should be more in-depth. The front-end is after all client side and can be 
manipulated by the user. Typically one solves XSS vulnerabilities by:

1. Filtering input on arrival where the user cannot manipulate it anymore 
(i.e. server)
2. Encode data on output
3. Set correct Http content headers (e.g. application/json)
4. Set correct Content Security Policy.

Your proposed solution does not fit any of those criteria. If you are 
worried about compatibility I suggest making it a server side configuration 
variable (e.g. atlas.server.insecure_escaping) which should default to “false” 
imho and alternative could be to enable configurable escaping but that’s more 
complex.

Note that in this case also #4 CSP headers seem to be very loose 
(unsafe-inline, unsafe-eval) which add to the attack surface:  


https://github.com/apache/atlas/blob/master/webapp/src/main/java/org/apache/atlas/web/filters/HeadersUtil.java#L44

Regards,
Bolke

Verstuurd vanaf mijn iPad

> Op 9 jun. 2020 om 06:04 heeft Madhan Neethiraj  het 
volgende geschreven:
> 
> Melinda,
> 
> Thank you for adding details. I think the frontend must take steps to 
prevent JavaScript execution while handling values in REST API responses.
> 
> Server side escaping all HTML characters in all responses wouldn’t be the 
right approach, as browser is not the only consumer of the responses. Consider 
applications that parse response from Atlas REST APIs; all such applications 
must be updated to deal with escaped HTML characters in responses. This will 
likely break existing Atlas integrations.
> 
> Hope this helps.
> 
> Regards,
> Madhan
> 
> On 6/8/20, 6:31 PM, "Melinda Crane"  wrote:
> 
>Apologies, looks like the second half of the email I just sent got
>formatted weirdly (I was copying from a failed earlier email attempt 
that
>got rejected for attaching images). Just to make sure it doesn’t get 
buried:
> 
>Of course this specific case can be patched on the frontend, but doing 
some
>kind of HTML sanitization escaping into the 
whatever-is-handling-the-ajax
>(EntityREST or AtlasEntityStoreV2, maybe?) to blanket-catch HTML 
characters
>sounds safer.
> 
>Hope this helps express my concerns.
>From, Melinda Crane
> 
> 
>>On Mon, Jun 8, 2020 at 9:13 PM Melinda Crane  wrote:
>> 
>> Dear Madhan,
>> 
>> Thank you kindly for your response and for offering to look into 
potential
>> solutions. I've been trying to step through how the ajax calls are 
handled,
>> I don't really see the AtlasJsonProvider being used much at all actually
>> for that. My concern is that the data from the ajax calls aren't being
>> sanitized on the backend. I see there is a ton of sanitization happening 
on
>> the frontend (lots of calls to _.escape()), but they're not all captured.
>> For example.
>> 
>> In CommonViewFunction, in the propertyTable
>> 

 function,
>> URLs are not escaped. So I can create an entity that has a key value of
>> 
>> https://www.google.com/search?\;>> height='\''1'\'' onload='\''window.alert(\"boo\");'\''>
>> 
>> and my script will successfully get successfully injected into my browser
>> when I try to view it. Looks like I can't attach images here but here's 
the
>> elements:
>> 
>> 
>>
>>> class="hide-empty-value">
>>
>>newSchema
>>
>>
>>N/A
>>
>> 

Re: Review Request 72486: ATLAS-3780 : Change 'Status' from Classification System Attributes to EntityStatus

[Nixon Rodrigues]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/72486/#review220979
---


Ship it!




Ship It!

- Nixon Rodrigues


On June 8, 2020, 3:14 p.m., Pinal Shah wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/72486/
> ---
> 
> (Updated June 8, 2020, 3:14 p.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj, Nixon Rodrigues, and Sarath 
> Subramanian.
> 
> 
> Bugs: ATLAS-3780
> https://issues.apache.org/jira/browse/ATLAS-3780
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> We are having 'State' Attribute for Status i.e ACTIVE and DELETED.
> Whenever Entity is Deleted,'state' is always ACTIVE for Classification 
> vertices but 'entityState' gets reflected as 'DELETED'.
> 
> For this UI, needs to handle '_entityStatus' as enum and whenever DELETED is 
> selected, showHistoricalEntities needs to be true.
> 
> 
> Diffs
> -
> 
>   intg/src/main/java/org/apache/atlas/type/AtlasClassificationType.java 
> 4d0179c44 
>   intg/src/main/java/org/apache/atlas/type/Constants.java 3fc13056e 
> 
> 
> Diff: https://reviews.apache.org/r/72486/diff/3/
> 
> 
> Testing
> ---
> 
> Manually tested
> 
> 
> Thanks,
> 
> Pinal Shah
> 
>

[jira] [Commented] (ATLAS-3780) Change 'Status' from Classification System Attributes to EntityStatus

[ASF subversion and git services (Jira)]

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

ASF subversion and git services commented on ATLAS-3780:


Commit 985264e129687e4d2c6bfaaa92f6a6550a106e89 in atlas's branch 
refs/heads/master from Pinal Shah
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=985264e ]

ATLAS-3780 : Change 'Status' from Classification System Attributes to 
EntityStatus


> Change 'Status' from Classification System Attributes to EntityStatus
> -
>
> Key: ATLAS-3780
> URL: https://issues.apache.org/jira/browse/ATLAS-3780
> Project: Atlas
>  Issue Type: Task
>  Components: atlas-intg
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: BasicSearch
> Fix For: 2.1.0, 3.0.0
>
> Attachments: Screen Shot 2020-05-05 at 4.40.40 PM.png
>
>




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

Re:atlas-release-2.1.0-rc1 start up error

[lk_hadoop]

I foud the reason, because I use elasticsearch as backend first to start atlas, 
I need to remove the hbase table create by JanusGraph.
but there is another problem:
the solr I config with :
atlas.graph.index.search.solr.mode=http
atlas.graph.index.search.solr.http-urls=http://10.8.130.52:8983/solr
first I give the wrong url, now when I start up atlas I got error:
ERROR - [main:] ~ Unable to save documents to Solr as one of the shape objects 
stored were not compatible with Solr. (Solr6Index:613)
org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error 
from server at http://10.8.130.52:8983/solr: Expected mime type 
application/octet-stream but got text/html. 


Error 404 Not Found

HTTP ERROR 404
Problem accessing /solr/vertex_index/update. Reason:
Not Found




at 
org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:591)
at 
org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:253)
at 
org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:242)
at 
org.apache.solr.client.solrj.impl.LBHttpSolrClient.request(LBHttpSolrClient.java:663)
at 
org.apache.solr.client.solrj.impl.LBHttpSolrClient.request(LBHttpSolrClient.java:638)
at org.janusgraph.diskstorage.solr.Solr6Index.commitChanges(Solr6Index.java:611)
at org.janusgraph.diskstorage.solr.Solr6Index.mutate(Solr6Index.java:487)
...







在 2020-06-09 12:13:09，"lk_hadoop"  写道：

hi,all: 
2020-06-09 11:29:41,005 INFO  - [main:] ~ Loading atlas-application.properties 
from 
file:/home/devuser/atlas/apache-atlas-2.1.0/conf/atlas-application.properties 
(ApplicationProperties:134)
2020-06-09 11:29:41,012 INFO  - [main:] ~ Using graphdb backend 'janus' 
(ApplicationProperties:314)
2020-06-09 11:29:41,012 INFO  - [main:] ~ Using storage backend 'hbase2' 
(ApplicationProperties:325)
2020-06-09 11:29:41,012 INFO  - [main:] ~ Using index backend 'solr' 
(ApplicationProperties:336)
2020-06-09 11:29:41,014 INFO  - [main:] ~ Atlas is running in MODE: PROD. 
(ApplicationProperties:340)
2020-06-09 11:29:41,014 INFO  - [main:] ~ Setting solr-wait-searcher property 
'true' (ApplicationProperties:346)
2020-06-09 11:29:41,014 INFO  - [main:] ~ Setting index.search.map-name 
property 'false' (ApplicationProperties:350)
2020-06-09 11:29:41,015 INFO  - [main:] ~ Setting 
atlas.graph.index.search.max-result-set-size = 150 (ApplicationProperties:360)
2020-06-09 11:29:41,015 INFO  - [main:] ~ Property (set to default) 
atlas.graph.cache.db-cache = true (ApplicationProperties:372)
2020-06-09 11:29:41,015 INFO  - [main:] ~ Property (set to default) 
atlas.graph.cache.db-cache-clean-wait = 20 (ApplicationProperties:372)
2020-06-09 11:29:41,015 INFO  - [main:] ~ Property (set to default) 
atlas.graph.cache.db-cache-size = 0.5 (ApplicationProperties:372)
2020-06-09 11:29:41,015 INFO  - [main:] ~ Property (set to default) 
atlas.graph.cache.tx-cache-size = 15000 (ApplicationProperties:372)
2020-06-09 11:29:41,015 INFO  - [main:] ~ Property (set to default) 
atlas.graph.cache.tx-dirty-size = 120 (ApplicationProperties:372)
2020-06-09 11:29:41,023 INFO  - [main:] ~ 

   Atlas Server (STARTUP)


project.name:apache-atlas
project.description:Metadata Management and Data Governance Platform over Hadoop
build.user:devuser
build.epoch:1591663542701
project.version:2.1.0
build.version:2.1.0
vc.revision:release
vc.source.url:scm:git:git://git.apache.org/atlas.git/atlas-webapp

 (Atlas:215)
2020-06-09 11:29:41,023 INFO  - [main:] ~ > 
(Atlas:216)
2020-06-09 11:29:41,023 INFO  - [main:] ~ Server starting with TLS ? false on 
port 21000 (Atlas:217)
2020-06-09 11:29:41,024 INFO  - [main:] ~ < 
(Atlas:218)
2020-06-09 11:29:41,811 INFO  - [main:] ~ Logged in user devuser (auth:SIMPLE) 
(LoginProcessor:77)
2020-06-09 11:29:42,174 INFO  - [main:] ~ Not running setup per configuration 
atlas.server.run.setup.on.start. (SetupSteps$SetupRequired:189)
2020-06-09 11:29:44,478 WARN  - [main:] ~ Local setting 
index.search.solr.mode=http (Type: GLOBAL_OFFLINE) is overridden by globally 
managed value (cloud).  Use the ManagementSystem interfa
ce instead of the local configuration to control this setting. 
(ReadConfigurationBuilder:268)
2020-06-09 11:29:44,480 WARN  - [main:] ~ Local setting 
index.search.backend=solr (Type: GLOBAL_OFFLINE) is overridden by globally 
managed value (elasticsearch).  Use the ManagementSystem i
nterface instead of the local configuration to control this setting. 
(ReadConfigurationBuilder:268)
2020-06-09 11:29:44,488 WARN  - [main:] ~ Local setting 
index.search.map-name=false (Type: GLOBAL) is overridden by globally managed 
value (true).  Use the ManagementSystem interface instea
d of the local configuration to control 

Re: Seeking advice on Atlas XSS vulnerabilities

[Bolke de Bruin]

Hi Madhan,

I don’t think solving this on the front-end is sufficient and the defense 
should be more in-depth. The front-end is after all client side and can be 
manipulated by the user. Typically one solves XSS vulnerabilities by:

1. Filtering input on arrival where the user cannot manipulate it anymore (i.e. 
server)
2. Encode data on output
3. Set correct Http content headers (e.g. application/json)
4. Set correct Content Security Policy.

Your proposed solution does not fit any of those criteria. If you are worried 
about compatibility I suggest making it a server side configuration variable 
(e.g. atlas.server.insecure_escaping) which should default to “false” imho and 
alternative could be to enable configurable escaping but that’s more complex.

Note that in this case also #4 CSP headers seem to be very loose 
(unsafe-inline, unsafe-eval) which add to the attack surface:  

https://github.com/apache/atlas/blob/master/webapp/src/main/java/org/apache/atlas/web/filters/HeadersUtil.java#L44

Regards,
Bolke

Verstuurd vanaf mijn iPad

> Op 9 jun. 2020 om 06:04 heeft Madhan Neethiraj  het 
> volgende geschreven:
> 
> Melinda,
> 
> Thank you for adding details. I think the frontend must take steps to prevent 
> JavaScript execution while handling values in REST API responses.
> 
> Server side escaping all HTML characters in all responses wouldn’t be the 
> right approach, as browser is not the only consumer of the responses. 
> Consider applications that parse response from Atlas REST APIs; all such 
> applications must be updated to deal with escaped HTML characters in 
> responses. This will likely break existing Atlas integrations.
> 
> Hope this helps.
> 
> Regards,
> Madhan
> 
> On 6/8/20, 6:31 PM, "Melinda Crane"  wrote:
> 
>Apologies, looks like the second half of the email I just sent got
>formatted weirdly (I was copying from a failed earlier email attempt that
>got rejected for attaching images). Just to make sure it doesn’t get 
> buried:
> 
>Of course this specific case can be patched on the frontend, but doing some
>kind of HTML sanitization escaping into the whatever-is-handling-the-ajax
>(EntityREST or AtlasEntityStoreV2, maybe?) to blanket-catch HTML characters
>sounds safer.
> 
>Hope this helps express my concerns.
>From, Melinda Crane
> 
> 
>>On Mon, Jun 8, 2020 at 9:13 PM Melinda Crane  wrote:
>> 
>> Dear Madhan,
>> 
>> Thank you kindly for your response and for offering to look into potential
>> solutions. I've been trying to step through how the ajax calls are handled,
>> I don't really see the AtlasJsonProvider being used much at all actually
>> for that. My concern is that the data from the ajax calls aren't being
>> sanitized on the backend. I see there is a ton of sanitization happening on
>> the frontend (lots of calls to _.escape()), but they're not all captured.
>> For example.
>> 
>> In CommonViewFunction, in the propertyTable
>> 
>>  function,
>> URLs are not escaped. So I can create an entity that has a key value of
>> 
>> https://www.google.com/search?\;>> height='\''1'\'' onload='\''window.alert(\"boo\");'\''>
>> 
>> and my script will successfully get successfully injected into my browser
>> when I try to view it. Looks like I can't attach images here but here's the
>> elements:
>> 
>> 
>>
>>> class="hide-empty-value">
>>
>>newSchema
>>
>>
>>N/A
>>
>>
>>
>>
>>classField
>>
>>
>>> href="https://www.google.com/search?;>
>>> height="1" onload="window.alert(boo);">
>>"https://www.google.com/search
>> ?"
>>> height="1" onload="window.alert(boo);">
>>...
>> 
>> ^You can see the iframe-script combo here.
>> 
>> Of course this specific case can be patched on the frontend, but doing
>> some kind of HTML sanitization escaping on the
>> whatever-is-handling-the-ajax (EntityREST or AtlasEntityStoreV2, maybe?) to
>> blanket-catch HTML characters sounds safer.
>> 
>> Hope this helps express my concerns.
>> From, Melinda Crane
>> 
>> 
>>> On Sat, Jun 6, 2020 at 2:48 PM Madhan Neethiraj  wrote:
>>> 
>>> Melinda,
>>> 
>>> Thank you for reaching out to Apache Atlas community.
>>> 
>>> As you noted, AtlasJsonProvider is used to deserialize/serialize REST API
>>> requests and responses. In addition, methods in AtlasJson are used in to
>>> convert to/from Json. It will help 

Re: [VOTE] Release Apache Atlas version 2.1.0 - rc1

[Bolke de Bruin]

Hi Madhan,

These are indeed related to the issues Melinda brought up and which are now 
confirmed.

It think that warrants another RC with those items fixed.

Cheers
Bolke

Verstuurd vanaf mijn iPad

> Op 8 jun. 2020 om 20:41 heeft Madhan Neethiraj  het 
> volgende geschreven:
> 
> Bolke,
> 
> Can you send specific security concerns that need to addressed in 2.1.0 
> release? If this is about questions from Melinda Crane, I asked for Melinda 
> details to better understand the questions. I suggest we know the details 
> before treating them as release blockers.
> 
> Thanks,
> Madhan
> 
> On 6/8/20, 9:56 AM, "Bolke de Bruin"  wrote:
> 
>This is my -1 (non-binding) which I will revert to +1 when the security 
> concerns have been addressed/clarified. 
> 
>Given that Atlas has pretty slow releases I think it smart to address them 
> now. 
> 
>Cheers
>Bolke
> 
>Sent from my iPhone
> 
>> On 8 Jun 2020, at 18:18, Sharmadha Sainath  
>> wrote:
>> 
>> +1 for Apache Atlas 2.1 RC1
>> 
>> 
>>  - Validated MD5 and SHA512 checksum of source.
>>  - Brought up Atlas using embedded HBase and Solr.
>>  - Verified DSL , Basic Search , Quick search and Suggestions
>>  - Verified Basic search using system attributes filters (multiple
>>  classification search , labels , custom attributes , business metadata
>>  search)
>>  - Added labels , user defined properties (custom attributes) , business
>>  metadata to entities and verified the entity properties and audits.
>>  - Purged Soft Deleted entity and verified purge audits.
>>  - Saved the Favorite searches and executed them.
>> 
>> Thanks,
>> Sharmadha S.
>> 
>> 
>> 
>>> On Mon, Jun 8, 2020 at 6:23 PM Nixon Rodrigues <
>>> nixon.rodrig...@freestoneinfotech.com> wrote:
>>> 
>>> Thanks Madhan for putting 2.1 RC1 together for the vote.
>>> 
>>> +1 for Apache Atlas 2.1 RC1
>>> 
>>> Validated the following items.
>>> 
>>>  1. verified the md5/sha checksum of source bundle.
>>>  2. packaging with -Pdist,embedded-hbase-solr is good.
>>>  3. Unit testcase passes.
>>>  4. Run quickstart and all the types and entities created are loading
>>>  correctly on the UI.
>>>  5. Create tags, glossary, term and its apply correctly on entities.
>>>  6. Created business metadata with attributes and applied it to entities.
>>>  7. tested basic and quick search flow.
>>>  8. Verified statistics page details
>>> 
>>> 
>>> Thanks & Regards
>>> Nixon
>>> 
>>> 
>>> 
>>> On Mon, Jun 8, 2020 at 11:17 AM Sarath Subramanian 
>>> wrote:
>>> 
 +1 for Apache Atlas 2.1 RC1
 
 Validated the following:
 
  - No binaries in source
  - Verified source checksum - md5 and sha512
  - Verified signature
  - Build was successful on the source (mvn clean -DskipTests package
  -Pdist,embedded-hbase-solr)
  - Ran quickStart and validated types and entities were created
  successfully.
  - Validated tag propagation works
  - Added/removed labels to an entity and verified audit is getting
  updated correctly
  - Added user-defined properties and business metadata attributes.
  - Deleted few entities and purged those entities - validated if purge
  audit recorded correctly.
  - Basic sanity tests - basic search (with system attributes), advanced
  search, quick search.
 
 
 
 Thanks,
 Sarath
 
 
 
 On Sat, Jun 6, 2020 at 10:22 AM Madhan Neethiraj 
 wrote:
 
> (resending with plain-text format)
> 
> Atlas team,
> 
> Apache Atlas 2.1.0 rc1, with following fixes since rc0, is now
>>> available
> for vote within dev community.
> 
>   ATLAS-3770: UI(Classic): Active and Deleted hyperlinks for certain
> entities throwing error on click
>   ATLAS-3766: Stats modal not close issue #2
>   ATLAS-3674: ZipFileMigationImporter: Migration status display fix.
> Part 2
> 
> Links to the release artifacts are given below. Please review and vote.
> 
> The vote will be open for at least 72 hours or until necessary votes
>>> are
> reached.
> [ ] +1 Approve
> [ ] +0 No opinion
> [ ] -1 Disapprove (and reason why)
> 
> Thanks,
> Madhan
> 
> 
> List of all issues addressed in this release:
> https://issues.apache.org/jira/issues/?jql=project=ATLAS AND
> status=Resolved AND fixVersion=2.1.0 ORDER BY key DESC
> 
> Git tag for the release:
> https://github.com/apache/atlas/tree/release-2.1.0-rc1
> Sources for the release:
> 
 
>>> https://dist.apache.org/repos/dist/dev/atlas/2.1.0-rc1/apache-atlas-2.1.0-sources.tar.gz
> 
> Source release verification:
> PGP Signature:
> 
 
>>> https://dist.apache.org/repos/dist/dev/atlas/2.1.0-rc1/apache-atlas-2.1.0-sources.tar.gz.asc
> SHA512 Hash:
> 
 
>>> https://dist.apache.org/repos/dist/dev/atlas/2.1.0-rc1/apache-atlas-2.1.0-sources.tar.gz.sha512
> MD5 Hash:
> 
 
>>> 

Re:Re:atlas-release-2.1.0-rc1 start up error

[lk_hadoop]

sorry, I know the reason , I need to creat solr index manully. 

At 2020-06-09 14:20:51, "lk_hadoop"  wrote:
>I foud the reason, because I use elasticsearch as backend first to start 
>atlas, I need to remove the hbase table create by JanusGraph.
>but there is another problem:
>the solr I config with :
>atlas.graph.index.search.solr.mode=http
>atlas.graph.index.search.solr.http-urls=http://10.8.130.52:8983/solr
>first I give the wrong url, now when I start up atlas I got error:
>ERROR - [main:] ~ Unable to save documents to Solr as one of the shape objects 
>stored were not compatible with Solr. (Solr6Index:613)
>org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error 
>from server at http://10.8.130.52:8983/solr: Expected mime type 
>application/octet-stream but got text/html. 
>
>
>Error 404 Not Found
>
>HTTP ERROR 404
>Problem accessing /solr/vertex_index/update. Reason:
>Not Found
>
>
>
>
>at 
>org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:591)
>at 
>org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:253)
>at 
>org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:242)
>at 
>org.apache.solr.client.solrj.impl.LBHttpSolrClient.request(LBHttpSolrClient.java:663)
>at 
>org.apache.solr.client.solrj.impl.LBHttpSolrClient.request(LBHttpSolrClient.java:638)
>at 
>org.janusgraph.diskstorage.solr.Solr6Index.commitChanges(Solr6Index.java:611)
>at org.janusgraph.diskstorage.solr.Solr6Index.mutate(Solr6Index.java:487)
>...
>
>
>
>
>
>
>
>在 2020-06-09 12:13:09，"lk_hadoop"  写道：
>
>hi,all: 
>2020-06-09 11:29:41,005 INFO  - [main:] ~ Loading atlas-application.properties 
>from 
>file:/home/devuser/atlas/apache-atlas-2.1.0/conf/atlas-application.properties 
>(ApplicationProperties:134)
>2020-06-09 11:29:41,012 INFO  - [main:] ~ Using graphdb backend 'janus' 
>(ApplicationProperties:314)
>2020-06-09 11:29:41,012 INFO  - [main:] ~ Using storage backend 'hbase2' 
>(ApplicationProperties:325)
>2020-06-09 11:29:41,012 INFO  - [main:] ~ Using index backend 'solr' 
>(ApplicationProperties:336)
>2020-06-09 11:29:41,014 INFO  - [main:] ~ Atlas is running in MODE: PROD. 
>(ApplicationProperties:340)
>2020-06-09 11:29:41,014 INFO  - [main:] ~ Setting solr-wait-searcher property 
>'true' (ApplicationProperties:346)
>2020-06-09 11:29:41,014 INFO  - [main:] ~ Setting index.search.map-name 
>property 'false' (ApplicationProperties:350)
>2020-06-09 11:29:41,015 INFO  - [main:] ~ Setting 
>atlas.graph.index.search.max-result-set-size = 150 (ApplicationProperties:360)
>2020-06-09 11:29:41,015 INFO  - [main:] ~ Property (set to default) 
>atlas.graph.cache.db-cache = true (ApplicationProperties:372)
>2020-06-09 11:29:41,015 INFO  - [main:] ~ Property (set to default) 
>atlas.graph.cache.db-cache-clean-wait = 20 (ApplicationProperties:372)
>2020-06-09 11:29:41,015 INFO  - [main:] ~ Property (set to default) 
>atlas.graph.cache.db-cache-size = 0.5 (ApplicationProperties:372)
>2020-06-09 11:29:41,015 INFO  - [main:] ~ Property (set to default) 
>atlas.graph.cache.tx-cache-size = 15000 (ApplicationProperties:372)
>2020-06-09 11:29:41,015 INFO  - [main:] ~ Property (set to default) 
>atlas.graph.cache.tx-dirty-size = 120 (ApplicationProperties:372)
>2020-06-09 11:29:41,023 INFO  - [main:] ~ 
>
>   Atlas Server (STARTUP)
>
>
>project.name:apache-atlas
>project.description:Metadata Management and Data Governance Platform over 
>Hadoop
>build.user:devuser
>build.epoch:1591663542701
>project.version:2.1.0
>build.version:2.1.0
>vc.revision:release
>vc.source.url:scm:git:git://git.apache.org/atlas.git/atlas-webapp
>
> (Atlas:215)
>2020-06-09 11:29:41,023 INFO  - [main:] ~ > 
>(Atlas:216)
>2020-06-09 11:29:41,023 INFO  - [main:] ~ Server starting with TLS ? false on 
>port 21000 (Atlas:217)
>2020-06-09 11:29:41,024 INFO  - [main:] ~ < 
>(Atlas:218)
>2020-06-09 11:29:41,811 INFO  - [main:] ~ Logged in user devuser (auth:SIMPLE) 
>(LoginProcessor:77)
>2020-06-09 11:29:42,174 INFO  - [main:] ~ Not running setup per configuration 
>atlas.server.run.setup.on.start. (SetupSteps$SetupRequired:189)
>2020-06-09 11:29:44,478 WARN  - [main:] ~ Local setting 
>index.search.solr.mode=http (Type: GLOBAL_OFFLINE) is overridden by globally 
>managed value (cloud).  Use the ManagementSystem interfa
>ce instead of the local configuration to control this setting. 
>(ReadConfigurationBuilder:268)
>2020-06-09 11:29:44,480 WARN  - [main:] ~ Local setting 
>index.search.backend=solr (Type: GLOBAL_OFFLINE) is overridden by globally 
>managed value (elasticsearch).  Use the ManagementSystem i
>nterface instead of the local configuration to control this setting. 
>(ReadConfigurationBuilder:268)

[jira] [Created] (ATLAS-3827) UI: Insted of default date format it should be defined.

[Keval Bhatt (Jira)]

Keval Bhatt created ATLAS-3827:
--

 Summary: UI: Insted of default date format it should be defined.
 Key: ATLAS-3827
 URL: https://issues.apache.org/jira/browse/ATLAS-3827
 Project: Atlas
  Issue Type: Improvement
Reporter: Keval Bhatt
Assignee: Keval Bhatt


Date Format should be

/MM/DD hh:mm:ss



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

[jira] [Created] (ATLAS-3828) UI: Change 'Status' from Classification System Attributes to EntityStatus

[Keval Bhatt (Jira)]

Keval Bhatt created ATLAS-3828:
--

 Summary: UI: Change 'Status' from Classification System Attributes 
to EntityStatus
 Key: ATLAS-3828
 URL: https://issues.apache.org/jira/browse/ATLAS-3828
 Project: Atlas
  Issue Type: Sub-task
Reporter: Keval Bhatt
Assignee: Keval Bhatt






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

[jira] [Updated] (ATLAS-3827) UI: Insted of default date format it should be moment format.

[Keval Bhatt (Jira)]

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

Keval Bhatt updated ATLAS-3827:
---
Summary: UI: Insted of default date format it should be moment format.  
(was: UI: Insted of default date format it should be defined.)

> UI: Insted of default date format it should be moment format.
> -
>
> Key: ATLAS-3827
> URL: https://issues.apache.org/jira/browse/ATLAS-3827
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
>
> Date Format should be
> /MM/DD hh:mm:ss



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

[jira] [Updated] (ATLAS-3827) UI: Insted of default date format it should be moment format.

[Keval Bhatt (Jira)]

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

Keval Bhatt updated ATLAS-3827:
---
Fix Version/s: 3.0.0

> UI: Insted of default date format it should be moment format.
> -
>
> Key: ATLAS-3827
> URL: https://issues.apache.org/jira/browse/ATLAS-3827
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0
>
>
> Date Format should be
> /MM/DD hh:mm:ss



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