The only use I can see for them is implementing a database table container concept similar to an RBDMS on top of Geode, but since they provide no real inherited or implied functionality (access/visibility, shared properties, security, etc.) it would seem they are of little use. Maintaining a clean core and allowing users of the project to build this type of functionality on top seems better. Bob
On 1/7/16, 10:43 AM, "John Blum" <jb...@pivotal.io> wrote: >Actually, +1000 to removing them altogether. > >On Thu, Jan 7, 2016 at 10:42 AM, John Blum <jb...@pivotal.io> wrote: > >> +1 to deprecating Subregions. >> >> On Thu, Jan 7, 2016 at 10:41 AM, Jens Deppe <jde...@pivotal.io> wrote: >> >>> In the past (GemFire days) we've had discussions about deprecating >>> subregions. I'd like to raise the topic again for consideration. >>> >>> Subregions are merely a way to provide a logical, hierarchical grouping of >>> regions and don't provide any kind of functionality or behavior which is >>> inherited or implied. >>> >>> A similar hierarchy could just as easily be created by using your own >>> naming conventions. For example, given region* 'A'* as the root, region >>> *'A_B'* would be the first 'subregion' and *'A_B_C'* could be considered a >>> 'sub-subregion'. >>> >>> Thoughts? Comments? >>> >>> --Jens >>> >> >> >> >> -- >> -John >> 503-504-8657 >> john.blum10101 (skype) >> > > > >-- >-John >503-504-8657 >john.blum10101 (skype)
