Is it a known behavior for table deletes of a real...
# troubleshooting
j
Is it a known behavior for table deletes of a realtime-only upsert tables being long-running in Pinot 0.6? Every realtime upsert table I’ve tried to delete takes a long time and eventually times out.
j
@Yupeng Fu Do you observe similar issues for upsert table deletion?
j
btw… i’m using the swagger to trigger the deletes.
y
i have not
j
From controller's perspective, I don't see any difference between deleting a regular realtime table vs upsert table. Are you able to delete regular realtime table? @Jai Patel
y
but upsert table we deleted are small, since the deletion happened in the dev phase.
j
ok. Cool
Also, is the time column used for anything other than the sequencing? Does it need to be a unix compatible timestamp or can it be any increasing number/
j
From upsert's perspective, increasing number should work. But for general realtime table handling, time column should be unix compatible for retention management
There is an open issue for upsert with custom column which is not supported yet: https://github.com/apache/incubator-pinot/issues/6523
j
so the time column is what’s honored in calculating whether to retain a row?
c
Yes