Uploaded image for project: 'JBRULES'
  1. JBRULES
  2. JBRULES-2578

Change @expires policy to override temporal requirements and behaviours

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • 5.1.0.CR1
    • 5.0.0.FINAL, 5.0.1.FINAL, 5.1.0.M1, 5.1.0.M2
    • None

    Description

      Up until now, the @expires policy was handled by the engine as a hint on the expiration offset for events, but that was causing several mistakes and misunderstanding by users. So, change the @expires policy to override and set a definitive expiration offset for events.

      Example:

      declare StockTick
      @role( event )
      @expires( 10m )
      end

      The above will cause StockTick events to be expired after 10m in memory, even if rules use temporal operators or sliding windows that would retain the event for more time, or would not require the event to be in memory for that amount of time.

      Attachments

        Activity

          People

            etirelli@redhat.com Edson Tirelli
            etirelli@redhat.com Edson Tirelli
            Archiver:
            rhn-support-ceverson Clark Everson

            Dates

              Created:
              Updated:
              Resolved:
              Archived:

              PagerDuty