[jira] [Updated] (IGNITE-4515) Throw exception when key and value fields mapped to the same DB columns

2017-09-26 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov updated IGNITE-4515:

Fix Version/s: (was: 2.3)

> Throw exception when key and value fields mapped to the same DB columns
> ---
>
> Key: IGNITE-4515
> URL: https://issues.apache.org/jira/browse/IGNITE-4515
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 1.8
>Reporter: Dmitry Karachentsev
>Assignee: Dmitry Karachentsev
>
> In case of using JDBC store and following config (pseudocode):
> KeyClass { field1; field2; field3 }, ValClass { field1; field2; field3 }
> Fields mapped to the same DB table TABLE_NAME and columns: field1 -> col1, 
> field2 -> col2, field3 -> col3.
> On node startup throw an exception with message that restricts such case. 
> Field mappings should not intersect.



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

[jira] [Updated] (IGNITE-4515) Throw exception when key and value fields mapped to the same DB columns

2017-07-10 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov updated IGNITE-4515:

Fix Version/s: (was: 2.1)
   2.2

> Throw exception when key and value fields mapped to the same DB columns
> ---
>
> Key: IGNITE-4515
> URL: https://issues.apache.org/jira/browse/IGNITE-4515
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 1.8
>Reporter: Dmitry Karachentsev
>Assignee: Dmitry Karachentsev
> Fix For: 2.2
>
>
> In case of using JDBC store and following config (pseudocode):
> KeyClass { field1; field2; field3 }, ValClass { field1; field2; field3 }
> Fields mapped to the same DB table TABLE_NAME and columns: field1 -> col1, 
> field2 -> col2, field3 -> col3.
> On node startup throw an exception with message that restricts such case. 
> Field mappings should not intersect.



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

[jira] [Updated] (IGNITE-4515) Throw exception when key and value fields mapped to the same DB columns

2017-04-06 Thread Dmitry Karachentsev (JIRA) 

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

Dmitry Karachentsev updated IGNITE-4515:

Fix Version/s: (was: 2.0)
   2.1

> Throw exception when key and value fields mapped to the same DB columns
> ---
>
> Key: IGNITE-4515
> URL: https://issues.apache.org/jira/browse/IGNITE-4515
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 1.8
>Reporter: Dmitry Karachentsev
>Assignee: Dmitry Karachentsev
> Fix For: 2.1
>
>
> In case of using JDBC store and following config (pseudocode):
> KeyClass { field1; field2; field3 }, ValClass { field1; field2; field3 }
> Fields mapped to the same DB table TABLE_NAME and columns: field1 -> col1, 
> field2 -> col2, field3 -> col3.
> On node startup throw an exception with message that restricts such case. 
> Field mappings should not intersect.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4515) Throw exception when key and value fields mapped to the same DB columns

2017-01-01 Thread Dmitry Karachentsev (JIRA) 

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

Dmitry Karachentsev updated IGNITE-4515:

Fix Version/s: (was: 2,0)
   2.0

> Throw exception when key and value fields mapped to the same DB columns
> ---
>
> Key: IGNITE-4515
> URL: https://issues.apache.org/jira/browse/IGNITE-4515
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 1.8
>Reporter: Dmitry Karachentsev
>Assignee: Dmitry Karachentsev
> Fix For: 2.0
>
>
> In case of using JDBC store and following config (pseudocode):
> KeyClass { field1; field2; field3 }, ValClass { field1; field2; field3 }
> Fields mapped to the same DB table TABLE_NAME and columns: field1 -> col1, 
> field2 -> col2, field3 -> col3.
> On node startup throw an exception with message that restricts such case. 
> Field mappings should not intersect.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4515) Throw exception when key and value fields mapped to the same DB columns

2017-01-01 Thread Dmitry Karachentsev (JIRA) 

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

Dmitry Karachentsev updated IGNITE-4515:

Description: 
In case of using JDBC store and following config (pseudocode):
KeyClass { field1; field2; field3 }, ValClass { field1; field2; field3 }

Fields mapped to the same DB table TABLE_NAME and columns: field1 -> col1, 
field2 -> col2, field3 -> col3.

On node startup throw an exception with message that restricts such case. Field 
mappings should not intersect.

  was:
In case of (pseudocode):
KeyClass { field1; field2; field3 }, ValClass { field1; field2; field3 }

Map fields to DB table TABLE_NAME columns: field1 -> col1, field2 -> col2, 
field3 -> col3.

On node startup throw an exception with message that restricts such case. Field 
mappings should not intersect.


> Throw exception when key and value fields mapped to the same DB columns
> ---
>
> Key: IGNITE-4515
> URL: https://issues.apache.org/jira/browse/IGNITE-4515
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 1.8
>Reporter: Dmitry Karachentsev
>Assignee: Dmitry Karachentsev
> Fix For: 2.0
>
>
> In case of using JDBC store and following config (pseudocode):
> KeyClass { field1; field2; field3 }, ValClass { field1; field2; field3 }
> Fields mapped to the same DB table TABLE_NAME and columns: field1 -> col1, 
> field2 -> col2, field3 -> col3.
> On node startup throw an exception with message that restricts such case. 
> Field mappings should not intersect.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)