FrankChen021 commented on PR #17668: URL: https://github.com/apache/druid/pull/17668#issuecomment-2673760567
From the general software design principle, it makes sense to leave a room to add trace and span logs in future. However, from reality, I would like to argue that if Druid is the right choice for span logs. For span logs, scan queries or point queries are mainly involved, and because Druid lacks rerverted index, bloom filter index, serving these needs would not be a good idea. And now, i also don't see Druid has any plan on the the index or storage layer to support these scenarios. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
