Merge pull request #1704 from ilianiliev-redis/RDSC-3787-removel-all-mentions-of-server-name

RDSC-3787 Remove all mentions of server name

Author: andy-stark-redis

content/integrate/redis-data-integration/data-pipelines/data-denormalization.md

@@ -117,7 +117,6 @@ To configure normalization, you must first configure the parent entity to use JS
 ```yaml
 # jobs/invoice.yaml
 source:
-  server_name: chinook
   schema: public
   table: Invoice
 
@@ -138,15 +137,13 @@ After you have configured the parent entity, you can then configure the child en
 ```yaml
 # jobs/invoice_line.yaml
 source:
-  server_name: chinook
   schema: public
   table: InvoiceLine
 output:
   - uses: redis.write
     with:
       nest: # cannot co-exist with other parameters such as 'key'
         parent:
-          # server_name: chinook
           # schema: public
           table: Invoice
         nesting_key: InvoiceLineId # the unique key in the composite structure under which the child data will be stored
@@ -161,10 +158,8 @@ output:
 The job has a `with` section under `output` that includes the `nest` block.
 The job must include the following attributes in the `nest` block:
 
-- `parent`: This specifies the RDI data stream for the parent entities. Typically, you only
-  need to supply the parent `table` name, unless you are nesting children under a parent that comes from
-  a different source database. If you do this then you must also specify `server_name` and
-  `schema` attributes. Note that this attribute refers to a Redis *key* that will be added to the target
+- `parent`: This specifies the config of the parent entities. You only
+  need to supply the parent `table` name. Note that this attribute refers to a Redis *key* that will be added to the target
   database, not to a table you can access from the pipeline. See [Using nesting](#using-nesting) below
   for the format of the key that is generated.
 - `nesting_key`: The unique key of each child entry in the JSON map that will be created under the path.

content/integrate/redis-data-integration/data-pipelines/transform-examples/redis-hash-example.md

@@ -24,7 +24,6 @@ If you don't supply an `expire` parameter, the keys will never expire.
 
 ```yaml
 source:
-  server_name: chinook
   schema: public
   table: invoice
 output:
@@ -36,4 +35,4 @@ output:
         expression: concat(['invoice_id:', InvoiceId])
         language: jmespath
       expire: 100
-```
+```

content/integrate/redis-data-integration/data-pipelines/transform-examples/redis-json-example.md

@@ -29,7 +29,6 @@ In this case, the result will be Redis JSON documents with key names based on th
 
 ```yaml
 source:
-  server_name: chinook
   schema: public
   table: invoice
 output:
@@ -42,4 +41,4 @@ output:
         language: jmespath
       on_update: replace        
       expire: 100
-```
+```

content/integrate/redis-data-integration/data-pipelines/transform-examples/redis-set-example.md

@@ -23,7 +23,6 @@ When writing to a set, you must supply an extra argument, `member`, which specif
 
 ```yaml
 source:
-  server_name: chinook
   schema: public
   table: invoice
 output:
@@ -37,4 +36,4 @@ output:
       args:
         member: InvoiceId
       expire: 100
-```
+```

content/integrate/redis-data-integration/data-pipelines/transform-examples/redis-set-key-name.md

@@ -47,7 +47,6 @@ To customize key names, use the `key` section within the `redis.write` output co
 
 ```yaml
 source:
-  server_name: rdi
   db: inventory
   table: customers
 output:
@@ -64,7 +63,6 @@ When working with the full row format, you need to handle key generation differe
 
 ```yaml
 source:
-  server_name: rdi
   db: inventory
   table: customers
   row_format: full

content/integrate/redis-data-integration/data-pipelines/transform-examples/redis-sorted-set-example.md

@@ -23,7 +23,6 @@ When writing to sorted sets, you must provide two additional arguments, `member`
 
 ```yaml
 source:
-  server_name: chinook
   schema: public
   table: invoice
 output:
@@ -44,4 +43,4 @@ Since sorted sets in Redis are inherently sorted, you can easily get the top N i
 
 ```
 ZREVRANGE invoices:sorted 0 9 WITHSCORES
-```
+```

content/integrate/redis-data-integration/data-pipelines/transform-examples/redis-stream-example.md

@@ -29,7 +29,6 @@ In the example, only three original fields are passed in the message payload: `I
 
 ```yaml
 source:
-  server_name: chinook
   schema: public
   table: invoice
 output:
@@ -45,4 +44,4 @@ output:
         - BillingCountry: country
         - Total
       expire: 100
-```
+```

content/integrate/redis-data-integration/data-pipelines/transform-examples/redis-string-example.md

@@ -35,7 +35,6 @@ If you don't supply an `expire` parameter, the keys will never expire.
 
 ```yaml
 source:
-  server_name: chinook
   table: album
   row_format: full
 output:
@@ -49,4 +48,4 @@ output:
       args:
         value: title
       expire: 86400
-```
+```