-
Notifications
You must be signed in to change notification settings - Fork 420
Description
Product / Area:
Redis Data Integration (RDI) jobs
Managed via Redis Insight (RDI Job Editor UI)
Affected version: RDI 1.14+ (issue started appearing after upgrading to 1.14)
Description
When creating or editing an RDI job, the top-level name field of the job definition is not preserved when reloading the job from the server.
The job runs correctly after it is first saved, but if I close the editor and then use “Load from server” (or reopen the job), the name: field is missing from the YAML. Because of this, every time I reload the job, I have to manually re-add the name field before saving again.
This behavior started to appear in Redis Data Integration v1.14 (and seems to still occur in later 1.14.x builds).
Steps to Reproduce
Open Redis Insight and go to Redis Data Integration → Jobs.
Create a new job with a YAML definition that includes a top-level name field, for example:
name: transform-birthdate
output:
- uses: redis.write
with:
connection: target
data_type: hash
key:
expression: concat(['users:',id])
language: jmespath
source:
schema: dbo
table: users
transform: - uses: add_field
with:
fields:
- expression: DATE(birtdate * 86400, 'unixepoch')
field: formatted_birthdate
language: sql
Save the job.
Close the editor.
Reopen the job by selecting Load from server (or equivalent).
Check the job YAML that is loaded.
Actual Behavior
The job YAML loads without the name: field at the top.
Example after reload:
output:
- uses: redis.write
with:
connection: target
data_type: hash
key:
expression: concat(['users:',id])
language: jmespath
source:
schema: dbo
table: users
transform: - uses: add_field
with:
fields:
- expression: DATE(birtdate * 86400, 'unixepoch')
field: formatted_birthdate
language: sql
Because name is missing, I need to manually add it again (name: transform-birthdate) each time I load the job from the server.
Expected Behavior
The name field should be persisted and reloaded along with the rest of the job definition.
After saving the job once, reloading it from the server should show the exact same YAML, including:
name: transform-birthdate
Impact
Adds manual friction every time the job is edited.
Can cause confusion if multiple jobs rely on name for identification.
Risk of misconfiguration or accidental saves without a proper job name.
Environment
Redis Data Integration (RDI): 1.14+
UI: Redis Insight (RDI Job Editor)
Job type: source → transform → output pipeline (example above)
