From: Niranjana Date: Fri, 7 May 2021 05:48:09 +0000 (+0530) Subject: Update database change in datalake-handler documentation X-Git-Url: https://gerrit.onap.org/r/gitweb?a=commitdiff_plain;h=refs%2Fchanges%2F50%2F121150%2F1;p=dcaegen2.git Update database change in datalake-handler documentation Issue-ID: DCAEGEN2-2329 Signed-off-by: Niranjana Change-Id: Ia942d2086fd4dea28c91bc39743ed588c73eba77 --- diff --git a/docs/sections/services/datalake-handler/DL-DES.PNG b/docs/sections/services/datalake-handler/DL-DES.PNG index ca3f4192..bd65f85e 100644 Binary files a/docs/sections/services/datalake-handler/DL-DES.PNG and b/docs/sections/services/datalake-handler/DL-DES.PNG differ diff --git a/docs/sections/services/datalake-handler/des-arch.PNG b/docs/sections/services/datalake-handler/des-arch.PNG index 02ffd648..52fbc46e 100644 Binary files a/docs/sections/services/datalake-handler/des-arch.PNG and b/docs/sections/services/datalake-handler/des-arch.PNG differ diff --git a/docs/sections/services/datalake-handler/feeder-arch.PNG b/docs/sections/services/datalake-handler/feeder-arch.PNG index cb995fac..596a2d19 100644 Binary files a/docs/sections/services/datalake-handler/feeder-arch.PNG and b/docs/sections/services/datalake-handler/feeder-arch.PNG differ diff --git a/docs/sections/services/datalake-handler/installation.rst b/docs/sections/services/datalake-handler/installation.rst index 00b01d5e..e9215c29 100644 --- a/docs/sections/services/datalake-handler/installation.rst +++ b/docs/sections/services/datalake-handler/installation.rst @@ -9,7 +9,7 @@ DL-handler consists of three pods- the feeder, admin UI and des. It can be deplo Pre-requisite ------------- -Make sure mariadb-galera from OOM is properly deployed and functional. +Make sure dcae postgres is properly deployed and functional. An external database, such as Elasticsearch and MongoDB is deployed. Install mongodb through the following command. #docker run -itd --restart=always --name dl-mongo -p 27017:27017 mongo diff --git a/docs/sections/services/datalake-handler/overview.rst b/docs/sections/services/datalake-handler/overview.rst index 101cb46b..fc14f995 100644 --- a/docs/sections/services/datalake-handler/overview.rst +++ b/docs/sections/services/datalake-handler/overview.rst @@ -49,7 +49,7 @@ A system administrator uses DataLake Admin UI to: - Configure which Topics to monitor, which databases to store the data for each Topic. - Pre-configured 3rd Party Tools dashboards and templates. -This UI tool is used to manage all the Dayalake settings stored in MariaDB. Here is the database schema: +This UI tool is used to manage all the Dayalake settings stored in postgres. Here is the database schema: .. image:: ./dbschema.PNG @@ -62,8 +62,8 @@ Features - Read data directly from Kafka for performance. - Support for pluggable databases. To add a new database, we only need to implement its corrosponding service. - - Support REST API for inter-component communications. Besides managing DatAlake settings in MariaDB, Admin UI also use this API to start/stop Feeder, query Feeder status and statistics. - - Use MariaDB to store settings. + - Support REST API for inter-component communications. Besides managing DatAlake settings in postgres, Admin UI also use this API to start/stop Feeder, query Feeder status and statistics. + - Use postgres to store settings. - Support data processing features. Before persisting data, data can be massaged in Feeder. Currently two features are implemented: Correlate Cleared Message (in org.onap.datalake.feeder.service.db.ElasticsearchService) and Flatten JSON Array (org.onap.datalake.feeder.service.StoreService). - Connection to Kafka and DBs are secured