Re: KCIDB: v5.0 - backwards-incompatible changes

On 3/7/25 6:37 PM, Nikolai Kondrashov wrote:
> On 2/27/25 8:32 PM, Nikolai Kondrashov wrote:
>> Hello again, everyone (potentially) involved with sending data to KCIDB,
>>
>> We've accumulated a bunch of schema change needs, which would break backwards
>> compatibility, and so it's time for another major update: v5.0.
>>
>> First, here's the kcidb-io PR: https://github.com/kernelci/kcidb-io/pull/95
>>
>> This will be followed by a DB/ORM update, once we agree on something. I'll go
>> over each proposed change below, linking to corresponding commits in the PR so
>> far. Please review and respond if you have any objections, comments or
>> requests (here, or in the PR).
>>
>> I'll merge this next Friday, March 7, if there are no objections by that time.
> 
> Alright, this is now merged into kcidb-io.
> 
> I'm finishing up the DB support for the new schema, but now that I have to run
> migration tests, each BigQuery load job gets stuck several minutes in Google
> queues, so I might not be able to finish testing today. Hopefully they fix the
> problem and the DB support will be merged beginning next week. After the
> Dashboard folks give a go-ahead, I'll upgrade the database, and the data with
> the new schema will start getting accepted.

We have now upgraded the database to the v5.0 I/O schema, and KCIDB is now
accepting data in this format. Please go ahead and upgrade your submissions,
whoever is ready to do so.

Thank you!
Nick