skuldshao commented on code in PR #18027:
URL: https://github.com/apache/druid/pull/18027#discussion_r2136623266
##########
docs/querying/using-caching.md:
##########
@@ -83,8 +83,20 @@ As long as the service is set to populate the cache, you can
set cache options f
}
}
```
+
In this example the user has set `populateCache` to `false` to avoid filling
the result cache with results for segments that are over a year old. For more
information, see [Druid SQL client APIs](../api-reference/sql-api.md).
+You can also use the SET command to specify cache options directly within your
SQL query string. For example:
+
+```
+{
+ "query" : "SET useCache=true; SET populateCache=false; SELECT COUNT(*) FROM
data_source WHERE foo = 'bar' AND __time > TIMESTAMP '2020-01-01 00:00:00'"
+}
+```
+
+For details about SET, see [SET
statements](../querying/sql.md#set-statements).
+
+
Review Comment:
resolved in the commit below.
--
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]
