mirror of https://github.com/apache/druid.git
9f6ce6ddc0
Description: Task action audit logging was first deprecated and disabled by default in Druid 0.13, #6368. As called out in the original discussion #5859, there are several drawbacks to persisting task action audit logs. - Only usage of the task audit logs is to serve the API `/indexer/v1/task/{taskId}/segments` which returns the list of segments created by a task. - The use case is really narrow and no prod clusters really use this information. - There can be better ways of obtaining this information, such as the metric `segment/added/bytes` which reports both the segment ID and task ID when a segment is committed by a task. We could also include committed segment IDs in task reports. - A task persisting several segments would bloat up the audit logs table putting unnecessary strain on metadata storage. Changes: - Remove `TaskAuditLogConfig` - Remove method `TaskAction.isAudited()`. No task action is audited anymore. - Remove `SegmentInsertAction` as it is not used anymore. `SegmentTransactionalInsertAction` is the new incarnation which has been in use for a while. - Deprecate `MetadataStorageActionHandler.addLog()` and `getLogs()`. These are not used anymore but need to be retained for backward compatibility of extensions. - Do not create `druid_taskLog` metadata table anymore. |
||
|---|---|---|
| .. | ||
| api-reference.md | ||
| automatic-compaction-api.md | ||
| data-management-api.md | ||
| dynamic-configuration-api.md | ||
| json-querying-api.md | ||
| legacy-metadata-api.md | ||
| lookups-api.md | ||
| retention-rules-api.md | ||
| service-status-api.md | ||
| sql-api.md | ||
| sql-ingestion-api.md | ||
| sql-jdbc.md | ||
| supervisor-api.md | ||
| tasks-api.md | ||