POC rework threading with PostgreSQL #1990
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- artifactId: apache-james-backends-postgres
- artifactId: apache-james-mailbox-postgres - Copy from mailbox/jpa -> mailbox/postgres
- artifactId: james-server-postgres-app - Copy from apps/jpa-app -> apps/postgres-app
tested manually the binding with the subscription module -> create subscription table upon James startup successfully.
…neral RLS configuration enabled
…ryptedMailboxMessage, JPAMailboxMessageWithAttachmentStorage
…Repository interface - It will more abstract for another implement (here is Postgres)
- Fix the startup docker-compose not work
In the Postgres implementation, we accept to just store the input ZonedDateTime under the UTC time zone. Therefore, we need to be more flexible comparing ZonedDateTime between different time zones. E.g.: 2014-04-02T19:01Z[UTC] isEqual 2014-04-03T02:01+07:00[Asia/Vientiane]
Wraps Reference, in-reply-to, Mime message id and subject. Utility to hash it with murmur Goals: - Reduce argument cardinality of numerous methods - Centralize parsing from headers (duplicated twice) - Centralize hashing (done for cassandra and PG backend) - Ease of passing that information downstream (future changes)
Reduce overall cardinality too.
Only on the reading thread side. This is actually saving us one denormalization.
Use the message table instead. That way we are strongly consistent.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Appart from the first commit that I think shall be cherry-picked on master
I wanted to experiment the idea to drop the thread lookup table and instead rely on a postgreSQL index in
order not to maintain a data projection.
Kepping the data model normalised minimises the amount of writes what seems important to me on a BTree non scalable system.
@quantranhong1999 especially: thoughts? Do you wonna experiment this?