search

Informatievlaanderen / VSDS-LDESServer4J

Linked Data Event Streams Server for Java
https://informatievlaanderen.github.io/VSDS-LDESServer4J
European Union Public License 1.2
9 stars 8 forks source link

Elaboration of MongoDB tables - Database structure. #1019

Closed xdxxxdx closed 4 months ago

xdxxxdx commented 8 months ago

LDES Server - Snapshot 2.4.0

image In MongoDB, 14 tables are created once launched the LDES Server. Some of them remain empty. e.g:

  1. fragmentation_allocation
  2. ldesfragment
  3. ldesmember

It might be a good idea to elaborate on the usage of each table in the doc, for the future open-source community and remove the redundant ones.

Thanks.

rorlic commented 8 months ago

Sorry, I believe it is a very bad idea to elaborate on the document collections: the last thing we want is for people to start depending on these. We need to reserve the freedom to change these as we see fit in order to improve performance or for whatever other reason.

Your concern on the empty collections is however legit: these are remains of a previous server & storage architecture and should ideally be removed.

xdxxxdx commented 8 months ago

Hello @rorlic, I agree with your idea. From my perspective, we need to have it documented somewhere before the end of project. Thanks

Yalz commented 8 months ago

@rorlic i think it's due to Mongock migrations.. Needs to be looked at.

But I follow you on documenting these tables. We keep track of our DB changes via Mongock which gives an explanation.

If we start writing static code, we are doomed to have documentation errors

Yalz commented 7 months ago

TO DO: delete redundant tables after clearing in mongock steps.

Tomvbe commented 4 months ago

The application (develop branch) currently only creates the tables that are used. I know that above was an issue in the past but I was not able to reproduce it anymore with the latest server and mongo. Whether or not we should document the usage of the other database collections can be part of https://github.com/Informatievlaanderen/VSDS-LDESServer4J/issues/346. Since we may migrate to PostgreSQL in the near future, it may be best to wait with this as well.