I think it would be great to move the metastore into a separate project - It seems to me that some security related features/apis which are specific to the metastore are outside of it…so separating the metastore would definetly mean a cleanup in this area as well - which will in turn make the whole system more easily understandable.
I feel that the "storage-api” may also find a better home in the new metastore project - since it defines an api used by Orc/etc to enable the usage of different storage drivers in a somewhat similar way - (however: this might not be a good idea, in case we want to use the storage-api module as the ‘declared’ api to support further storage drivers) > On 2017Jul 1,, at 12:38 PM, Chaoyu Tang <ctang...@gmail.com> wrote: > > +1. A nice move which might help HMS to be more easily adopted by more > other components. > > On Sat, Jul 1, 2017 at 12:41 AM, Sushanth Sowmyan <khorg...@gmail.com> > wrote: > >> +1 >> >> On Jun 30, 2017 17:05, "Owen O'Malley" <owen.omal...@gmail.com> wrote: >> >>> On Fri, Jun 30, 2017 at 3:26 PM, Chao Sun <sunc...@apache.org> wrote: >>> >>>> and maybe a different project name? >>>> >>> >>> Yes, it certainly needs a new name. I'd like to suggest Riven. >>> >>> .. Owen >>> >>
