[
https://issues.apache.org/jira/browse/UNOMI-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Serge Huber resolved UNOMI-328.
-------------------------------
Resolution: Fixed
> Unomi ignores Elasticsearch exceptions when saving an event
> -----------------------------------------------------------
>
> Key: UNOMI-328
> URL: https://issues.apache.org/jira/browse/UNOMI-328
> Project: Apache Unomi
> Issue Type: Bug
> Components: core
> Affects Versions: 1.5.0
> Reporter: Noa
> Assignee: Serge Huber
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When the save of a new event in Elasticsearch fails, the event isn't added,
> but the profile and session are added. Moreover, the rules are fired as if
> the event was added successfully.
> In addition to that, the context.json API's response is 200, although the
> event wasn't added.
> Steps to reproduce:
> 1) Post the following event to the context.json API:
> {
> "sessionId": "bug",
> "events": [
> {
> "eventType":"type",
> "properties" :
> { "prop": 1 }
> }]
> }
> The API returns 200. The event is added successfully, along with a new
> profile and session.
> 2) Post the same event with 2 small differences - change sessionId and the
> "prop" property type (from int to string):
> {
> "sessionId": "bug1",
> "events": [
> {
> "eventType":"type",
> "properties" :
> { "prop": "s" }
> }]
> }
> The API returns 200, but the event is not added. A new session and a new
> profile are created.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
