capistrant edited a comment on issue #10042: URL: https://github.com/apache/druid/issues/10042#issuecomment-675787130
thanks @AlexanderSaydakov, I was able to get that working easily. Now I'm just wondering why these base64 strings are able to be read despite the underlying query not running to completion. maybe the object is becoming corrupted within the druid broker code before it is sent off to the sketches library? ~~I've narrowed this down a bit as far as what will trip it..~~ ~~thetaSketch aggregations that are not a part of filtered aggregations seem to be working fine (the above query with filters removed works just fine). it is when I introduce the filter when the invalid seed issue comes up.~~ ~~I now realize I am only tripping it if the query turns into multiple query fragments. If I target a single data node, I do not hit this issue. But once I have a query that uses a sketch where multiple upgraded data nodes are involved, we seem to run into this. If a query hits two data nodes but one is druid 15 and the other is druid 18, the query will run.~~ I'll have to dive in further on this tomorrow, but I am finding that the failure will only seem to trip under certain conditions. --- Update.. After taking a step away for a bit I was able to come back and look at this from a broader view. I was getting too tunnel visioned in on certain things that didn't really matter. At the end fo the day, it looks like @leerho had given me what to look for all along by suggesting checking everything for empty sketches on the Druid side. I started deliberately sending queries that I knew would return empty sketches and confirmed the error would happen. Then I went back to some of my other queries that I thought wouldn't be returning empty sketches, but sure enough, they were on the instances of failure. So as of now I will be focusing in on a solve for this specific problem. ---------------------------------------------------------------- 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]
