Probably not telling you anything new here, but from the looks of it the
CliDriver will rerun the same command if it catches this exception from any
CommandProcessor. The Driver will throw this automatically if it is running
a task that is marked as retry-able. Also looks like it will only do that
in fat-client mode (no retries for HiveServer).
If you look at the Driver code there's some piece in there that seems to
indicate that one reason for introducing this was to try a query locally
and then retry it on the cluster if it fails. But I don't think the code to
auto-convert a full query was ever enabled.
My guess is that you would throw this in any task or command processor if
there was a reasonable chance that another run would succeed (i.e.: network
hiccup). This seems to be what FetchTask and ColumnStatsTask might be doing.
On Mon, Jul 8, 2013 at 7:36 PM, Edward Capriolo <[EMAIL PROTECTED]>wrote:
> No documentation here. Why should one throw it, and what does it mean to
> the caller?