Hi developers,

I have a dimension table that is generated by a spark job and written to
kudu. I would like to remove the rows in the table that were not found by
the spark job.

To do this, I was thinking the f renaming the existing table so it keeps
the UUID for existing queries create the table again and load the rows into
it. An hour later come back through and delete the old table.

If I were to do that what would your three highest concerns be? How would
this affect kudu master process?

Reply via email to