You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Dmitry Karachentsev (JIRA)" <ji...@apache.org> on 2017/01/02 06:57:58 UTC
[jira] [Updated] (IGNITE-4515) Throw exception when key and value
fields mapped to the same DB columns
[ 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)