Update database change in datalake-handler documentation

[dcaegen2.git] / docs / sections / services / datalake-handler / overview.rst

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