dlmarion commented on issue #88:
URL: https://github.com/apache/accumulo-access/issues/88#issuecomment-3639434273
@willmurnane - I understand where you are coming from and I mostly agree.
I'm looking at this from the following viewpoint:
1. I think we can all agree that access expressions and authorizations
should be human-readable.
2. They likely are human-readable in most, if not all, cases. The tokens
used in these things are domain specific and a human in most cases has to
manage them at some level.
3. The current 2.x implementation allowed non-UTF-8 characters. I'm not
sure how we would write an iterator that fixed a users domain specific tokens.
I think the user would need to write it. Additionally, this only fixes half of
the problem, if we fixed the access expressions, then we would need to fix the
authorizations too.
I'm thinking that we can make the specification and implementation backwards
compatible, but highly highly recommend to the users that they stick with a
strict UTF-8 policy. I think @keith-turner mentioned this above in some regard.
We could have two specifications, one strict and one relaxed. I don't see any
harm if other implementations only want to implement the strict specification.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
