summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/sections/services/datalake-handler/DL-DES.PNGbin27448 -> 308396 bytes
-rw-r--r--docs/sections/services/datalake-handler/des-arch.PNGbin30922 -> 292252 bytes
-rw-r--r--docs/sections/services/datalake-handler/feeder-arch.PNGbin64492 -> 345921 bytes
-rw-r--r--docs/sections/services/datalake-handler/installation.rst2
-rw-r--r--docs/sections/services/datalake-handler/overview.rst6
5 files changed, 4 insertions, 4 deletions
diff --git a/docs/sections/services/datalake-handler/DL-DES.PNG b/docs/sections/services/datalake-handler/DL-DES.PNG
index ca3f4192..bd65f85e 100644
--- a/docs/sections/services/datalake-handler/DL-DES.PNG
+++ b/docs/sections/services/datalake-handler/DL-DES.PNG
Binary files 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
--- a/docs/sections/services/datalake-handler/des-arch.PNG
+++ b/docs/sections/services/datalake-handler/des-arch.PNG
Binary files 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
--- a/docs/sections/services/datalake-handler/feeder-arch.PNG
+++ b/docs/sections/services/datalake-handler/feeder-arch.PNG
Binary files 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