Loading...

XML

Word

Printable

Type: Task
Resolution: Done
Priority: Major
Fix Version/s: 1.0.0.Final
Affects Version/s: None
Component/s: Core Engine
Labels:
- drools-core

Story Points:
5
Blocked:
False
Ready:
False
Release Note Text:
Undefined
Git Pull Request:
https://github.com/kiegroup/kogito-runtimes/pull/839
[QE] How to address?:
---
[QE] Why QE missed?:
---
Market:

Sprint:
2020 Week 43-45 (from Okt 19)

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

The Publisher and the CloudEventEmitter should be similar to those in the PoC https://github.com/evacchi/reactive-messaging-poc

Consumer: leverage the Reactor Kafka implementation – use the PoC and get config from properties. e.g. see SpringBootDecisionTracingConfiguration for an example
Producer: follow the PoC (which uses a plain KafkaProducer) or use a KafkaTemplate (e.g. see how it is done in org.kie.kogito.tracing.decision.SpringBootModelEventEmitter)

we may choose different Channel names (e.g. kogito-input-stream/kogito-output-stream)

blocks

KOGITO-3272 Consolidate CloudEvents usages (Part 1)

Resolved

is related to

KOGITO-3737 Uniform configuration properties for cloud events / kafka

Closed

KOGITO-3731 Use spring-boot-dependencies instead of explicit properties in bom

Open

KOGITO-3733 CloudEvent Kafka Consumers should allow to ack messages eplicitly

Open

KOGITO-3760 Use Reactive Kafka template for Spring Boot (Kafka Consumer)

Open

KOGITO-3723 Use trigger name as cloud event type in producer

Resolved

KOGITO-3753 CloudEvents: Update Documentation

Resolved

(2 is related to)

Assignee:: Edoardo Vacchi (Inactive)

Reporter:: Edoardo Vacchi (Inactive)

Tester:: Marian Macik

QA Contact:: Marian Macik

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: 2020/09/22 11:33 AM

Updated:: 2022/09/09 7:13 AM

Resolved:: 2020/10/29 9:26 AM