Skip to content
This repository was archived by the owner on May 14, 2025. It is now read-only.
This repository was archived by the owner on May 14, 2025. It is now read-only.

Default version is always used to pick the table prefixes #5467

@onobc

Description

@onobc

Main case

  1. Fresh SCDF 2.11.0 install
  2. Register task2 apps
    task.timestamp=maven://io.spring:timestamp-task:2.0.2
    task.timestamp.bootVersion=2
    task.timestamp-batch=maven://io.spring:timestamp-batch-task:2.0.2
    task.timestamp-batch.bootVersion=2
    
  3. Register task3 apps
    task.timestamp=maven://io.spring:timestamp-task:3.0.0
    task.timestamp.bootVersion=3
    task.timestamp-batch=maven://io.spring:timestamp-batch-task:3.0.0
    task.timestamp-batch.bootVersion=3
    
  4. Make task3 apps the default (manage versions view)
  5. Create simple timestamp task definition timestamp w/ name "taskOne"
  6. Choose launch task
  7. In launch view, click the drop-down Application Properties -> Version and select the boot2 task version
  8. Click "Launch Task"

💣 💥 In task execution view that is shown, notice the prefixes are all still BOOT3 eventhough we picked BOOT2.

THEORY: Default version is always used to pick the table prefixes. Another data point indicating the above theory is the following:

  1. Make task2 apps the default (manage versions view)
  2. Re-launch the task (choosing boot2 task version)
  3. In task execution view that is shown, notice the prefixes are all now BOOT2 as expected.

Symptom case

Switching version in task/stream deploy view does not update the table prefix properties (I believe this case is a symptom of the above).

  1. Make task3 apps the default (manage versions view)
  2. Create simple timestamp task definition timestamp w/ name "taskTwo"
  3. Choose launch task
  4. In launch view, click the drop-down Application Properties -> Version and select the boot3 task version
  5. Click "Launch Task"
  6. In task execution view that is shown, notice the prefixes are all BOOT3 as expected.
  7. Click "Relaunch Task"
  8. In launch view, click the drop-down Application Properties -> Version and select the boot2 task version

💣 💥 Notice the prefixes are all still BOOT3 eventhough we picked BOOT2.

Workaround

Use the "manage versions" view to pick the version that will be used. Never pick the version from the launch properties.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions