[JBoss JIRA] (DROOLS-3594) FEEL: Implement the interval-based algebra functions as defined by J.F. Allen
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3594?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3594:
-----------------------------------
Sprint: 2019 Week 05-07, 2019 Week 08-10, 2019 Week 11-13, 2019 Week 14-16, 2019 Week 17-19, 2019 Week 20-22, 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31, 2019 Week 32-34 (was: 2019 Week 05-07, 2019 Week 08-10, 2019 Week 11-13, 2019 Week 14-16, 2019 Week 17-19, 2019 Week 20-22, 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31)
> FEEL: Implement the interval-based algebra functions as defined by J.F. Allen
> -----------------------------------------------------------------------------
>
> Key: DROOLS-3594
> URL: https://issues.jboss.org/browse/DROOLS-3594
> Project: Drools
> Issue Type: Enhancement
> Components: dmn engine
> Affects Versions: 7.17.0.Final
> Reporter: Edson Tirelli
> Assignee: Edson Tirelli
> Priority: Major
> Attachments: ORF2009_Temporal_Reasoning_final.pdf
>
>
> In his paper "An interval-based representation of temporal knowledge", J.F.Allen defines an algebra to resolve interval relationships.
> This algebra is implemented already in Drools core to deal with events.
> This ticket is an RFE to implement similar functions in FEEL to support such algebra in DMN.
> The list of functions is:
> * before
> * meets
> * overlaps
> * finishes
> * includes
> * starts
> * coincides
> * after
> * metBy
> * overlappedBy
> * finishedBy
> * during
> * finishes
> Details of the semantics can be found in the attached presentation, slides 24 and 25.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (DROOLS-3680) Explore HA CEP design and architecture
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3680?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3680:
-----------------------------------
Sprint: 2019 Week 08-10, 2019 Week 11-13, 2019 Week 14-16, 2019 Week 17-19, 2019 Week 20-22, 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31, 2019 Week 32-34 (was: 2019 Week 08-10, 2019 Week 11-13, 2019 Week 14-16, 2019 Week 17-19, 2019 Week 20-22, 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31)
> Explore HA CEP design and architecture
> --------------------------------------
>
> Key: DROOLS-3680
> URL: https://issues.jboss.org/browse/DROOLS-3680
> Project: Drools
> Issue Type: Task
> Reporter: Mario Fusco
> Assignee: Massimiliano Dessi
> Priority: Major
> Labels: HADrools
>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (DROOLS-4255) Add KIE server support for deploying custom Prometheus metrics
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-4255?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-4255:
-----------------------------------
Sprint: 2019 Week 26-28, 2019 Week 29-31, 2019 Week 32-34 (was: 2019 Week 26-28, 2019 Week 29-31)
> Add KIE server support for deploying custom Prometheus metrics
> --------------------------------------------------------------
>
> Key: DROOLS-4255
> URL: https://issues.jboss.org/browse/DROOLS-4255
> Project: Drools
> Issue Type: Enhancement
> Components: kie server
> Affects Versions: 7.24.0.Final
> Reporter: Vladimir Blagojevic
> Assignee: Vladimir Blagojevic
> Priority: Major
> Labels: CustomerFocus
> Fix For: 7.26.0.Final
>
>
> The first implementation of Prometheus support in Kie provided default Prometheus metrics. We should enable our users to deploy their custom Prometheus metrics in addition to default Prometheus metrics already published.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JGRP-2273) ASYM_ENCRYPT: deprecate encrypt_entire_message
by Bela Ban (Jira)
[ https://issues.jboss.org/browse/JGRP-2273?page=com.atlassian.jira.plugin.... ]
Bela Ban edited comment on JGRP-2273 at 8/5/19 5:46 AM:
--------------------------------------------------------
How about we exclude GMS headers from (de-)serialization? Closing this issue for now, feel free to re-open if you have a better solution, or this solution is too kludgy for you!
was (Author: belaban):
How about we exclude GMS headers from (de-)serialization?
> ASYM_ENCRYPT: deprecate encrypt_entire_message
> ----------------------------------------------
>
> Key: JGRP-2273
> URL: https://issues.jboss.org/browse/JGRP-2273
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Major
> Fix For: 4.1.3
>
>
> In {{ASYM_ENCRYPT}}, {{encrypt_entire_message}} encrypts not only the payload, but also metadata such as destination and sender's address, headers and flags.
> The rationale was to prevent replay attacks. However, this is not an issue, as replayed messages will simply get dropped by the retransmission layer (e.g. NAKACK2 or UNICAST3).
> If people still want this feature, they can write a protocol _above_ {{ASYM_ENCRYPT}}, which serializes the entire message into the payload of a new message, and this would be exactly the same as setting {{encrypt_entire_message}} to {{true}}.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JGRP-2273) ASYM_ENCRYPT: deprecate encrypt_entire_message
by Bela Ban (Jira)
[ https://issues.jboss.org/browse/JGRP-2273?page=com.atlassian.jira.plugin.... ]
Bela Ban resolved JGRP-2273.
----------------------------
Resolution: Done
> ASYM_ENCRYPT: deprecate encrypt_entire_message
> ----------------------------------------------
>
> Key: JGRP-2273
> URL: https://issues.jboss.org/browse/JGRP-2273
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Major
> Fix For: 4.1.3
>
>
> In {{ASYM_ENCRYPT}}, {{encrypt_entire_message}} encrypts not only the payload, but also metadata such as destination and sender's address, headers and flags.
> The rationale was to prevent replay attacks. However, this is not an issue, as replayed messages will simply get dropped by the retransmission layer (e.g. NAKACK2 or UNICAST3).
> If people still want this feature, they can write a protocol _above_ {{ASYM_ENCRYPT}}, which serializes the entire message into the payload of a new message, and this would be exactly the same as setting {{encrypt_entire_message}} to {{true}}.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months