[
https://issues.apache.org/jira/browse/GEODE-5927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16665435#comment-16665435
]
ASF subversion and git services commented on GEODE-5927:
--------------------------------------------------------
Commit 8a8a418f1765e61d789c1b70b8f2d3cf13df5f4e in geode's branch
refs/heads/develop from [~dschneider]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=8a8a418 ]
GEODE-5927: enhance create jndi-binding to configure pool (#2711)
The create jndi-binding --datasource-config-properties will now check each
name for a "pool." prefix. If found then that property, minus the prefix,
will be added to the properties that the PooledDataSourceFactory gets to
configure the pool. The other datasource config properties are still used
to configure the database.
The help strings on create jndi-binding have been updated.
Co-authored-by: @BenjaminPerryRoss
> add a way for create jndi-binding --type=POOLED to pass vendor specific
> attributes to the pool provider
> -------------------------------------------------------------------------------------------------------
>
> Key: GEODE-5927
> URL: https://issues.apache.org/jira/browse/GEODE-5927
> Project: Geode
> Issue Type: Improvement
> Components: gfsh
> Reporter: Darrel Schneider
> Assignee: Darrel Schneider
> Priority: Major
> Labels: pull-request-available
> Time Spent: 50m
> Remaining Estimate: 0h
>
> The new create jndi-binding --type=POOLED does not provide a way to configure
> the pool.
> The pool can now be implemented by a user implemented class so we can not
> know in advance the different configuration options it may have. So we want
> to provide a way that the gfsh create jndi-binding command can pass key:value
> string pairs to the pool implementation.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
