Hi Sachin,
There is no suggestion that aggregate cursor is different from find cursor and former does not support DBQuery.Option.noTimeout.
Aggregate cursor is a different type of cursor compared to a query cursor from a find(). This is reflected in the list of supported operations of each cursor:
Can anyone suggest anything as how to prevent aggregate cursor from getting timed out/reset.
What is the use case for setting no timeout on a cursor? Generally, it is not recommended to set no timeout on a cursor, since if the application crashes while it is processing the cursor, the cursor (with no timeout) cannot be terminated by the server. This cursor will continue to take up resources on the server until the server is restarted.
Having said that, if you find that your application processing time frequently exceeds the cursor timeout for aggregation queries, you could either:
Best regards,
Kevin