[jira] [Assigned] (GEODE-6010) JDBC Connector should automatically configure JDBCLoader and JDBCAsyncWriter
[
https://issues.apache.org/jira/browse/GEODE-6010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darrel Schneider reassigned GEODE-6010:
---
Assignee: Darrel Schneider (was: Jianxia Chen)
> 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: Darrel Schneider
>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)
[jira] [Assigned] (GEODE-6010) JDBC Connector should automatically configure JDBCLoader and JDBCAsyncWriter
[
https://issues.apache.org/jira/browse/GEODE-6010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianxia Chen reassigned GEODE-6010:
---
Assignee: Jianxia Chen
> 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)
