Update database change in datalake-handler documentation

Issue-ID: DCAEGEN2-2329
Signed-off-by: Niranjana <niranjana.y60@wipro.com>
Change-Id: Ia942d2086fd4dea28c91bc39743ed588c73eba77

diff --git a/docs/sections/services/datalake-handler/DL-DES.PNG b/docs/sections/services/datalake-handler/DL-DES.PNG
index ca3f419..bd65f85 100644 (file)
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 02ffd64..52fbc46 100644 (file)
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 cb995fa..596a2d1 100644 (file)
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 00b01d5..e9215c2 100644 (file)
--- 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 101cb46..fc14f99 100644 (file)
--- 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.\r
   - Pre-configured 3rd Party Tools dashboards and templates.\r
 \r
-This UI tool is used to manage all the Dayalake settings stored in MariaDB. Here is the database schema:\r
+This UI tool is used to manage all the Dayalake settings stored in postgres. Here is the database schema:\r
 \r
 .. image:: ./dbschema.PNG\r
 \r
@@ -62,8 +62,8 @@ Features
 \r
    - Read data directly from Kafka for performance.\r
    - Support for pluggable databases. To add a new database, we only need to implement its corrosponding service.\r
-   - 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.\r
-   - Use MariaDB to store settings.\r
+   - 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.\r
+   - Use postgres to store settings.\r
    - 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).\r
    - Connection to Kafka and DBs are secured\r
 \r