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

Benoit Tellier commented on JAMES-3561:
---------------------------------------

>  when I then query my inbox the email isn’t listed in the query. (only a few 
> seconds later after a manual - not event triggered - refresh, the email 
> appears)

That is the real problem here: how do we ensure the push notification is sent 
when the underlying data is "viewable"?

ElasticSearch being a third party system we have no decent way to know when the 
data is ready for search. The best we can do is delay push notification and 
correlate the delay with the ElasticSearch flush interval. An imperfect 
solution that we could link to the JAMES-3559 proposal.

Cc [~rouazana]

> Email/query immediately after Email/set (mailbox move) does not reflect change
> ------------------------------------------------------------------------------
>
>                 Key: JAMES-3561
>                 URL: https://issues.apache.org/jira/browse/JAMES-3561
>             Project: James Server
>          Issue Type: Bug
>          Components: JMAP
>    Affects Versions: master
>            Reporter: Daniel Gultsch
>            Assignee: Antoine Duprat
>            Priority: Major
>
> Steps to reproduce:
> 1) Query emails in Inbox
> 2) Move one of the emails Trash. Await result of that operation
> 3) Query emails in Inbox again
>  
> Expected result:
> The second query should not contain the email we just moved to Trash.
>  
> Actual result:
>  
> It does. Only another query a few seconds later does not contain the email in 
> question.
>  
> I’m currently using ElasticSearch but enabling view.email.query.enabled did 
> not improve the situation. (I had the assumption that ElasticSearch index 
> updates are not synchronous.)
>  
> Full requests/responses are here: 
> https://gist.github.com/iNPUTmice/84e5ca91d994f73871ee67eaa2c58587



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to