asterixdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Carey <>
Subject Re: Metadata Dependencies
Date Wed, 12 Oct 2016 19:38:36 GMT
I assume that by "index" you really mean "catalog" (as opposed to index 
in the physical sense)?  I.e., your two proposals are about a possible 
additional metadata dataset in support of extension dependency management?

On 10/12/16 9:47 AM, Steven Jacobs wrote:
> Hi,
> I am trying to get feedback from the group in general about how best to add
> Metadata Dependencies, particularly in the context of extensions. The
> functionality that is needed is as follows:
> *When dropping a metadata entity A (e.g. a dataverse), first check whether
> A has any metadata entities that depend on it. Then allow these entities
> two options:*
> *1) block: don't drop A while this dependent entity exists*
> *2) chain: when dropping A, drop this dependent entity as well.*
> One issue to keep in mind here is that with extensions, Asterix will not
> currently know about metadata datasets added by extensions.
> So far we have two proposals for this issue:
> A) Metadata dependency index. When you create an entity that depends on
> another, add an entry to this index. Check this index when dropping an
> entity.
> B) Metadata data set index. All Metadata datasets would be registered in
> this index, and then we can query them as needed when dropping an entity.
> In this case we would need some way to specify which fields in these
> datasets represent dependencies in order to query them properly.
> We would like any feedback on these two solutions or proposals for
> alternate solutions.
> Steven

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message