[james-project] 13/13: JAMES-3052 Simplify fast view projections description by using cache term

[rc...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

rcordier pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/james-project.git

commit 0bf01afbedbddf7b1712da4963d486e513332f96
Author: Tran Tien Duc <dt...@linagora.com>
AuthorDate: Wed Feb 19 15:45:32 2020 +0700

    JAMES-3052 Simplify fast view projections description by using cache term
---
 src/site/markdown/server/manage-guice-distributed-james.md | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/src/site/markdown/server/manage-guice-distributed-james.md b/src/site/markdown/server/manage-guice-distributed-james.md
index 01ab8fe..85c9ed0 100644
--- a/src/site/markdown/server/manage-guice-distributed-james.md
+++ b/src/site/markdown/server/manage-guice-distributed-james.md
@@ -267,7 +267,7 @@ _Note_: keep in mind that reindexing can be a very long operation depending on t
 Cassandra backend uses data duplication to workaround Cassandra query limitations. 
 However, Cassandra is not doing transaction when writing in several tables, 
 this can lead to consistency issues for a given piece of data. 
-The consequence could be data that is in transient state (that should never appear outside of the system).
+The consequence could be that the data is in a transient state (that should never appear outside of the system).
 
 Because of the lack of transactions, it's hard to prevent these kind of issues. We had developed some features to 
 fix some existing cassandra inconsistency issues that had been reported to James. 
@@ -296,10 +296,8 @@ Execute the Cassandra mapping `SolveInconsistencies` task described in [webadmin
 ### Jmap message fast view projections
 
 When you read a Jmap message, some calculated properties are expected to be fast to retrieve, like `preview`, `hasAttachment`. 
-James achieves it by pre-calculating and storing them into a message projection table(`message_fast_view_projection`). 
-Consequently the following fetches are optimized by reading directly from the projection table instead of calculating it again. 
-The underlying data is immutable so there's no inconsistency risk if the projections is outdated. 
-But still you can face a performance issue, how bad it is depends on how much the projection is lagging behind.
+James achieves it by pre-calculating and storing them into a caching table (`message_fast_view_projection`). 
+Missing caches are populated on message reads and will temporary decrease the performance.
 
 #### How to detect the outdated projections
 


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org