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

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: extensions
• Assignee: Unassigned
• Reporter: Darrel Schneider
• Created: 06/Mar/19 20:08
• Updated: 06/Mar/19 20:08

Description

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.