- Couchbase\r
- Elasticsearch and Kibana\r
- HDFS\r
+\r
Depending on demands, new systems may be added to the supported list. In the following we use the term database for the storage, \r
even though HDFS is a file system (but with simple settings, it can be treats as a database, e.g. Hive.)\r
\r
\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, \r
- Admin UI also use this API to start/stop Feeder, query Feeder status and statistics.\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 data processing features. Before persisting data, data can be massaged in Feeder. \r
- Currently two features are implemented: Correlate Cleared Message (in org.onap.datalake.feeder.service.db.ElasticsearchService) \r
- and Flatten JSON Array (org.onap.datalake.feeder.service.StoreService). \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
\r