[
https://issues.apache.org/jira/browse/IGNITE-6316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16174615#comment-16174615
]
Alexander Paschenko commented on IGNITE-6316:
---------------------------------------------
[~vozerov]
1. When configuration is read from serialized {{StoredCacheData}}, it leads to
an usual attempt to create cache. But, in this case, we already do have cache
with same name in static configuration. And because we do, current internals
logic ignores attempts to create caches with existing names. So this behavior
is consistent with current state of things. However, it's doubtful whether such
behavior is still correct since PDS has been introduced. Still, I believe it'd
be more correct to fix this behavior in scope of a different issue/release.
2. All test failures I see are from flaky tests that fail in other branches too.
3. New clear re-run of all tests is on its way.
> SQL: Add ALTER TABLE tests with persistence
> -------------------------------------------
>
> Key: IGNITE-6316
> URL: https://issues.apache.org/jira/browse/IGNITE-6316
> Project: Ignite
> Issue Type: Task
> Components: sql
> Affects Versions: 2.3
> Reporter: Vladimir Ozerov
> Assignee: Alexander Paschenko
> Fix For: 2.3
>
>
> Scenario:
> 1) Start a node with persistence and pre-configured cache and {{QueryEntity}}
> 2) Add a column through {{ALTER TABLE}}
> 3) Restart the node
> 4) Make sure that new column is still there
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
