taskotron / resultsdb

#37 Add an option to return just status-code instead of the whole data to create/update API calls in ResultsDB
Closed: Fixed Opened by jskladan.

Closed: Fixed
Reopen Issue

As discussed in this ticket, we need to be able to just work with status codes, if the data is not necessary. Update the API with an option, that enables this behaviour for the request.
Once that is done, update the resultsdb directive in libtaskotron, so just the minimal amount of data is selected/transfered for (not only, but primarily) the create_result calls.

This ticket is a duplicate of https://pagure.io/taskotron/libtaskotron/issue/235

This ticket had assigned some Differential requests:
D333
D334

Actually, it's the update_job calls that are problematic. create_result is plenty fast and I'm not really worried about it.

I'm also wondering if the default should be to not return data and the flag would indicate that the extra data is desired.

ah, thanks for the clarification, /me got lost a bit probably :)

Either is good with me, to be honest. Adding an option to "not return data" seemes less consistency-breaking, but since we are probably the only-ones to actually use resultsdb, it is not really that much worrisome.

Yeah, that ticket got a bit murky with my stream-of-consciousness updates :)

I'd rather have the 'less data' option be default eventually but I'd be OK with it being an option until we get the whole slow query thing figured out as long as we make sure we're using the option in libtaskotron. Once we get the root cause of this ticket figured out, we can address API/default changes.
Metadata
None
None
None
None
Lowest
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.