[
https://issues.apache.org/jira/browse/GEODE-6010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16679143#comment-16679143
]
ASF subversion and git services commented on GEODE-6010:
--------------------------------------------------------
Commit 1137b72e9735c0faa9e554eed1cf94835dd559d2 in geode's branch
refs/heads/feature/GEODE-6010 from [~dschneider]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=1137b72 ]
GEODE-6010: Add unit test for CreateMappingCommand
Co-authored-by: Darrel Schneider <dschnei...@pivotal.io>
Co-authored-by: Jianxia Chen <jc...@pivotal.io>
> JDBC Connector should automatically configure JDBCLoader and JDBCAsyncWriter
> ----------------------------------------------------------------------------
>
> Key: GEODE-6010
> URL: https://issues.apache.org/jira/browse/GEODE-6010
> Project: Geode
> Issue Type: Improvement
> Components: extensions
> Reporter: Jianxia Chen
> Assignee: Jianxia Chen
> Priority: Major
>
> *As a* Geode user
> *When* I create a JDBC mapping using the create jdbc-mapping command
> *Then* I should not be required to perform additional configuration to get
> the data flowing between Geode and relational database.
> Currently, the user is expected to specify a CacheLoader and an
> AsyncEventQueue, which should not be required. We should also go ahead and
> create an async event queue with default values when a jdbc-mapping is
> created. (one queue per mapping)
> ----
> *Acceptance Criteria:*
> *Given* that a *partitioned* region has previously been created
> *When* a mapping is created using {{create jdbc-mapping}} command
> *Then* {{list async-event-queues}} command shows a newly created *parallel*
> AEQ
> *And* {{describe region}} command shows our cache-loader and
> async-event-queue-id configured
> *Given* that a *replicated* region has previously been created
> *When* a mapping is created using {{create jdbc-mapping}} command
> *Then* {{list async-event-queues}} command shows a newly created *serial* AEQ
> *And* {{describe region}} command shows our cache-loader and
> async-event-queue-id configured
> If cluster configuration is not enabled, it should throw an error.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
