[
https://issues.apache.org/jira/browse/UNOMI-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevan Jahanshahi updated UNOMI-744:
-----------------------------------
Description:
Proposal is:
* Add new option(s) on Context endpoint to request a new *sessionID* (mean
client won't have to provide the {*}sessionID{*})
* Unomi could generate the *sessionID* using format:
** UUID-indexName, like: UUID-000001, UUID-000002
* Then Unomi would return the *sessionID* in the context response.
This would provide two major improvements:
* {*}improve performance on first visitor /context requests and response
time{*}. As we know that session doesn't exists and should be new, so we don't
have to query ES like it's done today.
* *improve session/index affinity* for nexts incoming /context requests, this
would increase session retrieval consistency in case of index rolling over
(because index name is contains in the {*}sessionID{*}).
To be consider:
* this could be a breaking changes for client side applications that are
generating the session IDs on there side ({*}We could consider adding this next
to current code to not break current API, so that existing client side app
continue to be compatible.{*})
was:
Proposal is:
* Add new option(s) on Context endpoint to request a new *sessionID* (mean
client won't have to provide the {*}sessionID{*})
* Unomi could generate the *sessionID* using format:
** UUID-indexName, like: UUID-000001, UUID-000002
* Then Unomi would return the *sessionID* in the context response.
This would provide two major improvements:
* {*}improve performance on first visitor /context requests and response
time{*}. As we know that session doesn't exists and should be new, so we don't
have to query ES like it's done today.
* *improve session/index affinity* for nexts incoming /context requests, this
would increase session retrieval consistency in case of index rolling over
(because index name is contains in the {*}sessionID{*}).
To be consider:
* this could be a breaking changes for client side applications that are
generating the session IDs on there side
> Consider session ID creation on Unomi side instead of client applications
> side.
> -------------------------------------------------------------------------------
>
> Key: UNOMI-744
> URL: https://issues.apache.org/jira/browse/UNOMI-744
> Project: Apache Unomi
> Issue Type: Improvement
> Affects Versions: unomi-2.1.0
> Reporter: Kevan Jahanshahi
> Priority: Major
>
> Proposal is:
> * Add new option(s) on Context endpoint to request a new *sessionID* (mean
> client won't have to provide the {*}sessionID{*})
> * Unomi could generate the *sessionID* using format:
> ** UUID-indexName, like: UUID-000001, UUID-000002
> * Then Unomi would return the *sessionID* in the context response.
> This would provide two major improvements:
> * {*}improve performance on first visitor /context requests and response
> time{*}. As we know that session doesn't exists and should be new, so we
> don't have to query ES like it's done today.
> * *improve session/index affinity* for nexts incoming /context requests,
> this would increase session retrieval consistency in case of index rolling
> over (because index name is contains in the {*}sessionID{*}).
> To be consider:
> * this could be a breaking changes for client side applications that are
> generating the session IDs on there side ({*}We could consider adding this
> next to current code to not break current API, so that existing client side
> app continue to be compatible.{*})
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
