ddanielr opened a new issue, #4528: URL: https://github.com/apache/accumulo/issues/4528
**Is your feature request related to a problem? Please describe.** Scans using an `eventual` consistency level should never be allowed to run against the accumulo namespace. This is to ensure that data results loaded from the metadata table and root tables are always accurate and not out of date. Inaccurate results being returned could lead to system failure if used for administration actions. **Describe the solution you'd like** Scanners using a consistency level of `eventual` should fail immediately when attempting to scan the `accumulo.` namespace. Likewise the scan servers should also fail client scans to the `accumulo.` namespace. **Describe alternatives you've considered** Handling the scan failure in the client is faster, but if a malicious client modifies the client jar, then the scan server still needs to handle additional failures. **Additional context** Because this is at a namespace level, it should be easier to have a simple deny rule then needing to keep track of any additional `accumulo.`tables that are added in future versions. -- 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: notifications-unsubscr...@accumulo.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
