#troubleshooting
@jai.patel856: 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.
@jackie.jxt: @yupeng Do you observe similar issues for upsert table deletion?
@jai.patel856: btw… i’m using the swagger to trigger the deletes.
@yupeng: i have not
@jackie.jxt: >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.patel856
@yupeng: but upsert table we deleted are small, since the deletion happened in the dev phase.
@jai.patel856: ok. Cool
@jai.patel856: 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/
@jackie.jxt: From upsert's perspective, increasing number should work. But for general realtime table handling, time column should be unix compatible for retention management
@jackie.jxt: There is an open issue for upsert with custom column which is not supported yet:
@jai.patel856: so the time column is what’s honored in calculating whether to retain a row?
#presto-pinot-connector
@ricardobordon: @ricardobordon has joined the channel
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
