You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2017/04/17 12:30:41 UTC
[jira] [Commented] (IGNITE-4997) Make sure dynamic schema state is
re-created properly after client re-connect
[ https://issues.apache.org/jira/browse/IGNITE-4997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15971017#comment-15971017 ]
Vladimir Ozerov commented on IGNITE-4997:
-----------------------------------------
Considerations:
1) When disconnect happens, we must clear all schemas and H2 stuff;
2) When reconnect happens, we must re-create all schemas from existing cache descriptors received during discovery exchange;
3) Make sure that any concurrent events operate on current schema. Probably we will have to introduce some unique ID of "current state" to distinguish client before and after re-connect.
> Make sure dynamic schema state is re-created properly after client re-connect
> -----------------------------------------------------------------------------
>
> Key: IGNITE-4997
> URL: https://issues.apache.org/jira/browse/IGNITE-4997
> Project: Ignite
> Issue Type: Task
> Components: SQL
> Reporter: Vladimir Ozerov
> Assignee: Alexander Paschenko
> Labels: important
> Fix For: 2.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)