[katello-devel] key-value pairs for objects in katello db

[Adam Price]

----- Original Message -----
> From: "Dmitri Dolguikh" <dmitri at redhat.com>
> To: katello-devel at redhat.com
> Sent: Wednesday, August 15, 2012 10:38:04 AM
> Subject: Re: [katello-devel] key-value pairs for objects in katello db
> 
> On 15/08/12 02:26 PM, Tom McKay wrote:
> > One of the design tasks for this sprint is to come up with a way to
> > associate key-value pairs to systems and subscriptions. This would
> > be similar to the system facts that exist. It would be nice to
> > allow these pairs to exist on other objects now or in the future
> > as well (eg. activation keys).
> >
> > Question: What is the best way to model this in the katello db?
> > Joins or something?
> >
> > _______________________________________________
> > katello-devel mailing list
> > katello-devel at redhat.com
> > https://www.redhat.com/mailman/listinfo/katello-devel
> How many key-value pairs are we looking at: per system/per
> subscription/total per katello installation? Should they be mutable?
> The
> question was raised about searching - do we need to support it?
> 
> If the total number of key-value pairs is low (doesn't cross a
> million
> rows threshold) it should work ok, although searches will start to
> slow
> down when approaching the threshold above.
> 
> If the total number of pairs is large, might be better to store the
> whole set as a text blob, and rely on elastic search for lookups.

the number of pairs per system will be fairly small. it will be custom data that they can attach to a particular system (i.e. asset tag), so hopefully it won't be nearing 1M rows total.

> 
> -d
> 
> _______________________________________________
> katello-devel mailing list
> katello-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/katello-devel
> 

-- 
Adam Price
adprice at redhat dot com