Hi team.. quick question: in a hybrid table, can w...
# general
a
Hi team.. quick question: in a hybrid table, can we upload offline segments with overlapping time ranges but with unique names? We have a use case where we will need to backfill a hybrid table but the new data is not organized in time buckets but rather as a single csv spanning a large time range across existing segments. I'm wondering if we can simply create a new segment with the backfill data with unique name and upload it to the offline table and let mergeAndRollup job handle recreating segments with the correct ranges..
s
currently, we don't have the time based backfill that would clean up the old segments. Is it an option for you to upload the data & clean up the old segments?
a
Do I need to cleanup old segments even if the data is not duplicate but segments form overlapping time ranges? For example, I have two existing offline segments between with time ranges 2022-10-10_2022-10-15 and 2022-10-15_2022-10-20... If I upload a new segment with data between 2022-10-13_2022-10-17, do I need to do any cleanup? Or can I operate with these three segments and queries will work without any issues?
s
So, currently, Pinot’s data upload is based on
segment name
. If you upload segment with the same segment name, it will overwrite the data with the new one. If you upload segment with different name, it will be appended to the existing table.
that being said, if you want to push
2022-10-13_2022-10-17
, that means that you want to clean up all existing segments between
2022-10-13 -> 2022-10-17
because having those segments will incur double counting
a
Thanks for the explanation.. will double counting be a problem even if the data is different in the new segment and not repetitive?
s
then it should be fine
so no overlapping data should exist for all segments
a
Great.. that should work for our use-case then.. thanks a lot @Seunghyun
s
👍
by the way, another caveat is that the merge/rollup job currently doesn’t support backfill yet
this means that your new data
10-13-10-17
won’t be re-processed to be splitted
a
Ahh okay.. so it will stay independent and not get merged by the job.. but all the new data the gets ingested will continue to get merged and rolled up?
s
yes
so merge and rollup keeps the progress metric and it will only move forward (not looking at the back)
a
Cool.. that should be fine for us given we expect these new segments to be limited
s
👍
a
Is there a plan to support backfill with merge and rollup in future?
s
yes but it will take some time. we are still in the design phase.
a
Okay.. I will keep an eye out for this feature.. thanks again!