yuanlihan edited a comment on pull request #9905: URL: https://github.com/apache/druid/pull/9905#issuecomment-631867912
Hi @jihoonson, thanks for looking into this. It should be a kind of partial overlapping not one fully overlapping another one. And sorry for the misleading title. > If I'm reading this change correctly, the compaction task will read both old and new segments for those overlapping intervals. As far as I know Druid will correctly handle this in `DruidInputSource`. Or do I misunderstand something? > Can you share some more details of your use case? Why do you want to compact segments of different versions together? For example, user first creates a `DAY` granularity segment `inline_data_2020-05-18T00:00:00.000Z_2020-05-19T00:00:00.000Z_version_1`, and then need to fix invalid data of one specific hour and create this `HOUR` granularity segment `inline_data_2020-05-18T20:00:00.000Z_2020-05-18T21:00:00.000Z_version_2`. Then there is a compaction task to compact this two partial overlapping segments. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
