[ 
https://issues.apache.org/jira/browse/UNOMI-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456471#comment-16456471
 ] 

Serge Huber commented on UNOMI-179:
-----------------------------------

Hello Donnie, 

Here is an example of sending a non-persistent event inside an action: 
{code:java}
Event profileUpdated = new Event("profileUpdated", null, profile, 
event.getScope(), null, profile, new Date());
profileUpdated.setPersistent(false);
eventService.send(profileUpdated);
{code}
For external events it might simply be possible to set the boolean in the event 
json (example for the /eventcollector endpoint):
{code:java}
{
  "events" : [
    { "eventType" : "myEvent", "persistent" : false }
  ]
}
{code}

> Unable to remove monthly indexed items
> --------------------------------------
>
>                 Key: UNOMI-179
>                 URL: https://issues.apache.org/jira/browse/UNOMI-179
>             Project: Apache Unomi
>          Issue Type: Wish
>    Affects Versions: 1.2.0-incubating
>            Reporter: Don Hinshaw
>            Priority: Minor
>
> When I was trying to remove an event from elastic search I noticed this error.
>  
> {{Caused by: [context-*] InvalidIndexNameException[Invalid index name 
> [context-*], must not contain the following characters [ , ", *, \, <, |, ,, 
> >, /, ?]]}}
> However when I tried to load an event, it worked.  When I took a closer look 
> I noticed that the remove methods are not using the getMonthlyIndex() method 
> and are simply returning {{indexName + "-*"}}.
> It seems like the template in elasticsearch would allow for this type of 
> query but I cannot make it work.
> This seems to be a bug in ElasticSearchPersistenceImpl and since there is 
> nowhere in the code base that deletes events or sessions, it may have gone 
> unnoticed.
> Please confirm if this is a bug, or a configuration issue with elastic search 
> on my end.  If it is a bug I would be happy to work on it.
> Thanks,
> Don
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to