Created https://github.com/apache/accumulo-access with a subset of the
changes from 3715. For the rest of the changes in 3715 I am contemplating
creating a branch in accumulo called accumulo-access where accumulo is
modified to use a snapshot version of this library. This will allow
On Thu, Sep 7, 2023 at 8:53 AM Marc P. wrote:
> Out of curiosity, what is the benefit of having a new repo over a release
> target of accumulo-visibility ?
>
The main benefit of a new repo is that it allows it to release
independently of other parts of Accumulo with its own version number. In
I'm not 100% certain about the name, but a new repo is a really low risk
thing. I say go for it.
On Thu, Sep 7, 2023, 08:54 Marc P. wrote:
> 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
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
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
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.