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

[Ivan Nečas]

On 08/15/2012 04:38 PM, Dmitri Dolguikh wrote:
> 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.
>
> -d
>
> _______________________________________________
> katello-devel mailing list
> katello-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/katello-devel
With the amount of data stored ouside of our database, it's probably 
worth looking into another way to search/sort things. I always thought 
elasticsearch is one that could be able to do it.

-- 
Ivan