[
https://issues.apache.org/jira/browse/LENS-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939551#comment-14939551
]
Deepak Barr commented on LENS-794:
----------------------------------
Sure. Its simple thing.
HiveSessionService has an SessionExpiryRunnable thread that removes inactive
sessionHandles based on 'lens.server.session.timeout.second' property.
Say, A user has obtained open a session and he is using this session to fire
queries. If the sessionHandle is removed by SessionExpiryRunnable after some
inactivity, firing a query returns HTTP 410. Currently, that's how we figure
out if a session has expired.
If we add an API that can check whether a lens session handle is still valid,
the user can always check validity first, and then, fire a query.
> Session API to check whether a session is still valid
> -----------------------------------------------------
>
> Key: LENS-794
> URL: https://issues.apache.org/jira/browse/LENS-794
> Project: Apache Lens
> Issue Type: Wish
> Reporter: Deepak Barr
> Assignee: Deepak Barr
>
> For systematic data consumption through Lens API's, One might want to check
> whether a session is still valid. If it's valid, he can reuse the old
> session, else create a new one.
> Should we add such an API ? Thoughts ?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
