public inbox for bunsen@sourceware.org
 help / color / mirror / Atom feed
From: "Serhei Makarov" <me@serhei.io>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Bunsen <bunsen@sourceware.org>
Subject: Re: bunsen (re)design discussion #2: Repository Layout, SQLite design idea + Django-esque API(?)
Date: Mon, 21 Mar 2022 16:23:52 -0400	[thread overview]
Message-ID: <01b56f84-b5fe-4d4b-8cca-20df69a1bb0c@www.fastmail.com> (raw)
In-Reply-To: <87r16vdr8u.fsf@redhat.com>



On Mon, Mar 21, 2022, at 3:45 PM, Frank Ch. Eigler wrote:
> (We seem to be converging on accepting any loosely structured git repo
> for storage of the raw testresult data, which should make it easy for
> varied tooling to submit data.)
Yes, I have no problem with coding support for that into the design,
accepting test logs from a Git repo with free-form format and
putting parsed testrun data elsewhere.
For my concern re: cloning (full or partial) it does not complicate things.

>> Given the toss-up and potential complementary strengths, it would be
>> best to have a way to support both formats and experiment extensively.
>
> What could make sense is to have a dual API.  A secondary storage format
> that tools can consume (not just ours), and a programmatic python API
> bound to that stuff for those types of operations that are best written
> procedurally.
> ...
> Well, I hope through discussion and experiment, we settle on one or the
> other, before exposing this decision to our users.
The current model API is not "bound to" JSON the same way an
embedded-SQL analysis script would be bound to SQL.
Thus far I have completely avoided handling JSON format
directly in the analysis, doing everything through the model classes,
which could be coded against either JSON or SQL.

      reply	other threads:[~2022-03-21 20:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-17 21:23 Serhei Makarov
2022-03-20  2:59 ` Serhei Makarov
2022-03-21 19:45   ` Frank Ch. Eigler
2022-03-21 20:23     ` Serhei Makarov [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=01b56f84-b5fe-4d4b-8cca-20df69a1bb0c@www.fastmail.com \
    --to=me@serhei.io \
    --cc=bunsen@sourceware.org \
    --cc=fche@redhat.com \
    /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).