jihoonson commented on issue #11179: URL: https://github.com/apache/druid/issues/11179#issuecomment-844650038
Hey @scimas, sorry for the late response. I think the current workaround is setting up a compaction service outside Druid that periodically issues the compaction job. https://github.com/apache/druid/pull/10843 will allow you to change segment granularity using auto compaction, but will be included in our next major release. > Thinking about it, instead of fitting it into one of the closest predefined granularities, the allocate API should be able to accommodate the user specified segment granularity if there are no existing segments for the current row. Not sure why the design is as such. This code was written a long time ago, and I don't know why it does this. But I agree. I don't see any reason that it behaves this way. -- 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]
