Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-7946

TTL for history cleanup should support ISO-8601 format

    Details

    • Type: Feature Request
    • Status: Closed
    • Priority: L3 - Default
    • Resolution: Fixed
    • Affects Version/s: 7.7.0
    • Fix Version/s: 7.8.0, 7.8.0-alpha2
    • Component/s: engine
    • Labels:
      None

      Description

      One of the things I always liked about engine configuration is that when it comes to timers/intervals config, I did not have to think if the long value that is expected represents millis, seconds, days, ... I would just use a clear, unambiguous ISO statement.

      I am confused now that with the introduction of the TTL for history clean up you changed this and I now can only use a number of days ...

      I would love to have support for ISO statements here. As a fall back, since the release is out now, maybe the rule could be: if it is numeric, stick to days, if its a String, interpret it ...

        Activity

        Hide
        meyer Daniel Meyer added a comment -
        Show
        meyer Daniel Meyer added a comment - Svetlana Dorokhova WDYT?
        Hide
        svetlana.dorokhova Svetlana Dorokhova added a comment - - edited

        Hi Jan,
        hi Daniel,

        this makes sense, and we had such thought when designing the feature, but decided to simplify it for the 1st iteration. Now I see that we would better implement the TTL in ISO format at once, but restricted it only to days (P5D). But what is done is done.

        We can definitely take the proposed approach:

        if it is numeric, stick to days, if its a String, interpret it as ISO period format.

        Show
        svetlana.dorokhova Svetlana Dorokhova added a comment - - edited Hi Jan, hi Daniel, this makes sense, and we had such thought when designing the feature, but decided to simplify it for the 1st iteration. Now I see that we would better implement the TTL in ISO format at once, but restricted it only to days (P5D). But what is done is done. We can definitely take the proposed approach: if it is numeric, stick to days, if its a String, interpret it as ISO period format.
        Hide
        jan.galinski@holisticon.de Jan Galinski added a comment -

        Is it really important to have the ISO format limited to days? I mean, If I configure my maintenance-window from 0:00-23:59, I could also use hours ...

        Show
        jan.galinski@holisticon.de Jan Galinski added a comment - Is it really important to have the ISO format limited to days? I mean, If I configure my maintenance-window from 0:00-23:59, I could also use hours ...
        Hide
        svetlana.dorokhova Svetlana Dorokhova added a comment -

        It is for v. 7.7, as only check for days is implemented. My note was about the format. No matter that we decided to restrict it only for days in v. 7.7, we could have chosen ISO format (P5D).

        Within this issue more fine grained values must be implemented.

        Show
        svetlana.dorokhova Svetlana Dorokhova added a comment - It is for v. 7.7, as only check for days is implemented. My note was about the format. No matter that we decided to restrict it only for days in v. 7.7, we could have chosen ISO format (P5D). Within this issue more fine grained values must be implemented.
        Hide
        jan.galinski@holisticon.de Jan Galinski added a comment -

        Ah, I see.

        +1

        Show
        jan.galinski@holisticon.de Jan Galinski added a comment - Ah, I see. +1

          People

          • Assignee:
            roman.smirnov Smirnov Roman
            Reporter:
            jan.galinski@holisticon.de Jan Galinski
          • Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development