[
https://issues.apache.org/jira/browse/IGNITE-12061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16908893#comment-16908893
]
Stanilovsky Evgeny commented on IGNITE-12061:
---------------------------------------------
[~Pavlukhin] thanks a lot ! i`ll try to check all your comments soon.
As for : "Is it right that before this patch we did not clear index partition
at all on index drop? Do you know why was it so?" - i can only explain that it
take place for simplification, if u have only root page after index destroy no
need to handle IndexDestroy exceptions any more, i discuss with [~agoncharuk]
too and it looks like correct behavior to throw exception on concurrent index
drop and usage.
> Silently fail while try to recreate already existing index with differ
> inline_size.
> -----------------------------------------------------------------------------------
>
> Key: IGNITE-12061
> URL: https://issues.apache.org/jira/browse/IGNITE-12061
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Affects Versions: 2.5, 2.7, 2.7.5
> Reporter: Stanilovsky Evgeny
> Assignee: Stanilovsky Evgeny
> Priority: Major
> Fix For: 2.7.6
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> INLINE_SIZE differ from previous value is not correctly sets.
> 1. create index idx0(c1, c2)
> 2. drop idx0
> 3. create index idx0(c1, c2) inline_size 100;
> inline_size remains the same, in this case default = 10.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
