Re: Review Request 72713: ATLAS-3892 : Basic search enhanced Feature - Search history

[Madhan Neethiraj]

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


Ship it!




Ship It!

- Madhan Neethiraj


On July 31, 2020, 12:34 p.m., chaitali wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/72713/
> ---
> 
> (Updated July 31, 2020, 12:34 p.m.)
> 
> 
> Review request for atlas, Jayendra Parab, Madhan Neethiraj, Nixon Rodrigues, 
> and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-3892
> https://issues.apache.org/jira/browse/ATLAS-3892
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> 1.This patch implements the search history feature where from UI we will 
> receive below filters.
> 2.In backend we have introduced a new operator "TIME_RANGE" where all the 
> below 7 attribute values will have TIME_RANGE operator.
> 3.There will be a slight change in the JSON where previously we were passing 
> the Attribute value in Search parameters from the UI but for below filters   
> we will not pass any attributeValue except for "custom range" filter we 
> provide attribute value 
>   for eg ;"attributeValue":"159354180,159544260" .
> 
> New 7 filters :
> 
> 1.last 7 days.
> 2.Last month.
> 3.Last 30 days.
> 4.Today.
> 5.Yesterday.
> 6.Custom Range.
> 7.This Month.
> 
> 
> Diffs
> -
> 
>   common/src/main/java/org/apache/atlas/repository/Constants.java a71787bc0 
>   intg/src/main/java/org/apache/atlas/model/discovery/SearchParameters.java 
> fcc4494f2 
>   repository/src/main/java/org/apache/atlas/discovery/SearchProcessor.java 
> c9a605355 
>   repository/src/main/java/org/apache/atlas/util/SearchPredicateUtil.java 
> 5069d78c8 
>   
> repository/src/test/java/org/apache/atlas/discovery/EntitySearchProcessorTest.java
>  8e42d1700 
> 
> 
> Diff: https://reviews.apache.org/r/72713/diff/6/
> 
> 
> Testing
> ---
> 
> Tested with below json: 
> eg : 
> {
>   "excludeDeletedEntities": true,
>   "includeSubClassifications": true,
>   "includeSubTypes": true,
>   "includeClassificationAttributes": true,
>   "entityFilters": {
> "condition": "AND",
> "criterion": [
>   {
> "attributeName": "__timestamp",
>   "operator": "TIME_RANGE",
>   "attributeValue": "YESTERDAY"
>   }
> ]
>   },
>   "tagFilters": null,
>   "attributes": [
> "__timestamp"
>   ],
>   "limit": 25,
>   "offset": 0,
>   "typeName": "hdfs_path",
>   "classification": null,
>   "termName": null
> }
> eg: Only For custom range filter we provide attribute value.
> {
>   "excludeDeletedEntities": true,
>   "includeSubClassifications": true,
>   "includeSubTypes": true,
>   "includeClassificationAttributes": true,
>   "entityFilters": {
> "condition": "AND",
> "criterion": [
>   {
> "attributeName": "__timestamp",
>   "operator": "TIME_RANGE",
>   "attributeValue": "1595956315473,159596100"
>   }
> ]
>   },
>   "tagFilters": null,
>   "attributes": [
> "__timestamp"
>   ],
>   "limit": 25,
>   "offset": 0,
>   "typeName": "Table",
>   "classification": null,
>   "termName": null
> }
> 
> * Added Test cases to check new processDateRange method functionality
> 
> 
> Thanks,
> 
> chaitali
> 
>

Re: Review Request 72644: ATLAS-3872 Restrict typedef creation when a child type attribute conflicts with parent type attribute of same name

[Madhan Neethiraj]

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




intg/src/main/java/org/apache/atlas/type/AtlasStructType.java
Lines 723 (patched)


Consider replacing #723 - #780 with the following; and call this method 
from resolveReferencesPhase2() in AtlasEntityType and AtlasClassificationType.

  protected void ensureNoAttributeOverride(AtlasTypeRegistry typeRegistry, 
List superTypes) throws AtlasBaseException {
for (AtlasStructType superType : superTypes) {
  for (AtlasAttributeDef attributeDef : 
this.structDef.getAttributeDefs()) {
if 
(superType.getAllAttributes().containsKey(attributeDef.getName())) {
  throw new 
AtlasBaseException(AtlasErrorCode.ATTRIBUTE_NAME_ALREADY_EXISTS_IN_PARENT_TYPE, 
this.getName(), attributeDef.getName(), superType.getName());
}
  }
}
  }


- Madhan Neethiraj


On July 31, 2020, 11:56 a.m., Mandar Ambawane wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/72644/
> ---
> 
> (Updated July 31, 2020, 11:56 a.m.)
> 
> 
> Review request for atlas, Jayendra Parab, Madhan Neethiraj, Nixon Rodrigues, 
> and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-3872
> https://issues.apache.org/jira/browse/ATLAS-3872
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Cause of the problem:
> Type-def Column is created by quick-start script.
> 
> Here in this case, Type-def Column has the attribute "name". And it has 
> property isOptional = true
> 
> Type-def Column is a child of Type-def Asset which also has the attribute 
> "name". And it has property isOptional = false
> 
> Now while creating Entity of Type-def Column from UI, it does not show 
> attribute "name" in the mandatory fields because for Type-def Column its 
> property isOptional = true
> 
> But while validating the attributes from server side we iterate through all 
> the attributes of Entity type (Including Parent's attributes)
> In this case, while validating Type-def Asset's attribute "name" (which has 
> property isOptional = false) we get an error because its value is sent as 
> "null" from UI side.
> 
> 
> Diffs
> -
> 
>   intg/src/main/java/org/apache/atlas/AtlasErrorCode.java a14e43a 
>   intg/src/main/java/org/apache/atlas/type/AtlasClassificationType.java 
> e0843cb 
>   intg/src/main/java/org/apache/atlas/type/AtlasEntityType.java 58de4cc 
>   intg/src/main/java/org/apache/atlas/type/AtlasStructType.java 61ee458 
>   repository/src/test/resources/sales-v1-full.zip 
> 07afbf6ecae312a840b54cae5ab01335c513d180 
>   webapp/src/main/java/org/apache/atlas/examples/QuickStart.java 82a9f5c 
>   webapp/src/main/java/org/apache/atlas/examples/QuickStartV2.java d5cf9b7 
>   webapp/src/test/java/org/apache/atlas/web/integration/BaseResourceIT.java 
> 6db6b58 
>   
> webapp/src/test/java/org/apache/atlas/web/integration/TypesJerseyResourceIT.java
>  7c820e7 
> 
> 
> Diff: https://reviews.apache.org/r/72644/diff/4/
> 
> 
> Testing
> ---
> 
> PreCommit: 
> https://builds.apache.org/job/PreCommit-ATLAS-Build-Test/2007/console
> 
> PreCommit: 
> https://builds.apache.org/job/PreCommit-ATLAS-Build-Test/2014/console
> 
> 
> Thanks,
> 
> Mandar Ambawane
> 
>

[jira] [Commented] (ATLAS-3398) Duplicates for unique attributes

[Damian Warszawski (Jira)]

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

Damian Warszawski commented on ATLAS-3398:
--

Thanks [~amestry]. Of course, I don't mind.

> Duplicates for unique attributes 
> -
>
> Key: ATLAS-3398
> URL: https://issues.apache.org/jira/browse/ATLAS-3398
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0, trunk
>Reporter: Bolke de Bruin
>Assignee: Ashutosh Mestry
>Priority: Blocker
>  Labels: integrity
> Attachments: zrzut_ekranu_2019-09-03_o_10.28.50.png
>
>
> We are seeing issues with entities being added to Atlas with duplicate 
> "qualifiedName". The guids differ and other attributes do also differ. Below 
> a graph that shows the distribution over time for duplicates. We have 
> difficulty determining which one is the right one (as they are different) in 
> order to clean them up.
> We are also not the only ones encountering this as you can in the linked 
> issue.
> We have noticed that Atlas does not use the 
> [locking|https://docs.janusgraph.org/master/advanced-topics/eventual-consistency/]
>  mechanism of Janus to prevent this:
>  
> !zrzut_ekranu_2019-09-03_o_10.28.50.png!



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

[GitHub] [atlas] mohamed-a-abdelaziz commented on pull request #101: add-dist-cassandra-elasticsearch-profile and support GS

[GitBox]

mohamed-a-abdelaziz commented on pull request #101:
URL: https://github.com/apache/atlas/pull/101#issuecomment-667252655


   > @mohamed-a-abdelaziz any idea what are the steps required to run atlas 
with local cassandra and local elastic search? Don't seem to find anything in 
docs.
   
   just follow these steps 
   
   #download cassandra
   `wget 
https://mirrors.gethosted.online/apache/cassandra/3.11.7/apache-cassandra-3.11.7-bin.tar.gz`
   `tar -xzf apache-cassandra-3.11.7-bin.tar.gz`
   `#set start_rpc: true  on apache-cassandra/conf/cassandra.yml file `
   #run cassandra locally
   `/bin/cassandra -f &`
   #download elasticsearch
   `wget 
https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-7.8.1-linux-x86_64.tar.gz`
   `tar -xzf elasticsearch-7.8.1-linux-x86_64.tar.gz`
   #run elassticsearch 
   `/bin/elasticsearch &`
   #run kafka 
   `wget 
https://www.apache.org/dyn/closer.cgi?path=/kafka/2.5.0/kafka_2.12-2.5.0.tgz`
   `tar -xzf kafka_2.12-2.5.0.tgz`
   `/bin/zookeeper-server-start.sh config/zookeeper.properties &`
   `/bin/kafka-server-start.sh config/server.properties &`
   #clone atlas from my fork if you didn't yet :)
   `#set atlas.kafka.zookeeper.connect=localhost:2181 and  
atlas.kafka.bootstrap.servers=localhost:9092 on 
distro/src/conf/atlas-application.properties (or your own ports)`
   #build atlas
   `cd `
   `mvn clean -DskipTests package -Pdist,cassandra-elasticsearch`
   `cd distro/target/apache-atlas-2.1.0-server/apache-atlas-2.1.0`
   #run atlas
   `./bin/atlas_start.py`
   #open your browser and type localhost:21000/
   #user/pass : admin/admin
   
   
   
   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Updated] (ATLAS-3875) Adding missing APIs in AtlasClient with test cases

[Jyoti Singh (Jira)]

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

Jyoti Singh updated ATLAS-3875:
---
Description: 
1. There are many new APIs added to Atlas Project but the corresponding  APIs 
are missing from AtlasClientv2. The aim of this task is to complete the gap 
amongst existing APIs and their endpoints in Atls client. This will also 
include adding test cases via integration testing.

There are functions from AtlasClient for the following REST endpoints
 * TypeRest
 * EntityRest
 * LineageRest
 * DiscoveryRest
 * GlossaryRest
 * RelationshipRest

2. Added Sample-Project to showcase how to integrate with Atlas using 
AtlasCleint. This helps the user to understand the basic rest functionality of 
Atlas.

  was:
There are many new APIs added to Atlas Project but the corresponding  APIs are 
missing from AtlasClientv2. The aim of this task is to complete the gap amongst 
existing APIs and their endpoints in Atls client. This will also include adding 
test cases via integration testing.

There are functions from AtlasClient for the following REST endpoints
 * TypeRest
 * EntityRest
 * LineageRest
 * DiscoveryRest
 * GlossaryRest
 * RelationshipRest


> Adding missing APIs in AtlasClient with test cases
> --
>
> Key: ATLAS-3875
> URL: https://issues.apache.org/jira/browse/ATLAS-3875
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0, 2.1.0
>Reporter: Jyoti Singh
>Assignee: Jyoti Singh
>Priority: Major
>  Labels: api, client
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3875-1.patch, ATLAS-3875-4.patch
>
>
> 1. There are many new APIs added to Atlas Project but the corresponding  APIs 
> are missing from AtlasClientv2. The aim of this task is to complete the gap 
> amongst existing APIs and their endpoints in Atls client. This will also 
> include adding test cases via integration testing.
> There are functions from AtlasClient for the following REST endpoints
>  * TypeRest
>  * EntityRest
>  * LineageRest
>  * DiscoveryRest
>  * GlossaryRest
>  * RelationshipRest
> 2. Added Sample-Project to showcase how to integrate with Atlas using 
> AtlasCleint. This helps the user to understand the basic rest functionality 
> of Atlas.



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

[jira] [Updated] (ATLAS-3875) Adding missing APIs in AtlasClient with test cases

[Jyoti Singh (Jira)]

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

Jyoti Singh updated ATLAS-3875:
---
Attachment: ATLAS-3875-4.patch

> Adding missing APIs in AtlasClient with test cases
> --
>
> Key: ATLAS-3875
> URL: https://issues.apache.org/jira/browse/ATLAS-3875
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0, 2.1.0
>Reporter: Jyoti Singh
>Assignee: Jyoti Singh
>Priority: Major
>  Labels: api, client
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3875-1.patch, ATLAS-3875-4.patch
>
>
> There are many new APIs added to Atlas Project but the corresponding  APIs 
> are missing from AtlasClientv2. The aim of this task is to complete the gap 
> amongst existing APIs and their endpoints in Atls client. This will also 
> include adding test cases via integration testing.
> There are functions from AtlasClient for the following REST endpoints
>  * TypeRest
>  * EntityRest
>  * LineageRest
>  * DiscoveryRest
>  * GlossaryRest
>  * RelationshipRest



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

[jira] [Updated] (ATLAS-3903) New UI: Glossary category not reflected in the tree after creation.

[Keval Bhatt (Jira)]

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

Keval Bhatt updated ATLAS-3903:
---
Fix Version/s: 2.2.0

> New UI: Glossary category not reflected in the tree after creation.
> ---
>
> Key: ATLAS-3903
> URL: https://issues.apache.org/jira/browse/ATLAS-3903
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: Category_does_not_reflect_in_dropdown.mkv
>
>
> Steps reproduce the issue:
>  * Create the glossary
>  * Click on "..." to create the category
>  * After adding category details click on save
> Due to regression newly created category is not rendered in the tree view. if 
> a user clicks on the refresh button then it is visible.
> Please check the attached video for a better understanding.
> [^Category_does_not_reflect_in_dropdown.mkv]



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

[jira] [Commented] (ATLAS-3904) Regression: Glossary term deatils page not able to render the classfication tab

[ASF subversion and git services (Jira)]

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

ASF subversion and git services commented on ATLAS-3904:


Commit 9ce6fc38f3ae26cd19aac6b0a229ea61339e716d in atlas's branch 
refs/heads/branch-2.0 from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=9ce6fc3 ]

ATLAS-3904: Regression: Glossary term deatils page not able to render the 
classfication tab

(cherry picked from commit 38d7b91e4aa205f89d71f85328a513cc61516266)


> Regression: Glossary term deatils page not able to render the classfication 
> tab
> ---
>
> Key: ATLAS-3904
> URL: https://issues.apache.org/jira/browse/ATLAS-3904
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3904.patch, Screen Shot 2020-07-28 at 5.09.08 
> PM.png
>
>
> Click on the term details page and check the console.
>  
> !Screen Shot 2020-07-28 at 5.09.08 PM.png|width=618,height=304!



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

[jira] [Commented] (ATLAS-3904) Regression: Glossary term deatils page not able to render the classfication tab

[ASF subversion and git services (Jira)]

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

ASF subversion and git services commented on ATLAS-3904:


Commit 38d7b91e4aa205f89d71f85328a513cc61516266 in atlas's branch 
refs/heads/master from Keval Bhatt
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=38d7b91 ]

ATLAS-3904: Regression: Glossary term deatils page not able to render the 
classfication tab


> Regression: Glossary term deatils page not able to render the classfication 
> tab
> ---
>
> Key: ATLAS-3904
> URL: https://issues.apache.org/jira/browse/ATLAS-3904
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3904.patch, Screen Shot 2020-07-28 at 5.09.08 
> PM.png
>
>
> Click on the term details page and check the console.
>  
> !Screen Shot 2020-07-28 at 5.09.08 PM.png|width=618,height=304!



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

Re: Review Request 72666: Notification: Solution to Memory Build-up

[Madhan Neethiraj]

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


Ship it!




Ship It!

- Madhan Neethiraj


On July 31, 2020, 3:57 p.m., Ashutosh Mestry wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/72666/
> ---
> 
> (Updated July 31, 2020, 3:57 p.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj, Nikhil Bonte, Nixon Rodrigues, 
> and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-3878
> https://issues.apache.org/jira/browse/ATLAS-3878
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> **Background**
> See JIRA for details.
> 
> *Analysis* Using memory profiling tools, it was observed that large number of 
> notification objects were created. These stayed in memory and later were 
> promoted to higher generation, thereby taking even longer to be collected.
> 
> **Approach**
> Using the fixed-buffer approach to address the problem of creating large 
> number of small objects.
> 
> New *FixedBufferList* This is an encapsulation over *ArrayList*. During 
> initial allocation, list is populated with default values. Features:
> - Setting of values to these pre-allocated objects is achieved by first doing 
> a *get* on the element and then assigning values to it.
> - *toList* fetches the sub-list from the encapsulating list. This uses the 
> state within the class to fetch the right length for the returning array.
> 
> New *NamedFixedBufferList* Maintains a per-thread *FixedBufferList*. This is 
> necessary since the list is now part class's state.
> Modified *EntityAuditListenerV2* Uses the new classes.
> Modifed *EntityNotificationListener* Uses the new classes.
> 
> **Verification**
> - Using the test setup, the memory usage was observed over a period of 24 
> hrs. 
> - Memory usage and object allocation was obvserved using memory profiler.
> 
> 
> Diffs
> -
> 
>   intg/src/main/java/org/apache/atlas/AtlasConfiguration.java a942b9f93 
>   intg/src/main/java/org/apache/atlas/model/Clearable.java PRE-CREATION 
>   intg/src/main/java/org/apache/atlas/model/audit/EntityAuditEventV2.java 
> 63116d467 
>   intg/src/main/java/org/apache/atlas/utils/FixedBufferList.java PRE-CREATION 
>   intg/src/test/java/org/apache/atlas/utils/FixedBufferListTest.java 
> PRE-CREATION 
>   
> repository/src/main/java/org/apache/atlas/repository/audit/EntityAuditListenerV2.java
>  79527acfa 
> 
> 
> Diff: https://reviews.apache.org/r/72666/diff/12/
> 
> 
> Testing
> ---
> 
> **Unit testing**
> Unit tests added for the new classes.
> 
> **Volume testing**
> Setup:
> - Node: Threads 40, Core: 40, Allocated Memory: 12 GB
> - Multiple Kafka queues ingesting data.
> - Bulk entity creation using custom script ingesting 100M entities.
> 
> Memory usage stayed between 0 and 5% during the 24 hr period.
> 
> With:
> - Workers: 64
> - Batch size: 50 (fewer elements in batch improve commit time and audit write 
> time).
> - Throughput: ~1.2 M entities per hour. Without out of memory error.
> 
> **Pre-commit**
> https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/2035/
> https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/2067/
> https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/2076/
> 
> 
> Thanks,
> 
> Ashutosh Mestry
> 
>

[jira] [Assigned] (ATLAS-3398) Duplicates for unique attributes

[Ashutosh Mestry (Jira)]

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

Ashutosh Mestry reassigned ATLAS-3398:
--

Assignee: Ashutosh Mestry

> Duplicates for unique attributes 
> -
>
> Key: ATLAS-3398
> URL: https://issues.apache.org/jira/browse/ATLAS-3398
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0, trunk
>Reporter: Bolke de Bruin
>Assignee: Ashutosh Mestry
>Priority: Blocker
>  Labels: integrity
> Attachments: zrzut_ekranu_2019-09-03_o_10.28.50.png
>
>
> We are seeing issues with entities being added to Atlas with duplicate 
> "qualifiedName". The guids differ and other attributes do also differ. Below 
> a graph that shows the distribution over time for duplicates. We have 
> difficulty determining which one is the right one (as they are different) in 
> order to clean them up.
> We are also not the only ones encountering this as you can in the linked 
> issue.
> We have noticed that Atlas does not use the 
> [locking|https://docs.janusgraph.org/master/advanced-topics/eventual-consistency/]
>  mechanism of Janus to prevent this:
>  
> !zrzut_ekranu_2019-09-03_o_10.28.50.png!



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

[jira] [Commented] (ATLAS-3398) Duplicates for unique attributes

[Ashutosh Mestry (Jira)]

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

Ashutosh Mestry commented on ATLAS-3398:


[~dwarszawski] I am not able to assign this issue to you. Your name does not 
show up in the list for some reason. I have assigned it to me for tracking. 
Hope that is OK.

> Duplicates for unique attributes 
> -
>
> Key: ATLAS-3398
> URL: https://issues.apache.org/jira/browse/ATLAS-3398
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0, trunk
>Reporter: Bolke de Bruin
>Assignee: Ashutosh Mestry
>Priority: Blocker
>  Labels: integrity
> Attachments: zrzut_ekranu_2019-09-03_o_10.28.50.png
>
>
> We are seeing issues with entities being added to Atlas with duplicate 
> "qualifiedName". The guids differ and other attributes do also differ. Below 
> a graph that shows the distribution over time for duplicates. We have 
> difficulty determining which one is the right one (as they are different) in 
> order to clean them up.
> We are also not the only ones encountering this as you can in the linked 
> issue.
> We have noticed that Atlas does not use the 
> [locking|https://docs.janusgraph.org/master/advanced-topics/eventual-consistency/]
>  mechanism of Janus to prevent this:
>  
> !zrzut_ekranu_2019-09-03_o_10.28.50.png!



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

[jira] [Resolved] (ATLAS-3398) Duplicates for unique attributes

[Ashutosh Mestry (Jira)]

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

Ashutosh Mestry resolved ATLAS-3398.

Resolution: Fixed

> Duplicates for unique attributes 
> -
>
> Key: ATLAS-3398
> URL: https://issues.apache.org/jira/browse/ATLAS-3398
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0, trunk
>Reporter: Bolke de Bruin
>Assignee: Ashutosh Mestry
>Priority: Blocker
>  Labels: integrity
> Attachments: zrzut_ekranu_2019-09-03_o_10.28.50.png
>
>
> We are seeing issues with entities being added to Atlas with duplicate 
> "qualifiedName". The guids differ and other attributes do also differ. Below 
> a graph that shows the distribution over time for duplicates. We have 
> difficulty determining which one is the right one (as they are different) in 
> order to clean them up.
> We are also not the only ones encountering this as you can in the linked 
> issue.
> We have noticed that Atlas does not use the 
> [locking|https://docs.janusgraph.org/master/advanced-topics/eventual-consistency/]
>  mechanism of Janus to prevent this:
>  
> !zrzut_ekranu_2019-09-03_o_10.28.50.png!



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

Re: Review Request 72666: Notification: Solution to Memory Build-up

[Ashutosh Mestry via Review Board]

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

(Updated July 31, 2020, 3:57 p.m.)


Review request for atlas, Madhan Neethiraj, Nikhil Bonte, Nixon Rodrigues, and 
Sarath Subramanian.


Changes
---

Updates include: Addressed review comments.


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


Repository: atlas


Description
---

**Background**
See JIRA for details.

*Analysis* Using memory profiling tools, it was observed that large number of 
notification objects were created. These stayed in memory and later were 
promoted to higher generation, thereby taking even longer to be collected.

**Approach**
Using the fixed-buffer approach to address the problem of creating large number 
of small objects.

New *FixedBufferList* This is an encapsulation over *ArrayList*. During initial 
allocation, list is populated with default values. Features:
- Setting of values to these pre-allocated objects is achieved by first doing a 
*get* on the element and then assigning values to it.
- *toList* fetches the sub-list from the encapsulating list. This uses the 
state within the class to fetch the right length for the returning array.

New *NamedFixedBufferList* Maintains a per-thread *FixedBufferList*. This is 
necessary since the list is now part class's state.
Modified *EntityAuditListenerV2* Uses the new classes.
Modifed *EntityNotificationListener* Uses the new classes.

**Verification**
- Using the test setup, the memory usage was observed over a period of 24 hrs. 
- Memory usage and object allocation was obvserved using memory profiler.


Diffs (updated)
-

  intg/src/main/java/org/apache/atlas/AtlasConfiguration.java a942b9f93 
  intg/src/main/java/org/apache/atlas/model/Clearable.java PRE-CREATION 
  intg/src/main/java/org/apache/atlas/model/audit/EntityAuditEventV2.java 
63116d467 
  intg/src/main/java/org/apache/atlas/utils/FixedBufferList.java PRE-CREATION 
  intg/src/test/java/org/apache/atlas/utils/FixedBufferListTest.java 
PRE-CREATION 
  
repository/src/main/java/org/apache/atlas/repository/audit/EntityAuditListenerV2.java
 79527acfa 


Diff: https://reviews.apache.org/r/72666/diff/12/

Changes: https://reviews.apache.org/r/72666/diff/11-12/


Testing (updated)
---

**Unit testing**
Unit tests added for the new classes.

**Volume testing**
Setup:
- Node: Threads 40, Core: 40, Allocated Memory: 12 GB
- Multiple Kafka queues ingesting data.
- Bulk entity creation using custom script ingesting 100M entities.

Memory usage stayed between 0 and 5% during the 24 hr period.

With:
- Workers: 64
- Batch size: 50 (fewer elements in batch improve commit time and audit write 
time).
- Throughput: ~1.2 M entities per hour. Without out of memory error.

**Pre-commit**
https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/2035/
https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/2067/
https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/2076/


Thanks,

Ashutosh Mestry

Re: Review Request 72666: Notification: Solution to Memory Build-up

[Ashutosh Mestry via Review Board]

> On July 30, 2020, 11:58 p.m., Sarath Subramanian wrote:
> > good memory improvement fix!

Thanks!


- Ashutosh


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


On July 30, 2020, 10:58 p.m., Ashutosh Mestry wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/72666/
> ---
> 
> (Updated July 30, 2020, 10:58 p.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj, Nikhil Bonte, Nixon Rodrigues, 
> and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-3878
> https://issues.apache.org/jira/browse/ATLAS-3878
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> **Background**
> See JIRA for details.
> 
> *Analysis* Using memory profiling tools, it was observed that large number of 
> notification objects were created. These stayed in memory and later were 
> promoted to higher generation, thereby taking even longer to be collected.
> 
> **Approach**
> Using the fixed-buffer approach to address the problem of creating large 
> number of small objects.
> 
> New *FixedBufferList* This is an encapsulation over *ArrayList*. During 
> initial allocation, list is populated with default values. Features:
> - Setting of values to these pre-allocated objects is achieved by first doing 
> a *get* on the element and then assigning values to it.
> - *toList* fetches the sub-list from the encapsulating list. This uses the 
> state within the class to fetch the right length for the returning array.
> 
> New *NamedFixedBufferList* Maintains a per-thread *FixedBufferList*. This is 
> necessary since the list is now part class's state.
> Modified *EntityAuditListenerV2* Uses the new classes.
> Modifed *EntityNotificationListener* Uses the new classes.
> 
> **Verification**
> - Using the test setup, the memory usage was observed over a period of 24 
> hrs. 
> - Memory usage and object allocation was obvserved using memory profiler.
> 
> 
> Diffs
> -
> 
>   intg/src/main/java/org/apache/atlas/AtlasConfiguration.java 2c007ca01 
>   intg/src/main/java/org/apache/atlas/model/Clearable.java PRE-CREATION 
>   intg/src/main/java/org/apache/atlas/model/audit/EntityAuditEventV2.java 
> 63116d467 
>   intg/src/main/java/org/apache/atlas/utils/FixedBufferList.java PRE-CREATION 
>   intg/src/test/java/org/apache/atlas/utils/FixedBufferListTest.java 
> PRE-CREATION 
>   
> repository/src/main/java/org/apache/atlas/repository/audit/EntityAuditListenerV2.java
>  79527acfa 
> 
> 
> Diff: https://reviews.apache.org/r/72666/diff/11/
> 
> 
> Testing
> ---
> 
> **Unit testing**
> Unit tests added for the new classes.
> 
> **Volume testing**
> Setup:
> - Node: Threads 40, Core: 40, Allocated Memory: 12 GB
> - Multiple Kafka queues ingesting data.
> - Bulk entity creation using custom script ingesting 100M entities.
> 
> Memory usage stayed between 0 and 5% during the 24 hr period.
> 
> With:
> - Workers: 64
> - Batch size: 50 (fewer elements in batch improve commit time and audit write 
> time).
> - Throughput: ~1.2 M entities per hour. Without out of memory error.
> 
> **Pre-commit**
> https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/2035/
> https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/2067/
> 
> 
> Thanks,
> 
> Ashutosh Mestry
> 
>

Re: Review Request 72646: ATLAS-3876 : Relationship Search API not showing correct approximateCount

[Pinal Shah]

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

(Updated July 31, 2020, 12:43 p.m.)


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


Changes
---

Addressed review comment


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


Repository: atlas


Description
---

**Issue:**
Relationship api doesn't provide approximate count of the related entities in 
the response.

**Workaround:**
Get the total count of related given entity , irrespective of the offset/limit.
Added 'getApproximateCount' as queryParam in Rest api.


Also this patch includes **improvement in the time taken to fetch related 
entities**  .
Average time taken for the Api to search relationship entities having **5000 
end vertices** with limit **500**:
Before: 9seconds
After applying this patch : 3seconds


Diffs (updated)
-

  intg/src/main/java/org/apache/atlas/type/AtlasEntityType.java 58de4cc47 
  intg/src/main/java/org/apache/atlas/type/AtlasStructType.java 61ee4589f 
  
repository/src/main/java/org/apache/atlas/discovery/AtlasDiscoveryService.java 
86572598a 
  
repository/src/main/java/org/apache/atlas/discovery/EntityDiscoveryService.java 
4b9564295 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphRetriever.java
 863a00350 
  repository/src/main/java/org/apache/atlas/util/SearchPredicateUtil.java 
5069d78c8 
  webapp/src/main/java/org/apache/atlas/web/rest/DiscoveryREST.java cdeb912a4 


Diff: https://reviews.apache.org/r/72646/diff/4/

Changes: https://reviews.apache.org/r/72646/diff/3-4/


Testing
---

Manually tested
Precommit : https://builds.apache.org/job/PreCommit-ATLAS-Build-Test/2011 
(Failed in Impala build)


Thanks,

Pinal Shah

Re: Review Request 72713: ATLAS-3892 : Basic search enhanced Feature - Search history

[chaitali]

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

(Updated July 31, 2020, 12:34 p.m.)


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


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


Repository: atlas


Description
---

1.This patch implements the search history feature where from UI we will 
receive below filters.
2.In backend we have introduced a new operator "TIME_RANGE" where all the below 
7 attribute values will have TIME_RANGE operator.
3.There will be a slight change in the JSON where previously we were passing 
the Attribute value in Search parameters from the UI but for below filters   we 
will not pass any attributeValue except for "custom range" filter we provide 
attribute value 
  for eg ;"attributeValue":"159354180,159544260" .

New 7 filters :

1.last 7 days.
2.Last month.
3.Last 30 days.
4.Today.
5.Yesterday.
6.Custom Range.
7.This Month.


Diffs (updated)
-

  common/src/main/java/org/apache/atlas/repository/Constants.java a71787bc0 
  intg/src/main/java/org/apache/atlas/model/discovery/SearchParameters.java 
fcc4494f2 
  repository/src/main/java/org/apache/atlas/discovery/SearchProcessor.java 
c9a605355 
  repository/src/main/java/org/apache/atlas/util/SearchPredicateUtil.java 
5069d78c8 
  
repository/src/test/java/org/apache/atlas/discovery/EntitySearchProcessorTest.java
 8e42d1700 


Diff: https://reviews.apache.org/r/72713/diff/6/

Changes: https://reviews.apache.org/r/72713/diff/5-6/


Testing
---

Tested with below json: 
eg : 
{
  "excludeDeletedEntities": true,
  "includeSubClassifications": true,
  "includeSubTypes": true,
  "includeClassificationAttributes": true,
  "entityFilters": {
"condition": "AND",
"criterion": [
  {
"attributeName": "__timestamp",
"operator": "TIME_RANGE",
"attributeValue": "YESTERDAY"
  }
]
  },
  "tagFilters": null,
  "attributes": [
"__timestamp"
  ],
  "limit": 25,
  "offset": 0,
  "typeName": "hdfs_path",
  "classification": null,
  "termName": null
}
eg: Only For custom range filter we provide attribute value.
{
  "excludeDeletedEntities": true,
  "includeSubClassifications": true,
  "includeSubTypes": true,
  "includeClassificationAttributes": true,
  "entityFilters": {
"condition": "AND",
"criterion": [
  {
"attributeName": "__timestamp",
"operator": "TIME_RANGE",
"attributeValue": "1595956315473,159596100"
  }
]
  },
  "tagFilters": null,
  "attributes": [
"__timestamp"
  ],
  "limit": 25,
  "offset": 0,
  "typeName": "Table",
  "classification": null,
  "termName": null
}

* Added Test cases to check new processDateRange method functionality


Thanks,

chaitali

[jira] [Commented] (ATLAS-3906) “NoSuchMethodErrors” due to multiple versions of org.apache.curator:curator-client:jar

[Bing-ok (Jira)]

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

Bing-ok commented on ATLAS-3906:


[~nixon] Could you help me review this issue? Thx :P 

> “NoSuchMethodErrors” due to multiple versions of 
> org.apache.curator:curator-client:jar
> --
>
> Key: ATLAS-3906
> URL: https://issues.apache.org/jira/browse/ATLAS-3906
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Bing-ok
>Priority: Major
>
> Hi, there are multiple versions of _*org.apache.curator:curator-client*_ in 
> _*atlas/server-api*_. As shown in the following dependency tree, according to 
> Maven's “nearest wins” strategy, only 
> _*org.apache.curator:curator-client:4.0.1*_ can be loaded, 
> _*org.apache.curator:curator-client:2.12.0*_ will be shadowed.
> As _*org.apache.curator:curator-client:2.12.0*_ has not been loaded during 
> the building process, several methods are missing. However, the missing 
> methods:
> 1. _*org.codelibs.core.lang.StringUtil: java.lang.String 
> newStringUnsafe(char[])*_
> {noformat}
> paths--
>  getEntity(java.lang.String)> atlas\server-api\target\classes
>  java.lang.Object get(java.lang.Object)> 
> Repositories\org\apache\curator\curator-client\4.0.1\curator-client-4.0.1.jar
>  apply(java.lang.Object)> 
> Repositories\org\apache\curator\curator-framework\4.0.1\curator-framework-4.0.1.jar
>  apply(org.apache.curator.framework.api.CuratorListener)> 
> Repositories\org\apache\curator\curator-framework\4.0.1\curator-framework-4.0.1.jar
>  checkInterrupted(java.lang.Throwable)>{noformat}
>  
> The above missing methods are actually referenced by _*atlas/server-api*_, 
> which will cause “NoSuchMethodErrors” at runtime.
> Suggested fixing solutions:
> 1. Upgrade dependency *_org.apache.hadoop:hadoop-common_* from _*3.1.1*_ to 
> *_3.3.0_*. Because one conflicting library version 
> _*org.apache.curator:curator-client:2.12.0*_ is transitively introduced by 
> *_org.apache.hadoop:hadoop-common:3.1.1_*. Upgrading dependency 
> *_org.apache.hadoop:hadoop-common_* from _*3.1.1*_ to *_3.3.0_* can solve 
> this dependency conflict. 
> 2. Directly declare dependency _*org.apache.curator:curator-client:2.12.0*_.
> 3. Use configuration attribute  to unify the version of 
> library _*org.apache.curator:curator-client*_ to be _*2.12.0*_ in 
> _*atlas/server-api*_'s pom file.
> Please let me know which solution do you prefer? I can submit a PR to fix it.
> Thank you very much for your attention.
> Best regards,
> Dependency tree
> [INFO] org.apache.atlas:atlas-server-api:jar:3.0.0-SNAPSHOT
> [INFO] \- org.apache.hadoop:hadoop-common:jar:3.1.1:compile
> [INFO] +- org.apache.hadoop:hadoop-auth:jar:3.1.1:compile
> [INFO] | \- org.apache.curator:curator-framework:jar:4.0.1:compile (version 
> managed from 2.12.0)
> [INFO] | \- _*(org.apache.curator:curator-client:jar:4.0.1:compile - version 
> managed from 2.12.0; omitted for duplicate)*_
> [INFO] \- _*org.apache.curator:curator-client:jar:4.0.1:compile*_
> 



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

Re: Review Request 72477: ATLAS-3583 Use Audit framework to generate audit entries for TypeDefs CREATE, UPDATE and DELETE

[Mandar Ambawane]

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

(Updated July 31, 2020, 12:01 p.m.)


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


Changes
---

Changes to create single audit entry when multiple typedefs of different 
categories are created in a single request


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


Repository: atlas


Description
---

ATLAS-3583 Use Audit framework to generate audit entries for TypeDefs CREATE, 
UPDATE and DELETE


Diffs (updated)
-

  addons/models/-Area0/0010-base_model.json 9777b7a 
  
addons/models/-Area0/patches/006-base_model_add_atlas_operation_attributes.json
 PRE-CREATION 
  intg/src/main/java/org/apache/atlas/model/audit/AtlasAuditEntry.java a95cf4e 
  intg/src/main/java/org/apache/atlas/model/audit/AuditSearchParameters.java 
9120062 
  intg/src/test/java/org/apache/atlas/TestUtilsV2.java 2b9cf6e 
  
repository/src/main/java/org/apache/atlas/repository/audit/AtlasAuditService.java
 a0dc816 
  
repository/src/main/java/org/apache/atlas/repository/audit/TypeDefAuditListener.java
 PRE-CREATION 
  
repository/src/main/java/org/apache/atlas/repository/store/bootstrap/AtlasTypeDefStoreInitializer.java
 8e7c1b3 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/AtlasTypeDefGraphStore.java
 79f5270 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasEntityChangeNotifier.java
 0dc3193 
  repository/src/test/java/org/apache/atlas/TestModules.java a298934 
  webapp/src/test/java/org/apache/atlas/web/adapters/TestTypeDefsREST.java 
PRE-CREATION 


Diff: https://reviews.apache.org/r/72477/diff/5/

Changes: https://reviews.apache.org/r/72477/diff/4-5/


Testing
---

Basic testing is done.

Pre-commit: 
https://builds.apache.org/job/PreCommit-ATLAS-Build-Test/1871/console

Pre-commit: 
https://builds.apache.org/job/PreCommit-ATLAS-Build-Test/1885/console

Pre-commit: 
https://builds.apache.org/job/PreCommit-ATLAS-Build-Test/1888/console

Pre-commit: 
https://builds.apache.org/job/PreCommit-ATLAS-Build-Test/2071/console


Thanks,

Mandar Ambawane

Re: Review Request 72644: ATLAS-3872 Restrict typedef creation when a child type attribute conflicts with parent type attribute of same name

[Mandar Ambawane]

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

(Updated July 31, 2020, 11:56 a.m.)


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


Changes
---

Addressed review comments


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


Repository: atlas


Description
---

Cause of the problem:
Type-def Column is created by quick-start script.

Here in this case, Type-def Column has the attribute "name". And it has 
property isOptional = true

Type-def Column is a child of Type-def Asset which also has the attribute 
"name". And it has property isOptional = false

Now while creating Entity of Type-def Column from UI, it does not show 
attribute "name" in the mandatory fields because for Type-def Column its 
property isOptional = true

But while validating the attributes from server side we iterate through all the 
attributes of Entity type (Including Parent's attributes)
In this case, while validating Type-def Asset's attribute "name" (which has 
property isOptional = false) we get an error because its value is sent as 
"null" from UI side.


Diffs (updated)
-

  intg/src/main/java/org/apache/atlas/AtlasErrorCode.java a14e43a 
  intg/src/main/java/org/apache/atlas/type/AtlasClassificationType.java e0843cb 
  intg/src/main/java/org/apache/atlas/type/AtlasEntityType.java 58de4cc 
  intg/src/main/java/org/apache/atlas/type/AtlasStructType.java 61ee458 
  repository/src/test/resources/sales-v1-full.zip 
07afbf6ecae312a840b54cae5ab01335c513d180 
  webapp/src/main/java/org/apache/atlas/examples/QuickStart.java 82a9f5c 
  webapp/src/main/java/org/apache/atlas/examples/QuickStartV2.java d5cf9b7 
  webapp/src/test/java/org/apache/atlas/web/integration/BaseResourceIT.java 
6db6b58 
  
webapp/src/test/java/org/apache/atlas/web/integration/TypesJerseyResourceIT.java
 7c820e7 


Diff: https://reviews.apache.org/r/72644/diff/4/

Changes: https://reviews.apache.org/r/72644/diff/3-4/


Testing
---

PreCommit: https://builds.apache.org/job/PreCommit-ATLAS-Build-Test/2007/console

PreCommit: https://builds.apache.org/job/PreCommit-ATLAS-Build-Test/2014/console


Thanks,

Mandar Ambawane

[GitHub] [atlas] Aka-shi commented on pull request #101: add-dist-cassandra-elasticsearch-profile and support GS

[GitBox]

Aka-shi commented on pull request #101:
URL: https://github.com/apache/atlas/pull/101#issuecomment-667081617


   @mohamed-a-abdelaziz any idea what are the steps required to run atlas with 
local cassandra and local elastic search? Don't seem to find anything in docs. 



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org