September 2018 - infinispan-issues

[JBoss JIRA] (ISPN-8848) Revert ISPN-8843 when there's a fix in IntelliJ

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8848?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8848: ---------------------------------- Fix Version/s: (was: 9.4.0.Final) > Revert ISPN-8843 when there's a fix in IntelliJ > ----------------------------------------------- > > Key: ISPN-8848 > URL: https://issues.jboss.org/browse/ISPN-8848 > Project: Infinispan > Issue Type: Bug > Components: Build > Reporter: Galder Zamarreño > Assignee: Gustavo Fernandes > Priority: Minor > > Revert ISPN-8843 when the [IntelliJ bug|https://youtrack.jetbrains.com/issue/IDEA-186904] is fixed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7916) Display available JDBC datasources as a dropdown menu

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7916?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7916: ---------------------------------- Fix Version/s: (was: 9.4.0.Final) > Display available JDBC datasources as a dropdown menu > ----------------------------------------------------- > > Key: ISPN-7916 > URL: https://issues.jboss.org/browse/ISPN-7916 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Affects Versions: 9.0.0.Alpha3 > Reporter: Pedro Zapata > Assignee: Vladimir Blagojevic > Priority: Minor > > Currently the name of JDBC datasources are entered manually by the user, this should be replaced with a select option that consists of the configured datasources. > “/profile=clustered/subsystem=datasources/data-source=..." -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6639) Implement multi-tenancy for Memcached

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6639?page=com.atlassian.jira.plugin.... ] Tristan Tarrant closed ISPN-6639. --------------------------------- Resolution: Won't Do > Implement multi-tenancy for Memcached > ------------------------------------- > > Key: ISPN-6639 > URL: https://issues.jboss.org/browse/ISPN-6639 > Project: Infinispan > Issue Type: Sub-task > Components: Memcached, Server > Reporter: Sebastian Łaskawiec > Priority: Optional > > Currently this implementation is out of scope. Please vote for it if you'd like it to be implemented. -- 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: (was: 9.4.0.Final) > 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 > > 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-6639) Implement multi-tenancy for Memcached

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6639?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6639: ---------------------------------- Fix Version/s: (was: 9.4.0.Final) > Implement multi-tenancy for Memcached > ------------------------------------- > > Key: ISPN-6639 > URL: https://issues.jboss.org/browse/ISPN-6639 > Project: Infinispan > Issue Type: Sub-task > Components: Memcached, Server > Reporter: Sebastian Łaskawiec > Priority: Optional > > Currently this implementation is out of scope. Please vote for it if you'd like it to be implemented. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5585) Guide to Contributing needs updates for Infinispan 8

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5585?page=com.atlassian.jira.plugin.... ] Tristan Tarrant resolved ISPN-5585. ----------------------------------- Resolution: Out of Date > Guide to Contributing needs updates for Infinispan 8 > ---------------------------------------------------- > > Key: ISPN-5585 > URL: https://issues.jboss.org/browse/ISPN-5585 > Project: Infinispan > Issue Type: Task > Components: Documentation-Core > Reporter: Sanne Grinovero > Fix For: 9.4.0.Final > > > Just passed the link to a new contributor, I think we should at least update the JDK requirement. > Worth checking the rest.. > http://infinispan.org/docs/8.0.x/contributing/contributing.html -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9518) Create a Infinispan JDBC Driver

by Ramesh Reddy (JIRA)

Ramesh Reddy created ISPN-9518: ---------------------------------- Summary: Create a Infinispan JDBC Driver Key: ISPN-9518 URL: https://issues.jboss.org/browse/ISPN-9518 Project: Infinispan Issue Type: Feature Request Components: Remote Querying Reporter: Ramesh Reddy Build JDBC driver for Infinispan Cache using Teiid technology. There is currently already an Infinispan translator available in Teiid, this implementation needs to make use of that, but deliverable should be a single JAR that can be loaded as JDBC driver in any third party client applications. My current implementation resides at https://github.com/rareddy/infinispan-jdbc -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4075) State transfer should preserve the creation timestamp of entries

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4075?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-4075: ---------------------------------- Fix Version/s: 9.4.0.Final (was: 9.4.0.CR3) > State transfer should preserve the creation timestamp of entries > ---------------------------------------------------------------- > > Key: ISPN-4075 > URL: https://issues.jboss.org/browse/ISPN-4075 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 6.0.1.Final > Reporter: Dan Berindei > Fix For: 9.4.0.Final > > > State transfer inserts values with the current time as the creation time. Since the entries store the expected lifespan and not the expected expiration time, entries on the receiving node could expire much later than intended. > The argument probably doesn't apply to the timestamp of the last usage. Since state transfer process could be interpreted as a reader, it should be fine to extend the update the time of the last usage both on the sending node and on the receiving node. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3918) Inconsistent view of the cache with putIfAbsent in a non-tx cache during state transfer

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3918?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3918: ---------------------------------- Fix Version/s: 9.4.0.Final (was: 9.4.0.CR3) > Inconsistent view of the cache with putIfAbsent in a non-tx cache during state transfer > --------------------------------------------------------------------------------------- > > Key: ISPN-3918 > URL: https://issues.jboss.org/browse/ISPN-3918 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 6.0.0.Final > Reporter: Dan Berindei > Labels: consistency > Fix For: 9.4.0.Final > > Attachments: NonTxPutIfAbsentDuringLeaveStressTest.testNodeLeavingDuringPutIfAbsent_8.log.gz, NonTxPutIfAbsentDuringRebalanceStressTest.testPutIfAbsentDuringJoin_1.log.gz, ntpiadjst.log.gz > > > In a non-tx cache, sometimes it's possible for a {{get(k)}} to return {{null}} even though a previous {{putIfAbsent(k, v)}} returned a non-null value and the only concurrent operations on the cache are concurrent putIfAbsent calls. > Say \[B, A, C] are the owners of k (C just joined) > 1. A starts a {{putIfAbsent(k, v1)}} command, sends it to B > 2. B forwards the command to A and C > 3. C writes {{k=v1}} > 4. C becomes the primary owner of k (owners are now \[C, A]) > 5. A/B see the new topology before committing and throw an outdatedTopologyException > 6. A retries the command, sends it to C > 7. C forwards the command to A, which writes {{k=v1}} > 8. C doesn't have to update the entry, returns null > If, between steps 3 and 7, another thread on A starts a {{putIfAbsent(k, v2)}} command, the command will fail and return {{v1}} (because the primary owner already has a value). However, a subsequent {{get(k)}} command will return {{null}}, because A is an owner and doesn't have the value. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3835) Index Update command is processed before the registry listener is triggered

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3835?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3835: ---------------------------------- Fix Version/s: 9.4.0.Final (was: 9.4.0.CR3) > Index Update command is processed before the registry listener is triggered > --------------------------------------------------------------------------- > > Key: ISPN-3835 > URL: https://issues.jboss.org/browse/ISPN-3835 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 6.0.0.Final > Reporter: Sanne Grinovero > Priority: Critical > Labels: 64QueryBlockers > Fix For: 9.4.0.Final > > > When using the InfinispanIndexManager backend the master node might receive an index update command about an index which it hasn't defined yet. > Index definitions are triggered by the type registry, which in turn is driven by the ClusterRegistry and an event listener on the ClusterRegistry. It looks like slaves are sending update requests before the master has processed the configuration event. > This leads to index update commands to be lost (with a stacktrace logged) -- 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