[JBoss JIRA] (ISPN-8375) Allow additional HikariCP properties to be passed via PooledConnectionFactoryConfiguration
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-8375?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-8375:
----------------------------------
Fix Version/s: 9.4.2.Final
(was: 9.4.1.Final)
> Allow additional HikariCP properties to be passed via PooledConnectionFactoryConfiguration
> ------------------------------------------------------------------------------------------
>
> Key: ISPN-8375
> URL: https://issues.jboss.org/browse/ISPN-8375
> Project: Infinispan
> Issue Type: Enhancement
> Components: Loaders and Stores
> Affects Versions: 9.1.1.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 9.4.2.Final
>
>
> Currently the only way to provide additional HikariCP configuration is via a `hikari.properties` file. We should allow users to enter these properties via our xml/config builders.
> This will also benefit the new datagrid-infinispan-datasources subsystem, as it will allow users to continue to utilise many of the additional tuning options that we have inherited from the wildfly-connector subsystem.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months
[JBoss JIRA] (ISPN-8356) Embedded distribution names are confusing
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-8356?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-8356:
----------------------------------
Fix Version/s: 9.4.2.Final
(was: 9.4.1.Final)
> Embedded distribution names are confusing
> -----------------------------------------
>
> Key: ISPN-8356
> URL: https://issues.jboss.org/browse/ISPN-8356
> Project: Infinispan
> Issue Type: Enhancement
> Components: Build
> Affects Versions: 9.1.1.Final
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 9.4.2.Final
>
>
> The binary distribution names for embedded libraries are confusing:
> I propose the following names
>
> - infinispan-${version}-all.zip -> infinispan-embedded-${version}-all.zip
> - infinispan-${version}-minimal.zip -> infinispan-embedded-${version}-minimal.zip
> - infinispan-${version}-remote.zip -> infinispan-remote-${version}.zip
> The website labelling needs to be modified accordingly too
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months
[JBoss JIRA] (ISPN-8241) Refactor RocksDB clearThreshold
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-8241?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-8241:
----------------------------------
Fix Version/s: 9.4.2.Final
(was: 9.4.1.Final)
> Refactor RocksDB clearThreshold
> -------------------------------
>
> Key: ISPN-8241
> URL: https://issues.jboss.org/browse/ISPN-8241
> Project: Infinispan
> Issue Type: Sub-task
> Components: Loaders and Stores
> Affects Versions: 9.1.0.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 9.4.2.Final
>
>
> Currently the RocksDB store utilises a "clearThreshold" to try to delete entries individually before deleting and re-initiating the database. We should deprecate this threshold and always delete/reinit the database.
> Currently when deleting the database, we utilise Util.recursiveFileRemove which does not confirm that the file has actually been deleted. Instead, we should provide a nio based implementation instead, similar to the one stated [here|https://stackoverflow.com/questions/779519/delete-directories-recurs...]. This has the advantage that an IOException is thrown by java.nio.file.Files::delete
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months