[jira] [Assigned] (IGNITE-5662) Primary index name should contain type ID or name

2017-07-10 Thread Eduard Shangareev (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-5662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eduard Shangareev reassigned IGNITE-5662:
-

Assignee: Eduard Shangareev  (was: Alexey Goncharuk)

> Primary index name should contain type ID or name
> -
>
> Key: IGNITE-5662
> URL: https://issues.apache.org/jira/browse/IGNITE-5662
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.1
>Reporter: Alexey Goncharuk
>Assignee: Eduard Shangareev
> Fix For: 2.1
>
> Attachments: IgnitePersistentStoreQueryTest.java
>
>
> Currently, the primary index name contains neither type ID nor type name. 
> Since metadata storage allocates tree root based on the index name, two 
> different indexes will be using the same index tree.
> Attached test reproduces this issue.
> A correct fix would be to include type ID or type name (depends on the 
> current SQL internals) to the index name.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Assigned] (IGNITE-5662) Primary index name should contain type ID or name

2017-07-10 Thread Vladimir Ozerov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-5662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov reassigned IGNITE-5662:
---

Assignee: Alexey Goncharuk

> Primary index name should contain type ID or name
> -
>
> Key: IGNITE-5662
> URL: https://issues.apache.org/jira/browse/IGNITE-5662
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.1
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
> Fix For: 2.1
>
> Attachments: IgnitePersistentStoreQueryTest.java
>
>
> Currently, the primary index name contains neither type ID nor type name. 
> Since metadata storage allocates tree root based on the index name, two 
> different indexes will be using the same index tree.
> Attached test reproduces this issue.
> A correct fix would be to include type ID or type name (depends on the 
> current SQL internals) to the index name.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)