https://pinot.apache.org/ logo
j

Jai Patel

02/25/2021, 6:54 PM
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

Jackie

02/25/2021, 7:11 PM
@Yupeng Fu Do you observe similar issues for upsert table deletion?
j

Jai Patel

02/25/2021, 7:12 PM
btw… i’m using the swagger to trigger the deletes.
y

Yupeng Fu

02/25/2021, 7:13 PM
i have not
j

Jackie

02/25/2021, 7:13 PM
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

Yupeng Fu

02/25/2021, 7:13 PM
but upsert table we deleted are small, since the deletion happened in the dev phase.
j

Jai Patel

02/25/2021, 10:59 PM
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

Jackie

02/25/2021, 11:55 PM
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

Jai Patel

02/26/2021, 12:02 AM
so the time column is what’s honored in calculating whether to retain a row?
c

Chinmay Soman

02/26/2021, 5:50 AM
Yes