Is your feature request related to a problem? Please describe.
Setting table properties via the accumulo.properties file is deprecated in 2.1 and then removed in main.
While there is an API to set table properties, there is nothing to denote when a property was set, changed, or removed in ZK.
The lack of transaction details makes it difficult to manage properties for an accumulo deployment.
Describe the solution you'd like
accumulo properties that are set in ZK should also have metadata that can contains creation time and last modified time.
This would improve configuration management processes.
Describe alternatives you've considered
Having a way for users to include system or namespace specific properties via the accumulo init command
would also help for initial system creation
That would be similar to the NewTableConfiguration type that allows properties to be set on table creation.
Additional context
Other issues and PRs related to setting properties:
#5854
#5855
#5562
#3909
#5859
Is your feature request related to a problem? Please describe.
Setting table properties via the accumulo.properties file is deprecated in
2.1and then removed inmain.While there is an API to set table properties, there is nothing to denote when a property was set, changed, or removed in ZK.
The lack of transaction details makes it difficult to manage properties for an accumulo deployment.
Describe the solution you'd like
accumulo properties that are set in ZK should also have metadata that can contains creation time and last modified time.
This would improve configuration management processes.
Describe alternatives you've considered
Having a way for users to include system or namespace specific properties via the accumulo init command
would also help for initial system creation
That would be similar to the NewTableConfiguration type that allows properties to be set on table creation.
Additional context
Other issues and PRs related to setting properties:
#5854
#5855
#5562
#3909
#5859