You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/03/12 17:38:00 UTC

[jira] [Commented] (GEODE-6461) Jdbc should throw exception if a mapped table deviates from the mapping

    [ https://issues.apache.org/jira/browse/GEODE-6461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16790796#comment-16790796 ] 

ASF subversion and git services commented on GEODE-6461:
--------------------------------------------------------

Commit 18f0f214ae8ddc9da8d43f4ae7403d563bb92523 in geode's branch refs/heads/develop from BenjaminPerryRoss
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=18f0f21 ]

GEODE-6461: Report errors when table metadata and region mapping do not match (#3256)

Co-authored-by: Ben Ross <br...@pivotal.io>
Co-authored-by: Darrel Schneider <ds...@pivotal.io>
Co-authored-by: Jianxia Chen <jc...@pivotal.io>


> Jdbc should throw exception if a mapped table deviates from the mapping
> -----------------------------------------------------------------------
>
>                 Key: GEODE-6461
>                 URL: https://issues.apache.org/jira/browse/GEODE-6461
>             Project: Geode
>          Issue Type: Improvement
>            Reporter: Benjamin P Ross
>            Assignee: Benjamin P Ross
>            Priority: Major
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> When a Jdbc Mapping is created it maps values it maps values to the table as it exists during mapping creation. If the table has columns added, removed, or modified then we can't gaurentee the mapping is still correct. Attempting to load a mapping which is out of date should throw an exception prompting the user to delete and recreate their mapping with the new table format.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)