bildwelt
E2E FORUM
E2E Bridge E2E Commerce

Externalise big payload from persistent state db – removal upon delete

E2E Forum Modeling & Development Externalise big payload from persistent state db – removal upon delete

This topic contains 2 replies, has 2 voices, and was last updated by  Christof 4 years, 7 months ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #447

    Christof
    Blocked

    At one of our clients, the persistent state object payload is quite big, that’s why we only save lookup keys in the ps object, and the payload is persisted and retrieved explicitly when needed by sql adapter calls in another dedicated db table.

    Upon process completion, the payload is removed again from this dedicated db table (clean-up).

    However, when objects are deleted using the delete button in E2E console, the clean-up routine does not take place, and thus the payload oracle table contains orphans.

    Any idea how to improve this?
    Only thing I could think of is a scheduler that checks for orphans regularly…

    #449

    Marcel R.
    Blocked

    A scheduler working as garbage collector might make sense.

    However, deleting objects in the Console should only be done as last resort because this is not part of the normal life-cycle of Persistent State objects. Why is this necessary at all?

    #490

    Christof
    Blocked

    It’s currently necessary, because there is no other convenient way to manually interact with the process. I wanted to avoid building a individual UI, but instead use the process dashboard.

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.