Rahul Sharma
10/22/2025, 7:56 PMupsertCompactionTask is visible, but its task configuration is empty. As a result, compaction is not working, and the number of records in my table remains the same.
Can anyone please help?
Conf:
"task": {
"taskTypeConfigsMap": {
"UpsertCompactionTask": {
"schedule": "0 */5 * ? * *",
"bufferTimePeriod": "0d",
"invalidRecordsThresholdPercent": "10",
"invalidRecordsThresholdCount": "1000"
}
}
},Rahul Sharma
10/22/2025, 7:59 PMXiang Fu
Rahul Sharma
10/23/2025, 3:22 AM[DefaultQuartzScheduler_Worker-3] Finished generating 0 tasks configs for table: customer_requests_REALTIMEXiang Fu
Rahul Sharma
10/23/2025, 8:52 AMRahul Sharma
10/23/2025, 3:46 PMvalidDocIdsType was set to SNAPSHOT and i enabled snapshot today so no old segment would have snapshot. I changed it to IN_MEMORY and it worked. Now have again changed to SNAPSHOT as it should work for new segments now.Xiang Fu
enableSnapshot in the table upsert config?Xiang Fu
validDocIdsType (Optional) Specifies the source of validDocIds to fetch when running the data compaction. The valid types are SNAPSHOT, IN_MEMORY, IN_MEMORY_WITH_DELETE
SNAPSHOT: Default validDocIds type. This indicates that the validDocIds bitmap is loaded from the snapshot from the Pinot segment. UpsertConfig's enableSnapshot must be enabled for this type.
IN_MEMORY: This indicates that the validDocIds bitmap is loaded from the real-time server's in-memory.
IN_MEMORY_WITH_DELETE: This indicates that the validDocIds bitmap is read from the real-time server's in-memory. The valid document ids here does take account into the deleted records. UpsertConfig's deleteRecordColumn must be provided for this type.Rahul Sharma
10/23/2025, 6:33 PM