From: Nikolai Kondrashov <Nikolai.Kondrashov@redhat.com>
To: kernelci@lists.linux.dev, Dmitry Vyukov <dvyukov@google.com>,
Cristian Marussi <cristian.marussi@arm.com>,
Alice Ferrazzi <alicef@gentoo.org>,
Philip Li <philip.li@intel.com>,
Vishal Bhoj <vishal.bhoj@linaro.org>,
automated-testing@lists.yoctoproject.org,
Tim Bird <Tim.Bird@sony.com>, CKI <cki-project@redhat.com>,
Mark Brown <broonie@kernel.org>,
Johnson George <Johnson.George@microsoft.com>,
Sachin Sant <sachinp@linux.ibm.com>,
Aditya Nagesh <adityanagesh@microsoft.com>
Subject: Re: KCIDB: Add timestamp metadata
Date: Mon, 23 Oct 2023 15:34:30 +0300 [thread overview]
Message-ID: <d2e2dfc9-2d67-4d23-8729-28bf683e276b@redhat.com> (raw)
In-Reply-To: <df217387-5e45-4b37-957f-5474a34af1db@redhat.com>
On 10/23/23 14:14, Nikolai Kondrashov wrote:
> As we're working on transitioning away from BigQuery as our main database, and
> lowering our growing costs, we have to implement data retention policies in
> order to maintain performance of PostgreSQL as the replacement.
>
> For that purpose I'd like to introduce a concept of "metadata" to the KCIDB
> I/O schema. Specifically a timestamp field for each object. The change will
> bump the latest schema to v4.3.
>
> Please respond with your comments here, or in the corresponding PR for
> kcidb-io:
>
> https://github.com/kernelci/kcidb-io/pull/76
I will merge this next Monday, Oct 30, if there are no remaining objections by
that time.
I'm already finishing support for this on the database/API/tool side.
Nick
prev parent reply other threads:[~2023-10-23 12:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 11:14 KCIDB: Add timestamp metadata Nikolai Kondrashov
2023-10-23 12:34 ` Nikolai Kondrashov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d2e2dfc9-2d67-4d23-8729-28bf683e276b@redhat.com \
--to=nikolai.kondrashov@redhat.com \
--cc=Johnson.George@microsoft.com \
--cc=Tim.Bird@sony.com \
--cc=adityanagesh@microsoft.com \
--cc=alicef@gentoo.org \
--cc=automated-testing@lists.yoctoproject.org \
--cc=broonie@kernel.org \
--cc=cki-project@redhat.com \
--cc=cristian.marussi@arm.com \
--cc=dvyukov@google.com \
--cc=kernelci@lists.linux.dev \
--cc=philip.li@intel.com \
--cc=sachinp@linux.ibm.com \
--cc=vishal.bhoj@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).