You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a usecase where we need to update the data for offline tables due to various reasons. If we have 1:1 mapping between segments and the source parquet file, it is very easy. We modify the parquet file with same filename, create a new segment with same segment name and pinot update the segment inplace.
This is not possible if we enable merge rollup task for the offline table. There is no mapping maintained between merged segment and the source parquet files. And as far as I know, you can only create one segment from one file. There is no way to create one segment for multiple source parquet files.
Because of this, we are now forced to
disable merge rollup tasks
merge source parquet files on our own (e.g one monthly file for the whole month)
create and push merged segment from the merged parquet file
delete all the smaller segments manually (remove all segments for the month and retain only one merged monthly segment)
I would be curious to know if there is a way to do it with merge rollup tasks.
The text was updated successfully, but these errors were encountered:
We have a usecase where we need to update the data for offline tables due to various reasons. If we have 1:1 mapping between segments and the source parquet file, it is very easy. We modify the parquet file with same filename, create a new segment with same segment name and pinot update the segment inplace.
This is not possible if we enable merge rollup task for the offline table. There is no mapping maintained between merged segment and the source parquet files. And as far as I know, you can only create one segment from one file. There is no way to create one segment for multiple source parquet files.
Because of this, we are now forced to
I would be curious to know if there is a way to do it with merge rollup tasks.
The text was updated successfully, but these errors were encountered: