Ok, now we are on the same page.
On Wed, Sep 13, 2023 at 8:04 PM Adam Williamson <adamwill@xxxxxxxxxxxxxxxxx> wrote:
On Wed, 2023-09-13 at 16:49 +0200, Tomas Hrcka wrote:
> I thought this was exactly the JSON blob we will implement, If you look at
> the model of PDC
> https://product-definition-center.github.io/product-definition-center/_images/overview.svg
>
> Those endpoints are covered by relations Release, Compose, RPM through some
> others.
> The PDC approach is more or less a normalized RDBMS model.
> This should be replaceable by a much simpler denormalized approach and
> create one entry for each compose with all the data in one place.
That's missing the 'composes' endpoint use (#1 in my list below). Not
sure if that's your fault or mine, sorry if I left it out of a previous
list.
Does your replacement plan cover the "previous_release" use case, where
we need a list of all the composes for each release in the order they
happened?
Yes idea was to have the compose_id as a document root since it is unique for each compose.
something like this:
Fedora-Rawhide-20230913.n.0:{
compose_related_metadata:[metadata0:metadata,metadata1:metadata]
rpms:[nvr:other_rdata,nvr1:other_rdata1]
images:{Fedora-Sway-Live-x86_64-Rawhide-20230913.n.0.iso:"some metadata"}
}
If we store the data in the correct format for fedfind use case we can minimize the number of operations that are needed compared to REST API.
I will start working on this on the 15th. My idea is to start with the data format, Once that is sorted out.
Just a friendly reminder we will not drop PDC suddenly. The plan is to implement the new solution and have it running in parallel with PDC for a while,
Once we are sure everything is working we will start to sunset PDC.
Thanks!
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@xxxxxxxxxxxxx
https://www.happyassassin.net
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
--
Tomas Hrcka
fas: humaton
libera.CHAT: jednorozec
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
