September 2018 - infinispan-issues

[JBoss JIRA] (ISPN-7979) Include all component licenses in distributions

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7979?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7979: ---------------------------------- Fix Version/s: 9.4.0.Final (was: 9.4.0.CR3) > Include all component licenses in distributions > ----------------------------------------------- > > Key: ISPN-7979 > URL: https://issues.jboss.org/browse/ISPN-7979 > Project: Infinispan > Issue Type: Task > Components: Build > Reporter: Tristan Tarrant > Assignee: Jakub Senko > Priority: Blocker > Fix For: 9.4.0.Final > > > The distributions should include licenses for all components -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7956) Investigate removing PartitionHandlingInterceptor

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7956?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7956: ---------------------------------- Fix Version/s: 9.4.0.Final (was: 9.4.0.CR3) > Investigate removing PartitionHandlingInterceptor > ------------------------------------------------- > > Key: ISPN-7956 > URL: https://issues.jboss.org/browse/ISPN-7956 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 9.1.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.4.0.Final > > > When all the owners of a key leave the cluster, the distribution interceptor doesn't know how to handle that key. Instead, it has to signal that to the {{PartitionHandlingInterceptor}} somehow, and PHI decides whether to return a {{null}} value or throw an {{AvailabilityException}}. > Single-key read commands and write commands are handled by throwing an {{AllOwnersLostException}} (initially an {{RpcException}}) from the distribution interceptor and catching it in {{PartitionHandlingInterceptor}}. If partitioning handling is disabled, the {{AllOwnersLostException}} is instead caught by {{StateTransferInterceptor}}, which returns the {{null}} value (for read commands) or waits for a new topology and retries (for write commands). > For multi-key read commands the distribution interceptor can't throw an exception, because that would lose the values that were retrieved successfully. For {{GetAllCommand}} we could get away with storing the values in the context, but that wouldn't work for functional commands because they transform the values on the remote node. ISPN-7884 removing the values with missing owners from the result collection, but that means values that are simply missing have to be treated differently, and {{StateTransferInterceptor}} has to iterate through the list of results again in order to remove them. > It should be simpler to move all the availability checks to the distribution interceptor, and remove the {{PartitionHandlingInterceptor}}. DI already calls some {{PartitionHandlingManager}} methods directly, in order to keep track of partially committed transactions. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7947) Remove META-INF/services resource files from server wherever possible and replace them with @MetaInfServices annotation

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7947?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7947: ---------------------------------- Fix Version/s: 9.4.0.Final (was: 9.4.0.CR3) > Remove META-INF/services resource files from server wherever possible and replace them with @MetaInfServices annotation > ----------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-7947 > URL: https://issues.jboss.org/browse/ISPN-7947 > Project: Infinispan > Issue Type: Task > Components: Server > Affects Versions: 9.1.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.4.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[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.0.Final (was: 9.4.0.CR3) > 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 > Fix For: 9.4.0.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.5.0#75005)

7 years, 6 months

1
0
0 / 0

[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.0.Final (was: 9.4.0.CR3) > 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 > Fix For: 9.4.0.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.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8320) Javadoc comments contain malformed HTML

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8320?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8320: ---------------------------------- Fix Version/s: 9.4.0.Final (was: 9.4.0.CR3) > Javadoc comments contain malformed HTML > --------------------------------------- > > Key: ISPN-8320 > URL: https://issues.jboss.org/browse/ISPN-8320 > Project: Infinispan > Issue Type: Bug > Components: Documentation-Core > Affects Versions: 9.1.0.Final > Reporter: Dan Berindei > Priority: Trivial > Fix For: 9.4.0.Final > > > In Java 8, {{javadoc}} started reporting malformed HTML tags in Javadoc comments. Our distribution build is ignoring the errors, and the normal build doesn't generate Javadoc at all. However, invoking {{mvn javadoc:javadoc}} directly fails: > {noformat} > [INFO] [ERROR] Exit code: 1 - /home/dan/Work/infinispan/target/checkout/checkstyle/src/main/java/org/infinispan/checkstyle/filters/ExcludeTestPackages.java:17: error: malformed HTML > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8303) Cassandra Cache Store: Upgrade to latest Cassandra stable release 3.0.14

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8303?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8303: ---------------------------------- Fix Version/s: 9.4.0.Final (was: 9.4.0.CR3) > Cassandra Cache Store: Upgrade to latest Cassandra stable release 3.0.14 > ------------------------------------------------------------------------ > > Key: ISPN-8303 > URL: https://issues.jboss.org/browse/ISPN-8303 > Project: Infinispan > Issue Type: Task > Components: Loaders and Stores > Reporter: Andrea Cosentino > Assignee: Andrea Cosentino > Fix For: 9.4.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8260) Add user guide section for the deployment of analyzers with Ickle

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8260?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8260: ---------------------------------- Fix Version/s: 9.4.0.Final (was: 9.4.0.CR3) > Add user guide section for the deployment of analyzers with Ickle > ----------------------------------------------------------------- > > Key: ISPN-8260 > URL: https://issues.jboss.org/browse/ISPN-8260 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Affects Versions: 9.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.4.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8242) Utilise Column Families for expiration

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8242?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8242: ---------------------------------- Fix Version/s: 9.4.0.Final (was: 9.4.0.CR3) > Utilise Column Families for expiration > -------------------------------------- > > Key: ISPN-8242 > URL: https://issues.jboss.org/browse/ISPN-8242 > Project: Infinispan > Issue Type: Sub-task > Components: Loaders and Stores > Affects Versions: 9.1.0.Final > Reporter: Ryan Emerson > Assignee: William Burns > Fix For: 9.4.0.Final > > > Currently we utilise two separate databases for the actual data being stored and an expiration queue. Instead we should utilise [Column Families|https://github.com/facebook/rocksdb/wiki/Column-Families] as these allow for atomic updates across columns. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[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.0.Final (was: 9.4.0.CR3) > 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 > Fix For: 9.4.0.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.5.0#75005)

7 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2018