You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@geode.apache.org by "Darrel Schneider (JIRA)" <ji...@apache.org> on 2019/03/06 20:09:00 UTC

[jira] [Created] (GEODE-6494) JdbcLoader, JdbcWriter, JdbcAsyncWriter instances should fail if added to more than one region

Darrel Schneider created GEODE-6494:
---------------------------------------

             Summary: JdbcLoader, JdbcWriter, JdbcAsyncWriter instances should fail if added to more than one region
                 Key: GEODE-6494
                 URL: https://issues.apache.org/jira/browse/GEODE-6494
             Project: Geode
          Issue Type: Bug
          Components: extensions
            Reporter: Darrel Schneider


The current implementation of JdbcLoader, JdbcWriter, JdbcAsyncWriter  uses an internal SqlHandler instance that is tied to a single region. But if you add the same JdbcLoader/Writer/AsyncWriter to multiple regions then the single SqlHandler will only know about the region the first operation (i.e. get/put/destroy) was done on.

SqlHandler read and write methods should have a check to detect if they are being used on some other region and throw a Jdbc exception saying that they can only be used on a single region.

 



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