You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@unomi.apache.org by "Chandrashekar (Jira)" <ji...@apache.org> on 2021/10/26 12:12:00 UTC
[jira] [Updated] (UNOMI-519) KafkaInjector does not persists the
event and doesnt trigger profile creation
[ https://issues.apache.org/jira/browse/UNOMI-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chandrashekar updated UNOMI-519:
--------------------------------
Description:
While testing kafka integration with unomi using KafkaInjector plugin, we found that the event that is read from kafka, is processed differently compared to normal workflow. In normal workflow (using cxs/eventcollector) a temporary profile is created and then if there are any rules the profiles are also merged. But in KafkaInjector plugin, the event is sent and it is not even saved, since it is missing the profile.
I just used a simple event body in kafka.
{
"eventType":"mergeProfiles",
"itemId": "email",
"scope":"new",
"properties" :
{ "firstName" : "John", "lastName" : "Smith", "email":"john.smith@acme.com" }
}
Is this a bug or am I giving the wrong input? For comparison of normal workflow, I checked the code EventsCollectorEndpoint class in org.apache.unomi.rest.endpoints package. Here doEvent method gets executed which does more than what is implemented in KafkaInjector plugin.
was:
While testing kafka integration with unomi using KafkaInjector plugin, we found that the event that is read from kafka, is processed differently compared to normal workflow. In normal workflow (using cxs/eventcollector) a temporary profile is created and then if there are any rules the profiles are also merged. But in KafkaInjector plugin, the event is sent and it is not even saved, since it is missing the profile.
I just used a simple event body in kafka.
{
"eventType":"mergeProfiles",
"itemId": "email",
"scope":"new",
"properties" : {
"firstName" : "John",
"lastName" : "Smith",
"email":"john.smith@acme.com"
}
}
Is this a bug or am I giving the wrong input? For comparison of normal workflow, I checked the code EventsCollectorEndpoint class in org.apache.unomi.rest.endpoints package. Here doEvent method gets executed which does more than what is implemented in KafkaInjector plugin.
> KafkaInjector does not persists the event and doesnt trigger profile creation
> -----------------------------------------------------------------------------
>
> Key: UNOMI-519
> URL: https://issues.apache.org/jira/browse/UNOMI-519
> Project: Apache Unomi
> Issue Type: Bug
> Components: core
> Affects Versions: 1.5.7
> Reporter: Chandrashekar
> Priority: Major
>
> While testing kafka integration with unomi using KafkaInjector plugin, we found that the event that is read from kafka, is processed differently compared to normal workflow. In normal workflow (using cxs/eventcollector) a temporary profile is created and then if there are any rules the profiles are also merged. But in KafkaInjector plugin, the event is sent and it is not even saved, since it is missing the profile.
> I just used a simple event body in kafka.
> {
> "eventType":"mergeProfiles",
> "itemId": "email",
> "scope":"new",
> "properties" :
> { "firstName" : "John", "lastName" : "Smith", "email":"john.smith@acme.com" }
> }
>
> Is this a bug or am I giving the wrong input? For comparison of normal workflow, I checked the code EventsCollectorEndpoint class in org.apache.unomi.rest.endpoints package. Here doEvent method gets executed which does more than what is implemented in KafkaInjector plugin.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)