From 313983b8180dd1a1d0fe05b1bebb0c00bc2762b4 Mon Sep 17 00:00:00 2001 From: Jason Fox Date: Fri, 18 Aug 2023 10:40:09 +0200 Subject: [PATCH] Formatting --- docs/historic-context-flume.md | 49 +++--- docs/time-series-data.md | 1 - docs/xacml-access-rules.md | 271 +++++++++++++++++---------------- 3 files changed, 162 insertions(+), 159 deletions(-) diff --git a/docs/historic-context-flume.md b/docs/historic-context-flume.md index c11eb00..8052d5a 100644 --- a/docs/historic-context-flume.md +++ b/docs/historic-context-flume.md @@ -860,7 +860,6 @@ To leave the Postgres client and leave interactive mode, run the following: You will then return to the command-line. - ## ElasticSearch - Persisting Context Data into a Database To persist historic context data into an alternative database such as **ElasticSearch**, we will need an additional @@ -1150,34 +1149,33 @@ curl -X GET 'localhost:9200/_sql?format=json' \ "type": "datetime" } ], - "rows": [ - [ - "TimeInstant", - "DateTime", - "2023-08-14T14:16:48.154Z", - "supportedProtocol", - "Text", - "[\"ul20\"]", - "Motion:001", - "Motion", - "2023-08-14T14:16:48.154Z" - ], - [ - "TimeInstant", - "DateTime", - "2023-08-14T14:16:48.154Z", - "function", - "Text", - "[\"sensing\"]", - "Motion:001", - "Motion", - "2023-08-14T14:16:48.154Z" + "rows": [ + [ + "TimeInstant", + "DateTime", + "2023-08-14T14:16:48.154Z", + "supportedProtocol", + "Text", + "[\"ul20\"]", + "Motion:001", + "Motion", + "2023-08-14T14:16:48.154Z" + ], + [ + "TimeInstant", + "DateTime", + "2023-08-14T14:16:48.154Z", + "function", + "Text", + "[\"sensing\"]", + "Motion:001", + "Motion", + "2023-08-14T14:16:48.154Z" + ] ] - ] } ``` - ## MySQL - Persisting Context Data into a Database Similarly, to persisting historic context data into **MySQL**, we will again need an additional container which hosts @@ -1711,7 +1709,6 @@ same for each database. The response will be **201 - Created**. To read persisted data from the attached databases, please refer to the previous sections of this tutorial. -