You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "ArbaazKhan1 (via GitHub)" <gi...@apache.org> on 2026/10/02 14:05:50 UTC

[PR] Stricter configuration validation [accumulo]

ArbaazKhan1 opened a new pull request, #6577:
URL: https://github.com/apache/accumulo/pull/6577

   Closes [issue #6216 ](https://github.com/apache/accumulo/issues/6216)
   
   - Add new Property Type: `CLOSED_PREFIX` to represent non-extensible namespace prefixes
   - The existing `PropertyType.PREFIX `remains open for user-extensible properties (e.g. table.custom, table.iterator ...)
   - Reclassified `tserver`, `manager`, `gc`, `monitor`, `rpc`, `sserver`, `compactor`, `compaction-coordinator`, and `instance` to `CLOSED_PREFIX`
   - updated unit test to test for new closed prefix type
   - Updated `ConfigCheckUtil`, `AccumuloConfiguration`, `ConfigurationImpl`, `ConfigurationDocGen`, and `SystemPropUtil` to handle CLOSED_PREFIX wherever `PropertyType.PREFIX` was previously checked
   - Fix `DefaultConfiguration` static initializer to exclude `CLOSED_PREFIX` properties, which also have null default values
   - Unrecognized keys under closed prefix now log a warning instead of silently being accepted


-- 
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-unsubscribe@accumulo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] Stricter configuration validation [accumulo]

Posted by "ArbaazKhan1 (via GitHub)" <gi...@apache.org>.
ArbaazKhan1 commented on PR #6577:
URL: https://github.com/apache/accumulo/pull/6577#issuecomment-5954481842

   I know [PR #6487 ](https://github.com/apache/accumulo/pull/6487) is also working on updating Properties. It looks like the work done there v here is mostly orthogonal, but depending on which get merged in first there will likely be some merge conflict, since they both touch the same block in Property.java. Worth double-checking once #6487 settles: if it ends up marking a property "required" just because its default value is null, that would wrongly flag every prefix property as required too, since both PREFIX and CLOSED_PREFIX types always have a null default by convention.


-- 
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-unsubscribe@accumulo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org