samarthjain commented on code in PR #18568:
URL: https://github.com/apache/druid/pull/18568#discussion_r2392381071


##########
processing/src/main/java/org/apache/druid/query/scan/ScanQueryQueryToolChest.java:
##########
@@ -191,6 +198,80 @@ public Sequence<Object[]> resultsAsArrays(final ScanQuery 
query, final Sequence<
     );
   }
 
+  @Override
+  public CacheStrategy<ScanResultValue, ScanResultValue, ScanQuery> 
getCacheStrategy(
+      final ScanQuery query,
+      @Nullable final ObjectMapper objectMapper
+  )
+  {
+    return new CacheStrategy<>()
+    {
+      @Override
+      public boolean isCacheable(ScanQuery query, boolean willMergeRunners, 
boolean segmentLevel)
+      {
+        // Currently, there is no bijective mapping from ScanResultValue to 
Result<BySegmentResultValueClass<ScanResultValue>>.
+        // This means queries will fail if:
+        //   - A query is issued with bySegment:true
+        //   - Segment-level cache is enabled on the broker (in which case it 
sends bySegment queries to data nodes).
+        return !query.context().isBySegment() && (!segmentLevel || 
willMergeRunners);
+      }
+
+      @Override
+      public byte[] computeCacheKey(ScanQuery query)
+      {
+        CacheKeyBuilder builder = new CacheKeyBuilder(SCAN_QUERY)
+            .appendCacheable(query.getVirtualColumns())
+            .appendString(query.getResultFormat().toString())

Review Comment:
   Do you know if resultFormat is used after getting results out of the result 
set cache or before the results are written to the cache? If former, we 
probably can remove it from the cache key. 



-- 
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]

Reply via email to