November 2018 - infinispan-issues

[JBoss JIRA] (ISPN-9322) Remove all usages of @IndexedField protostream annotation

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-9322?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9322: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Remove all usages of @IndexedField protostream annotation > --------------------------------------------------------- > > Key: ISPN-9322 > URL: https://issues.jboss.org/browse/ISPN-9322 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Major > Fix For: 9.4.3.Final > > > This annotation is deprecated and should be replaced with @Field but we still have several usages in our test suite. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9319) Cache.lock(key) should throw AvailabilityException in degraded mode

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-9319?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9319: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Cache.lock(key) should throw AvailabilityException in degraded mode > ------------------------------------------------------------------- > > Key: ISPN-9319 > URL: https://issues.jboss.org/browse/ISPN-9319 > Project: Infinispan > Issue Type: Bug > Components: Core, Test Suite - Core > Affects Versions: 9.3.0.CR1 > Reporter: Dan Berindei > Priority: Major > Fix For: 9.4.3.Final > > > We need a test for {{cache.lock(key)}} when one of the owners is not an actual member of the cluster and the cache is in degraded mode. {{PartitionHandlingInterceptor}} doesn't handle {{LockControlCommand}} explicitly, so it might end up throwing {{TimeoutException}} after waiting for a new topology. We should make sure it throws an {{AvailabilityException}} instead. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9316) Rewrite Ickle parser on ANTLR 4

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-9316?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9316: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Rewrite Ickle parser on ANTLR 4 > ------------------------------- > > Key: ISPN-9316 > URL: https://issues.jboss.org/browse/ISPN-9316 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Major > Fix For: 9.4.3.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9297) Prevent cache configuration that has L1 and exception based eviction

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-9297?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9297: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Prevent cache configuration that has L1 and exception based eviction > -------------------------------------------------------------------- > > Key: ISPN-9297 > URL: https://issues.jboss.org/browse/ISPN-9297 > Project: Infinispan > Issue Type: Bug > Reporter: William Burns > Assignee: William Burns > Priority: Major > Fix For: 9.4.3.Final > > > Exception based eviction is specifically around only keeping so much data in memory. There is no reason to have something like L1 in this case as it prevents using space for actual entries. It also would be quite confusing if a get caused an exception. > We should prevent this configuration from occurring. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9388) Cannot specify IndexedQueryMode with QueryBuilder

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-9388?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9388: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Cannot specify IndexedQueryMode with QueryBuilder > ------------------------------------------------- > > Key: ISPN-9388 > URL: https://issues.jboss.org/browse/ISPN-9388 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Affects Versions: 9.2.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Major > Fix For: 9.4.3.Final > > > IndexedQueryMode was added to the API only to QueryFactory.create(String queryString, IndexedQueryMode queryMode). > But it would be very useful to be able to specify IndexedQueryMode also when creating a query using the QueryBuilder rather than supplying the query string directly. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9382) Jenkins release pipeline should handle multiple branches and reversioning

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-9382?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9382: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Jenkins release pipeline should handle multiple branches and reversioning > ------------------------------------------------------------------------- > > Key: ISPN-9382 > URL: https://issues.jboss.org/browse/ISPN-9382 > Project: Infinispan > Issue Type: Enhancement > Components: Build > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 9.4.3.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9443) Fail when single region is accessed with multiple strategies

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-9443?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9443: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Fail when single region is accessed with multiple strategies > ------------------------------------------------------------ > > Key: ISPN-9443 > URL: https://issues.jboss.org/browse/ISPN-9443 > Project: Infinispan > Issue Type: Enhancement > Components: Hibernate Cache > Affects Versions: 9.3.1.Final > Reporter: Radim Vansa > Priority: Major > Fix For: 9.4.3.Final > > > When we have two entities that share the same region but use different access strategies the Hibernate boot should fail. Right now there's an assertion in {{DomainDataRegionImpl.prepareFor*}} but this does not give much explanation and does not fail when assertions are disabled which leads to cryptic errors later on. > Example: > {code} > @Cache(usage = CacheConcurrencyStrategy.NONSTRICT_READ_WRITE, region = "item") > public static class NonStrictReadWriteVersionedCacheableItem { ... } > @Cache(usage = CacheConcurrencyStrategy.READ_WRITE, region = "item") > public static class ReadWriteVersionedCacheableItem { ... } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9582) Lifespan/MaxIdle = 0 from Hot Rod behaviour is inconsistent with embedded

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-9582?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9582: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Lifespan/MaxIdle = 0 from Hot Rod behaviour is inconsistent with embedded > ------------------------------------------------------------------------- > > Key: ISPN-9582 > URL: https://issues.jboss.org/browse/ISPN-9582 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.4.0.CR3 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 9.4.3.Final > > > In embedded mode, specifying 0 for lifespan or maxIdle results in immediate expiration. > In Hot Rod, however, 0 results in the entry using the default server-side expiration. This was done in order to not introduce a protocol change at the time. > The 2.2 protocol introduced timeunit support with special values for default and infinity. > We should therefore not override a user-specified value of 0 with "default". -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9578) Move HR wire docs to contributing guide

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-9578?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9578: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Move HR wire docs to contributing guide > --------------------------------------- > > Key: ISPN-9578 > URL: https://issues.jboss.org/browse/ISPN-9578 > Project: Infinispan > Issue Type: Task > Components: Documentation-Core > Affects Versions: 9.4.0.CR3 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 9.4.3.Final > > > The Hot Rod wire protocol has no place in the user guide. It should be moved to the contributing guide. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9564) Align pom.xml order and versions

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-9564?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9564: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Align pom.xml order and versions > -------------------------------- > > Key: ISPN-9564 > URL: https://issues.jboss.org/browse/ISPN-9564 > Project: Infinispan > Issue Type: Enhancement > Components: Build > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 9.4.3.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 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 November 2018