[jira] [Commented] (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:comment-tabpanel=16688400#comment-16688400
]
ASF subversion and git services commented on GEODE-6010:
Commit 0dc46eab3a95195ea45e2215047a5a79a0bde2e8 in geode's branch
refs/heads/feature/GEODE-5787-dunit-internal from [~dschneider]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=0dc46ea ]
GEODE-6010: change create jdbc-mapping to alter region and create async-queue
(#2836)
create jdbc-mapping now also does the following:
-- alters the region to have a JdbcLoader as its cache-loader
-- if synchronous, alters the region to have a JdbcWriter as its cache-writer
-- if asynchronous, creates an async-event-queue and alters regions to have it
The async-event-queue is created parallel for partitioned regions, and serial
for all other regions.
create jdbc-mapping now requires cluster configuration and uses it to check
all required preconditions before the command starts changing things.
Co-authored-by: Darrel Schneider
Co-authored-by: Jianxia Chen
Co-authored-by: Scott Jewell
> 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
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> *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] [Commented] (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:comment-tabpanel=16686982#comment-16686982
]
ASF subversion and git services commented on GEODE-6010:
Commit 0dc46eab3a95195ea45e2215047a5a79a0bde2e8 in geode's branch
refs/heads/develop from [~dschneider]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=0dc46ea ]
GEODE-6010: change create jdbc-mapping to alter region and create async-queue
(#2836)
create jdbc-mapping now also does the following:
-- alters the region to have a JdbcLoader as its cache-loader
-- if synchronous, alters the region to have a JdbcWriter as its cache-writer
-- if asynchronous, creates an async-event-queue and alters regions to have it
The async-event-queue is created parallel for partitioned regions, and serial
for all other regions.
create jdbc-mapping now requires cluster configuration and uses it to check
all required preconditions before the command starts changing things.
Co-authored-by: Darrel Schneider
Co-authored-by: Jianxia Chen
Co-authored-by: Scott Jewell
> 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
> Labels: pull-request-available
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> *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] [Commented] (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:comment-tabpanel=16680213#comment-16680213
]
ASF subversion and git services commented on GEODE-6010:
Commit 9b244d222c5141dbdfadf14ca936def33ca20aeb in geode's branch
refs/heads/feature/GEODE-6010 from [~dschneider]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=9b244d2 ]
Merge branch 'develop' into feature/GEODE-6010
> 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)
[jira] [Commented] (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:comment-tabpanel=16679177#comment-16679177
]
ASF subversion and git services commented on GEODE-6010:
Commit 1ca8e5cb6df80d304a24e12fdcec63e3f15219d2 in geode's branch
refs/heads/feature/GEODE-6010 from [~dschneider]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=1ca8e5c ]
GEODE-6010: Add unit test for CreateMappingCommand
Co-authored-by: Darrel Schneider
Co-authored-by: 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)
[jira] [Commented] (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:comment-tabpanel=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
Co-authored-by: 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)
