Skip to content

Commit d2fe5fb

Browse files
DOC-5282 fixed links in examples
1 parent d3bca28 commit d2fe5fb

File tree

4 files changed

+5
-5
lines changed

4 files changed

+5
-5
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,14 +27,14 @@ transformation.
2727
## Map to a new JSON structure
2828

2929
The first
30-
[job file]({{< relref "/integrate/redis-data-integration/data-pipelines/data-pipelines#job-files" >}})
30+
[job file]({{< relref "/integrate/redis-data-integration/data-pipelines/transform-examples" >}})
3131
example creates a new [JSON]({{< relref "/develop/data-types/json" >}})
3232
object structure to write to the target.
3333
The `source` section selects the `employee` table of the
3434
[`chinook`](https://github.com/Redislabs-Solution-Architects/rdi-quickstart-postgres)
3535
database (the optional `db` value here corresponds to the
3636
`sources.<source-name>.connection.database` value defined in
37-
[`config.yaml`]({{< relref "/integrate/redis-data-integration/data-pipelines/data-pipelines#the-configyaml-file" >}})).
37+
[`config.yaml`]({{< relref "/integrate/redis-data-integration/data-pipelines/pipeline-config" >}})).
3838

3939
In the `transform` section, the `map` transformation uses a [JMESPath](https://jmespath.org/)
4040
expression to specify the new JSON format. (Note that the vertical bar "|" in the `expression`

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ The `source` section selects the `customer` table of the
2929
[`chinook`](https://github.com/Redislabs-Solution-Architects/rdi-quickstart-postgres)
3030
database (the optional `db` value here corresponds to the
3131
`sources.<source-name>.connection.database` value defined in
32-
[`config.yaml`]({{< relref "/integrate/redis-data-integration/data-pipelines/data-pipelines#the-configyaml-file" >}})).
32+
[`config.yaml`]({{< relref "/integrate/redis-data-integration/data-pipelines/pipeline-config" >}})).
3333

3434
In the `transform` section, the `add_field` transformation adds an extra field called `localphone`
3535
to the object, which is created by removing the country and area code from the `phone`

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ The `source` section selects the `employee` table of the
2929
[`chinook`](https://github.com/Redislabs-Solution-Architects/rdi-quickstart-postgres)
3030
database (the optional `db` field here corresponds to the
3131
`sources.<source-name>.connection.database` field defined in
32-
[`config.yaml`]({{< relref "/integrate/redis-data-integration/data-pipelines/data-pipelines#the-configyaml-file" >}})).
32+
[`config.yaml`]({{< relref "/integrate/redis-data-integration/data-pipelines/pipeline-config" >}})).
3333

3434
In the `transform` section, the `remove_field` transformation removes the
3535
`hiredate` field.

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ The `title` is then written to the Redis target database as a string under a cus
2424
form `AlbumTitle:42`, where the `42` is the primary key value of the table (the `albumid` column).
2525

2626
The `connection` is an optional parameter that refers to the corresponding connection name defined in
27-
[`config.yaml`]({{< relref "integrate/redis-data-integration/data-pipelines/data-pipelines#the-configyaml-file" >}}).
27+
[`config.yaml`]({{< relref "/integrate/redis-data-integration/data-pipelines/pipeline-config" >}}).
2828
When you specify the `data_type` parameter for the job, it overrides the system-wide setting `target_data_type` defined in `config.yaml`. Here, the `string` data type also requires an `args` subsection
2929
with a `value` argument that specifies the column you want to capture from the source table.
3030

0 commit comments

Comments
 (0)