Good to know you’re adding this feature in the next versions.

About the idle session timeout parameter — in Impala 2.5, is there a chance that this parameter is basically killing queries that are running more than the session timeout?

We saw that if we configure the idle session timeout to be 300s, than a query that takes over 300s to be executed is getting an exception with the query status: “Session expired due to inactivity”.

If that’s the case in Impala 2.5 it’s kind of a bug. So my question is, are you familiar with that problem? And does it get fixed in the next versions?

Thanks!