[
https://issues.apache.org/jira/browse/IGNITE-20295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich updated IGNITE-20295:
---------------------------------------
Description:
At the begining of Ignite 3 was plans to have server side sessions and
partially it was implemented, but now it's not actual and we could remove all
obsolete code related to the part.
At least required to remove package
org.apache.ignite.internal.sql.engine.session with all classes
Also need to remove org.apache.ignite.sql.Session#idleTimeout
All stuff requires for keep 'session' information could be moved to client
handlers, like a ClientResource class.
was:
At the begining of Ignite 3 was plans to have server side sessions and
partially it was implemented, but now it's not actual and we could remove all
obsolete code related to the part.
At least required to remove package
org.apache.ignite.internal.sql.engine.session with all classes
All stuff requires for keep 'session' information could be moved to client
handlers, like a ClientResource class.
> Get rid of server-side session management
> -----------------------------------------
>
> Key: IGNITE-20295
> URL: https://issues.apache.org/jira/browse/IGNITE-20295
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Yury Gerzhedovich
> Priority: Major
> Labels: ignite-3
>
> At the begining of Ignite 3 was plans to have server side sessions and
> partially it was implemented, but now it's not actual and we could remove all
> obsolete code related to the part.
> At least required to remove package
> org.apache.ignite.internal.sql.engine.session with all classes
> Also need to remove org.apache.ignite.sql.Session#idleTimeout
> All stuff requires for keep 'session' information could be moved to client
> handlers, like a ClientResource class.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
