\r
Description\r
~~~~~~~~~~~\r
-DataLate Handler's main function is to monitor and persist data flow through DMaaP. The databases are outside of ONAP scope, \r
+DataLake Handler's main function is to monitor and persist data flow through DMaaP and provide a query API for other component or external services. The databases are outside of ONAP scope, \r
since the data is expected to be huge, and a database may be a complicated cluster consisting of thousand of nodes.\r
\r
Admin UI\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
+Des\r
+~~~\r
+Architecture\r
+.. image:: ./des-arch.PNG\r
+\r
+Features\r
+\r
+ - Provide a data query API for other components to consume.\r
+ - Integrate with Presto to do data query via sql template.\r
\r
Links\r
~~~~~\r
- DataLake Development Environment Setup https://wiki.onap.org/display/DW/DataLake+Development+Environment+Setup\r
+ - Des description and deployment steps: https://wiki.onap.org/display/DW/DES\r
- Source Code https://gerrit.onap.org/r/gitweb?p=dcaegen2/services.git;a=tree;f=components/datalake-handler;hb=HEAD\r