Out of curiosity, what is the benefit of having a new repo over a release target of accumulo-visibility ?
I've used VisibilityEvaluator on non Accumulo projects, so I can see some perceived benefit, but in those projects I wanted to support a visibility expression or ColumnVisibility "as Accumulo does". Marc On Thu, Sep 7, 2023 at 8:33 AM Dave Marion <dmario...@gmail.com> wrote: > I don't think the risk of not creating a release from the new repo exists. > I believe we have to use non-snapshot dependencies when creating an > Accumulo release. Right? I have no issue with creating the repo now and no > issue with the name, since we can rename it. > > On Wed, Sep 6, 2023 at 3:18 PM Keith Turner <ktur...@apache.org> wrote: > > > I would like to create a new git repository named accumulo-access in the > > ASF and want to know if anyone has thoughts about creating this repo. > This > > new repo would be a home for the Accumulo access module being created in > > 3715[1]. > > > > Once this repository is created, then the following could happen. > > > > 1. Finish creating the stand alone library that offers Accumulo's > current > > visibility functionality. > > 2. Release the new library. > > 3. Adapt Accumulo 3.1 or later to use this new library for its > > implementation of ColumnVisibility, adding it as a new dependency to > > Accumulo. > > > > One risk with creating this repository is that a release never happens > from > > it and we are left with an unused git repo hanging around. Another risk > is > > that the name could change before release, it seems this can be handled > > with a Jira issue to INFRA to rename the git repo. Are there any other > > risks? > > > > I looked into creating a new git repo and ASF offers self service tools > > that make this easy. Renaming is not self service as far as I can tell, > but > > I did find Jira issues where other projects requested a rename w/o > problem. > > > > [1]: https://github.com/apache/accumulo/pull/3715 > > >
