[jira] [Commented] (JAMES-3440) JMAP: Avoid ElasticSearch on critical reads
[ https://issues.apache.org/jira/browse/JAMES-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17235840#comment-17235840 ] Benoit Tellier commented on JAMES-3440: --- https://github.com/linagora/james-project/pull/4044 contributed tasks to intially populate the view > JMAP: Avoid ElasticSearch on critical reads > --- > > Key: JAMES-3440 > URL: https://issues.apache.org/jira/browse/JAMES-3440 > Project: James Server > Issue Type: Improvement > Components: cassandra, elasticsearch, JMAP >Reporter: Benoit Tellier >Assignee: Antoine Duprat >Priority: Major > > I wrote a little ADR: https://github.com/apache/james-project/pull/259 > I am willing to improve the resiliency of the Distributed James JMAP > deployments I have to manage. > On the James deployments I have to manage, ElasticSearch proves to be a pain > point, both in term of performance and stability. > In order to enhence the service delivered to customers, I want to offer a > good user experience given a degraded or down ElasticSearch on top of JMAP. > The way to do it will be to offer an optional Cassandra view for resolving > common Email/query requests, involved on critical read operations (filter & > comparators for sentAt). -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3440) JMAP: Avoid ElasticSearch on critical reads
[ https://issues.apache.org/jira/browse/JAMES-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17232710#comment-17232710 ] Benoit Tellier commented on JAMES-3440: --- https://github.com/linagora/james-project/pull/4041 allows to use the EmailQueryView to resolve relevant Email/query requests both on Draft and RFC-8621 > JMAP: Avoid ElasticSearch on critical reads > --- > > Key: JAMES-3440 > URL: https://issues.apache.org/jira/browse/JAMES-3440 > Project: James Server > Issue Type: Improvement > Components: cassandra, elasticsearch, JMAP >Reporter: Benoit Tellier >Assignee: Antoine Duprat >Priority: Major > > I wrote a little ADR: https://github.com/apache/james-project/pull/259 > I am willing to improve the resiliency of the Distributed James JMAP > deployments I have to manage. > On the James deployments I have to manage, ElasticSearch proves to be a pain > point, both in term of performance and stability. > In order to enhence the service delivered to customers, I want to offer a > good user experience given a degraded or down ElasticSearch on top of JMAP. > The way to do it will be to offer an optional Cassandra view for resolving > common Email/query requests, involved on critical read operations (filter & > comparators for sentAt). -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3440) JMAP: Avoid ElasticSearch on critical reads
[ https://issues.apache.org/jira/browse/JAMES-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17232459#comment-17232459 ] Benoit Tellier commented on JAMES-3440: --- https://github.com/linagora/james-project/pull/4032 provides a listener to populate this projection > JMAP: Avoid ElasticSearch on critical reads > --- > > Key: JAMES-3440 > URL: https://issues.apache.org/jira/browse/JAMES-3440 > Project: James Server > Issue Type: Improvement > Components: cassandra, elasticsearch, JMAP >Reporter: Benoit Tellier >Assignee: Antoine Duprat >Priority: Major > > I wrote a little ADR: https://github.com/apache/james-project/pull/259 > I am willing to improve the resiliency of the Distributed James JMAP > deployments I have to manage. > On the James deployments I have to manage, ElasticSearch proves to be a pain > point, both in term of performance and stability. > In order to enhence the service delivered to customers, I want to offer a > good user experience given a degraded or down ElasticSearch on top of JMAP. > The way to do it will be to offer an optional Cassandra view for resolving > common Email/query requests, involved on critical read operations (filter & > comparators for sentAt). -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3440) JMAP: Avoid ElasticSearch on critical reads
[ https://issues.apache.org/jira/browse/JAMES-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17230379#comment-17230379 ] Benoit Tellier commented on JAMES-3440: --- https://github.com/linagora/james-project/pull/4027 provides a memory & cassandra data storage for this. I added sample optimized JMAP queries in the ADR as well as explanations regarding table structure (I needed hands on to come with the right one!) > JMAP: Avoid ElasticSearch on critical reads > --- > > Key: JAMES-3440 > URL: https://issues.apache.org/jira/browse/JAMES-3440 > Project: James Server > Issue Type: Improvement > Components: cassandra, elasticsearch, JMAP >Reporter: Benoit Tellier >Assignee: Antoine Duprat >Priority: Major > > I wrote a little ADR: https://github.com/apache/james-project/pull/259 > I am willing to improve the resiliency of the Distributed James JMAP > deployments I have to manage. > On the James deployments I have to manage, ElasticSearch proves to be a pain > point, both in term of performance and stability. > In order to enhence the service delivered to customers, I want to offer a > good user experience given a degraded or down ElasticSearch on top of JMAP. > The way to do it will be to offer an optional Cassandra view for resolving > common Email/query requests, involved on critical read operations (filter & > comparators for sentAt). -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
