Skip to content

Commit edc6b2e

Browse files
committed
Add extenstion docs and refactor docker tests
1 parent 6c5d690 commit edc6b2e

File tree

2 files changed

+17
-17
lines changed

2 files changed

+17
-17
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,7 @@ The next table outlines CMAKE flags that correspond with MiNiFi extensions. Exte
7575
| AWS | [AWSCredentialsService](CONTROLLERS.md#awscredentialsservice)<br/>[PutS3Object](PROCESSORS.md#puts3object)<br/>[DeleteS3Object](PROCESSORS.md#deletes3object)<br/>[FetchS3Object](PROCESSORS.md#fetchs3object)<br/>[ListS3](PROCESSORS.md#lists3) | -DENABLE_AWS=ON |
7676
| Azure | [AzureStorageCredentialsService](CONTROLLERS.md#azurestoragecredentialsservice)<br/>[PutAzureBlobStorage](PROCESSORS.md#putazureblobstorage)<br/>[DeleteAzureBlobStorage](PROCESSORS.md#deleteazureblobstorage)<br/>[FetchAzureBlobStorage](PROCESSORS.md#fetchazureblobstorage)<br/>[ListAzureBlobStorage](PROCESSORS.md#listazureblobstorage)<br/>[PutAzureDataLakeStorage](PROCESSORS.md#putazuredatalakestorage)<br/>[DeleteAzureDataLakeStorage](PROCESSORS.md#deleteazuredatalakestorage)<br/>[FetchAzureDataLakeStorage](PROCESSORS.md#fetchazuredatalakestorage)<br/>[ListAzureDataLakeStorage](PROCESSORS.md#listazuredatalakestorage) | -DENABLE_AZURE=ON |
7777
| CivetWeb | [ListenHTTP](PROCESSORS.md#listenhttp) | -DENABLE_CIVET=ON |
78-
| Couchbase | [CouchbaseClusterService](CONTROLLERS.md#couchbaseclusterservice)<br/>[PutCouchbaseKey](PROCESSORS.md#putcouchbasekey) | -DENABLE_COUCHBASE=ON |
78+
| Couchbase | [CouchbaseClusterService](CONTROLLERS.md#couchbaseclusterservice)<br/>[PutCouchbaseKey](PROCESSORS.md#putcouchbasekey)<br/>[GetCouchbaseKey](PROCESSORS.md#getcouchbasekey) | -DENABLE_COUCHBASE=ON |
7979
| Elasticsearch | [ElasticsearchCredentialsControllerService](CONTROLLERS.md#elasticsearchcredentialscontrollerservice)<br/>[PostElasticsearch](PROCESSORS.md#postelasticsearch) | -DENABLE_ELASTICSEARCH=ON |
8080
| ExecuteProcess (Linux and macOS) | [ExecuteProcess](PROCESSORS.md#executeprocess) | -DENABLE_EXECUTE_PROCESS=ON |
8181
| Google Cloud Platform | [DeleteGCSObject](PROCESSORS.md#deletegcsobject)<br>[FetchGCSObject](PROCESSORS.md#fetchgcsobject)<br>[GCPCredentialsControllerService](CONTROLLERS.md#gcpcredentialscontrollerservice)<br>[ListGCSBucket](PROCESSORS.md#listgcsbucket)<br>[PutGCSObject](PROCESSORS.md#putgcsobject) | -DENABLE_GCP=ON |

docker/test/integration/features/couchbase.feature

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -67,17 +67,17 @@ Feature: Executing Couchbase operations from MiNiFi-C++
6767
And a document with id "test_doc_id" in bucket "test_bucket" is present with data '{"field1": "value1"}' of type "Binary" in Couchbase
6868

6969
Scenario: A MiNiFi instance can get data from test bucket with GetCouchbaseKey processor
70-
Given a Couchbase server is set up
71-
And a GetFile processor with the "Input Directory" property set to "/tmp/input"
70+
Given a GetFile processor with the "Input Directory" property set to "/tmp/input"
7271
And a file with the content '{"field1": "value1", "field2": "value2"}' is present in '/tmp/input'
7372
And a PutCouchbaseKey processor with the "Bucket Name" property set to "test_bucket"
7473
And the "Document Id" property of the PutCouchbaseKey processor is set to "test_doc_id"
74+
And the "Couchbase Cluster Controller Service" property of the PutCouchbaseKey processor is set to "CouchbaseClusterService"
7575
And a GetCouchbaseKey processor with the "Bucket Name" property set to "test_bucket"
7676
And the "Document Id" property of the GetCouchbaseKey processor is set to "test_doc_id"
77+
And the "Couchbase Cluster Controller Service" property of the GetCouchbaseKey processor is set to "CouchbaseClusterService"
7778
And a PutFile processor with the "Directory" property set to "/tmp/output"
7879
And a LogAttribute processor with the "FlowFiles To Log" property set to "0"
79-
And a CouchbaseClusterService is setup up for PutCouchbaseKey with the name "CouchbaseClusterService"
80-
And a CouchbaseClusterService is setup up for GetCouchbaseKey with the name "CouchbaseClusterService"
80+
And a CouchbaseClusterService is setup up with the name "CouchbaseClusterService"
8181

8282
And the "success" relationship of the GetFile processor is connected to the PutCouchbaseKey
8383
And the "success" relationship of the PutCouchbaseKey processor is connected to the GetCouchbaseKey
@@ -94,19 +94,19 @@ Feature: Executing Couchbase operations from MiNiFi-C++
9494
And the Minifi logs match the following regex: "key:couchbase.doc.expiry value:\d{4}-\d{2}-\d{2} \d{2}:\d{2}:\d{2}\.\d{3}" in less than 1 seconds
9595

9696
Scenario: A MiNiFi instance can get data from test bucket with GetCouchbaseKey processor using binary storage
97-
Given a Couchbase server is set up
98-
And a GetFile processor with the "Input Directory" property set to "/tmp/input"
97+
Given a GetFile processor with the "Input Directory" property set to "/tmp/input"
9998
And a file with the content '{"field1": "value1", "field2": "value2"}' is present in '/tmp/input'
10099
And a PutCouchbaseKey processor with the "Bucket Name" property set to "test_bucket"
101100
And the "Document Id" property of the PutCouchbaseKey processor is set to "test_doc_id"
102101
And the "Document Type" property of the PutCouchbaseKey processor is set to "Binary"
102+
And the "Couchbase Cluster Controller Service" property of the PutCouchbaseKey processor is set to "CouchbaseClusterService"
103103
And a GetCouchbaseKey processor with the "Bucket Name" property set to "test_bucket"
104104
And the "Document Id" property of the GetCouchbaseKey processor is set to "test_doc_id"
105105
And the "Document Type" property of the GetCouchbaseKey processor is set to "Binary"
106+
And the "Couchbase Cluster Controller Service" property of the GetCouchbaseKey processor is set to "CouchbaseClusterService"
106107
And a PutFile processor with the "Directory" property set to "/tmp/output"
107108
And a LogAttribute processor with the "FlowFiles To Log" property set to "0"
108-
And a CouchbaseClusterService is setup up for PutCouchbaseKey with the name "CouchbaseClusterService"
109-
And a CouchbaseClusterService is setup up for GetCouchbaseKey with the name "CouchbaseClusterService"
109+
And a CouchbaseClusterService is setup up with the name "CouchbaseClusterService"
110110

111111
And the "success" relationship of the GetFile processor is connected to the PutCouchbaseKey
112112
And the "success" relationship of the PutCouchbaseKey processor is connected to the GetCouchbaseKey
@@ -123,20 +123,20 @@ Feature: Executing Couchbase operations from MiNiFi-C++
123123
And the Minifi logs match the following regex: "key:couchbase.doc.expiry value:\d{4}-\d{2}-\d{2} \d{2}:\d{2}:\d{2}\.\d{3}" in less than 1 seconds
124124

125125
Scenario: A MiNiFi instance can get data from test bucket with GetCouchbaseKey processor and put the result in an attribute
126-
Given a Couchbase server is set up
127-
And a GetFile processor with the "Input Directory" property set to "/tmp/input"
126+
Given a GetFile processor with the "Input Directory" property set to "/tmp/input"
128127
And a file with the content '{"field1": "value1", "field2": "value2"}' is present in '/tmp/input'
129128
And a PutCouchbaseKey processor with the "Bucket Name" property set to "test_bucket"
130129
And the "Document Id" property of the PutCouchbaseKey processor is set to "test_doc_id"
131130
And the "Document Type" property of the PutCouchbaseKey processor is set to "String"
131+
And the "Couchbase Cluster Controller Service" property of the PutCouchbaseKey processor is set to "CouchbaseClusterService"
132132
And a GetCouchbaseKey processor with the "Bucket Name" property set to "test_bucket"
133133
And the "Document Id" property of the GetCouchbaseKey processor is set to "test_doc_id"
134134
And the "Document Type" property of the GetCouchbaseKey processor is set to "String"
135+
And the "Couchbase Cluster Controller Service" property of the GetCouchbaseKey processor is set to "CouchbaseClusterService"
135136
And the "Put Value to Attribute" property of the GetCouchbaseKey processor is set to "get_couchbase_result"
136137
And a PutFile processor with the "Directory" property set to "/tmp/output"
137138
And a LogAttribute processor with the "FlowFiles To Log" property set to "0"
138-
And a CouchbaseClusterService is setup up for PutCouchbaseKey with the name "CouchbaseClusterService"
139-
And a CouchbaseClusterService is setup up for GetCouchbaseKey with the name "CouchbaseClusterService"
139+
And a CouchbaseClusterService is setup up with the name "CouchbaseClusterService"
140140

141141
And the "success" relationship of the GetFile processor is connected to the PutCouchbaseKey
142142
And the "success" relationship of the PutCouchbaseKey processor is connected to the GetCouchbaseKey
@@ -154,17 +154,17 @@ Feature: Executing Couchbase operations from MiNiFi-C++
154154
And the Minifi logs contain the following message: 'key:get_couchbase_result value:{"field1": "value1", "field2": "value2"}' in less than 1 seconds
155155

156156
Scenario: GetCouchbaseKey transfers FlowFile to failure relationship on Couchbase value type mismatch
157-
Given a Couchbase server is set up
158-
And a GetFile processor with the "Input Directory" property set to "/tmp/input"
157+
Given a GetFile processor with the "Input Directory" property set to "/tmp/input"
159158
And a file with the content '{"field1": "value1", "field2": "value2"}' is present in '/tmp/input'
160159
And a PutCouchbaseKey processor with the "Bucket Name" property set to "test_bucket"
161160
And the "Document Id" property of the PutCouchbaseKey processor is set to "test_doc_id"
162161
And the "Document Type" property of the PutCouchbaseKey processor is set to "String"
162+
And the "Couchbase Cluster Controller Service" property of the PutCouchbaseKey processor is set to "CouchbaseClusterService"
163163
And a GetCouchbaseKey processor with the "Bucket Name" property set to "test_bucket"
164164
And the "Document Id" property of the GetCouchbaseKey processor is set to "test_doc_id"
165165
And the "Document Type" property of the GetCouchbaseKey processor is set to "Binary"
166-
And a CouchbaseClusterService is setup up for PutCouchbaseKey with the name "CouchbaseClusterService"
167-
And a CouchbaseClusterService is setup up for GetCouchbaseKey with the name "CouchbaseClusterService"
166+
And the "Couchbase Cluster Controller Service" property of the GetCouchbaseKey processor is set to "CouchbaseClusterService"
167+
And a CouchbaseClusterService is setup up with the name "CouchbaseClusterService"
168168

169169
And the "success" relationship of the GetFile processor is connected to the PutCouchbaseKey
170170
And the "success" relationship of the PutCouchbaseKey processor is connected to the GetCouchbaseKey

0 commit comments

Comments
 (0)