[Backlogmanager] [FIWARE-JIRA] (HELP-14466) FIWARE.Question.Tech.Are esper time intervals supported in fiware perseo?.

[Fernando Lopez (JIRA)]

     [ https://jira.fiware.org/browse/HELP-14466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fernando Lopez updated HELP-14466:
----------------------------------
    Description: 
Created question in FIWARE Q/A platform on 30-07-2018 at 23:07
{color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/51602716/are-esper-time-intervals-supported-in-fiware-perseo


+Question:+
Are esper time intervals supported in fiware perseo?

+Description:+
I'm trying to model a rule for perseo CEP using esper time intervals (timer:interval), like the one documented on http://esper.espertech.com/release-6.1.0/esper-reference/html/event_patterns.html#pattern-atoms.

In particular this example which must be fire every 20 seconds is never executed:

{
    "name": "timer_interval_update",
    "text": "select *,\"timer_interval_update\" as ruleName from pattern [every timer:interval(20 sec)]",
    "action": {
        "type": "update",
        "parameters": {
            "id":"${id}",
            "type":"A",
            "attributes": [
                {
                    "name": "status",
                    "value": "open",
                    "type": "text"
                }

            ]
        }
    }
}



  was:

Created question in FIWARE Q/A platform on 30-07-2018 at 23:07
{color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/51602716/are-esper-time-intervals-supported-in-fiware-perseo


+Question:+
Are esper time intervals supported in fiware perseo?

+Description:+
I'm trying to model a rule for perseo CEP using esper time intervals (timer:interval), like the one documented on http://esper.espertech.com/release-6.1.0/esper-reference/html/event_patterns.html#pattern-atoms.

In particular this example which must be fire every 20 seconds is never executed:

{
    "name": "timer_interval_update",
    "text": "select *,\"timer_interval_update\" as ruleName from pattern [every timer:interval(20 sec)]",
    "action": {
        "type": "update",
        "parameters": {
            "id":"${id}",
            "type":"A",
            "attributes": [
                {
                    "name": "status",
                    "value": "open",
                    "type": "text"
                }

            ]
        }
    }
}



     HD-Enabler: Perseo

> FIWARE.Question.Tech.Are esper time intervals supported in fiware perseo?.
> --------------------------------------------------------------------------
>
>                 Key: HELP-14466
>                 URL: https://jira.fiware.org/browse/HELP-14466
>             Project: Help-Desk
>          Issue Type: Monitor
>          Components: FIWARE-TECH-HELP
>            Reporter: Backlog Manager
>            Assignee: Rafael Fernández
>              Labels: cep, esper, fiware
>
> Created question in FIWARE Q/A platform on 30-07-2018 at 23:07
> {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/51602716/are-esper-time-intervals-supported-in-fiware-perseo
> +Question:+
> Are esper time intervals supported in fiware perseo?
> +Description:+
> I'm trying to model a rule for perseo CEP using esper time intervals (timer:interval), like the one documented on http://esper.espertech.com/release-6.1.0/esper-reference/html/event_patterns.html#pattern-atoms.
> In particular this example which must be fire every 20 seconds is never executed:
> {
>     "name": "timer_interval_update",
>     "text": "select *,\"timer_interval_update\" as ruleName from pattern [every timer:interval(20 sec)]",
>     "action": {
>         "type": "update",
>         "parameters": {
>             "id":"${id}",
>             "type":"A",
>             "attributes": [
>                 {
>                     "name": "status",
>                     "value": "open",
>                     "type": "text"
>                 }
>             ]
>         }
>     }
> }



--
This message was sent by Atlassian JIRA
(v6.4.1#64016)