You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ponymail.apache.org by GitBox <gi...@apache.org> on 2021/09/24 23:40:17 UTC

[GitHub] [incubator-ponymail-foal] sebbASF opened a new issue #85: Could not find any database design documentation

sebbASF opened a new issue #85:
URL: https://github.com/apache/incubator-ponymail-foal/issues/85


   The database design is crucial to the working and understanding of the code.
   However I could not find any details of the design.
   
   Every ES index entry needs a unique id, so the choice of id for each table is crucial to ensure the id is unique and reproducible (if appropriate).
   
   Various indices relate to each other, so the links between these indexes need to be documented.
   For example attachments, mbox and source all have related entries and it must be possible to move from one to another.
   
   The indices are created from the file mappings.yaml; this could be updated to include suitable documentation


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@ponymail.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [incubator-ponymail-foal] sebbASF commented on issue #85: Could not find any database design documentation

Posted by GitBox <gi...@apache.org>.
sebbASF commented on issue #85:
URL: https://github.com/apache/incubator-ponymail-foal/issues/85#issuecomment-926972020


   As an example of the sort of issues that a lack of documentation can cause, the code currently uses several different ways of finding the source record associated with an mbox record.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@ponymail.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org