317brian commented on code in PR #16368:
URL: https://github.com/apache/druid/pull/16368#discussion_r1588102170


##########
docs/configuration/index.md:
##########
@@ -899,6 +915,9 @@ These Coordinator static configurations can be defined in 
the `coordinator/runti
 |`druid.coordinator.kill.datasource.on`| Boolean value for whether to enable 
automatic deletion of datasource metadata (Note: datasource metadata only 
exists for datasource created from supervisor). If set to true, Coordinator 
will periodically remove datasource metadata of terminated supervisor from the 
datasource table in metadata storage.  | No | True|
 |`druid.coordinator.kill.datasource.period`| How often to do automatic 
deletion of datasource metadata in [ISO 
8601](https://en.wikipedia.org/wiki/ISO_8601) duration format. Value must be 
equal to or greater than  
`druid.coordinator.period.metadataStoreManagementPeriod`. Only applies if 
`druid.coordinator.kill.datasource.on` is set to true.| No| `P1D`|
 |`druid.coordinator.kill.datasource.durationToRetain`| Duration of datasource 
metadata to be retained from created time in [ISO 
8601](https://en.wikipedia.org/wiki/ISO_8601) duration format. Only applies if 
`druid.coordinator.kill.datasource.on` is set to true.| Yes if 
`druid.coordinator.kill.datasource.on` is set to true.| `P90D`|
+|`druid.coordinator.kill.segmentSchema.on`| Boolean value for whether to 
enable automatic deletion of unused segment schemas. If set to true, 
Coordinator will periodically identify segment schemas which are not referenced 
by any used segment and mark them as unused. At a later point, these unused 
schemas are deleted. Only applies if [Centralized Datasource 
schema](#centralized-datasource-schema) feature is enabled. | No | True|
+|`druid.coordinator.kill.segmentSchema.period`| How often to do automatic 
deletion of segment schemas in [ISO 
8601](https://en.wikipedia.org/wiki/ISO_8601) duration format. Value must be 
equal to or greater than 
`druid.coordinator.period.metadataStoreManagementPeriod`. Only applies if 
`druid.coordinator.kill.segmentSchema.on` is set to true.| No| `P1D`|
+|`druid.coordinator.kill.segmentSchema.durationToRetain`| Duration of segment 
schemas to be retained from the time it was marked as unused in [ISO 
8601](https://en.wikipedia.org/wiki/ISO_8601) duration format. Only applies if 
`druid.coordinator.kill.segmentSchema.on` is set to true.| Yes, if 
`druid.coordinator.kill.segmentSchema.on` is set to true.| `P90D`|

Review Comment:
   ```suggestion
   |`druid.coordinator.kill.segmentSchema.on`| Boolean value for enabling 
automatic deletion of unused segment schemas. If set to true, the Coordinator 
service periodically identifies segment schemas that are not referenced by any 
used segment and marks them as unused. At a later point, these unused schemas 
are deleted. Only applies if the [Centralized Datasource 
schema](#centralized-datasource-schema) feature is enabled.| No | True|
   |`druid.coordinator.kill.segmentSchema.period`| How often to do automatic 
deletion of segment schemas in [ISO 
8601](https://en.wikipedia.org/wiki/ISO_8601) duration format. Value must be 
equal to or greater than 
`druid.coordinator.period.metadataStoreManagementPeriod`. Only applies if 
`druid.coordinator.kill.segmentSchema.on` is set to true.| No| `P1D`|
   |`druid.coordinator.kill.segmentSchema.durationToRetain`| [ISO 
8601](https://en.wikipedia.org/wiki/ISO_8601) duration for the time a segment 
schema is retained for from when it's marked as unused. Only applies if 
`druid.coordinator.kill.segmentSchema.on` is set to true.| Yes, if 
`druid.coordinator.kill.segmentSchema.on` is set to true.| `P90D`|
   ```



-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to