August 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5601) Merge ExtendedModuleCommandFactory into ModuleCommandFactory

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-5601?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-5601: ------------------------------ Fix Version/s: 8.1.0.Final (was: 8.0.0.Final) > Merge ExtendedModuleCommandFactory into ModuleCommandFactory > ------------------------------------------------------------ > > Key: ISPN-5601 > URL: https://issues.jboss.org/browse/ISPN-5601 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.0.0.Alpha2 > Reporter: Radim Vansa > Assignee: Ryan Emerson > Fix For: 8.1.0.Final > > > These are the docs for ExtendedModuleCommandFactory: > {quote} > Temporary workaround to avoid modifying ModuleCommandFactory interface. This interface should be merged with ModuleCommandFactory in 6.0. > {quote} > Seems that was forgotten in 6.0, 8.0 can fix that. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

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

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-5585?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-5585: ------------------------------ Fix Version/s: 8.1.0.Final (was: 8.0.0.Final) > 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: 8.1.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 (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5584) Support fine-grained write skew check for FineGrainedAtomicMap entries

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-5584?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-5584: ------------------------------ Fix Version/s: 8.1.0.Final (was: 8.0.0.Final) > Support fine-grained write skew check for FineGrainedAtomicMap entries > ---------------------------------------------------------------------- > > Key: ISPN-5584 > URL: https://issues.jboss.org/browse/ISPN-5584 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 8.0.0.Alpha2, 7.2.3.Final > Reporter: Dan Berindei > Fix For: 8.1.0.Final > > > FineGrainedAtomicMap doesn't currently work with write skew check enabled. > I was able to make it work by adding a special case for DeltaAwareCacheEntry in WriteSkewHelper, however the map has a single version, so the write skew check fails if any of the sub-keys were modified in parallel. With pessimistic locking, fine-grained maps allow the user to modify different sub-keys concurrently, we should allow the same with optimistic locking. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5578) Allow default index storage location scoped by cache name

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-5578?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-5578: ------------------------------ Fix Version/s: 8.1.0.Final (was: 8.0.0.Final) > Allow default index storage location scoped by cache name > --------------------------------------------------------- > > Key: ISPN-5578 > URL: https://issues.jboss.org/browse/ISPN-5578 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 8.1.0.Final > > > Thus avoiding clashing of multiple indexed caches without necessarily needing to configure {{indexBase}} for each one -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5579) Infinispan server subsystem thread pool injection

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-5579?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-5579: ------------------------------ Fix Version/s: 8.1.0.Final (was: 8.0.0.Final) > Infinispan server subsystem thread pool injection > ------------------------------------------------- > > Key: ISPN-5579 > URL: https://issues.jboss.org/browse/ISPN-5579 > Project: Infinispan > Issue Type: Feature Request > Components: Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.1.0.Final > > > Upstream wildfly will be dropping the threads subsystem so subsystems which require thread pools should add configuration for these -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5575) Shared write-behind store can read stale entries on joiner

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-5575?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-5575: ------------------------------ Fix Version/s: 8.1.0.Final (was: 8.0.0.Final) > Shared write-behind store can read stale entries on joiner > ---------------------------------------------------------- > > Key: ISPN-5575 > URL: https://issues.jboss.org/browse/ISPN-5575 > Project: Infinispan > Issue Type: Bug > Components: Core, Loaders and Stores > Affects Versions: 8.0.0.Alpha2, 7.2.3.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.1.0.Final > > > The AsyncCacheWriter modification queue is not sent with state transfer when the store is shared. A joiner can then read from the shared store a stale version of entries that have updates in the modification queue but are no longer in memory (because they were either removed explicitly, or evicted). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5574) Define high-level cache capabilities

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-5574?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-5574: ------------------------------ Fix Version/s: 8.1.0.Final (was: 8.0.0.Final) > Define high-level cache capabilities > ------------------------------------ > > Key: ISPN-5574 > URL: https://issues.jboss.org/browse/ISPN-5574 > Project: Infinispan > Issue Type: Feature Request > Components: Configuration, Core > Affects Versions: 7.2.3.Final > Reporter: Dan Berindei > Priority: Minor > Fix For: 8.1.0.Final > > > Infinispan's configuration is very flexible, and it's sometimes hard to figure out how different settings affect things like cache consistency. > For example, the lucene-directory module uses the fairly complicated {{Configurations.noDataLossOnJoiner()}} method to validate that a cache is safe for storing lucene indexes. > Another example is users who would like to use a store for backup, but they don't want read from the store for M/R tasks or when get(k) doesn't find the key in memory. > One idea would be to define a set of "capabilities" like "state-transfer-complete" or "all-data-in-memory". The user could then add those capabilities in the cache definition, and the cache won't start if the configuration violates those capabilities. The capabilities would also be used internally, to improve the error message when a feature requires a particular combination of settings. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5642) Reduce contention in the RPC timeout handling

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-5642?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-5642: ------------------------------ Fix Version/s: 8.1.0.Final (was: 8.0.0.Final) > Reduce contention in the RPC timeout handling > --------------------------------------------- > > Key: ISPN-5642 > URL: https://issues.jboss.org/browse/ISPN-5642 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 8.0.0.Beta2 > Reporter: Dan Berindei > Priority: Minor > Labels: help_wanted > Fix For: 8.1.0.Final > > > Most of the RPC timeout tasks are cancelled way before their timeout expires. This means the scheduler spends a lot of time reordering the elements of its DelayQueue. > It should be possible to store the tasks with a long timeout (e.g. 1s) in a queue and only move them to the scheduler's priority queue when they have less than 1s to expiration (e.g. by a worker thread that runs every 0.5s) > Storing all the tasks in a single queue may be impractical because the worker thread would have more and work to do as load increases and the RPCs take longer to finish, so a [hashed timing wheel|http://www.cse.wustl.edu/~cdgill/courses/cs6874/TimingWheels.ppt] may be needed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5682) The minimum aggregation function doesn't work with Strings

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-5682?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-5682: ------------------------------ Fix Version/s: 8.1.0.Final (was: 8.0.0.Final) > The minimum aggregation function doesn't work with Strings > ---------------------------------------------------------- > > Key: ISPN-5682 > URL: https://issues.jboss.org/browse/ISPN-5682 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 8.0.0.Beta3 > Reporter: Jakub Markos > Assignee: Adrian Nistor > Fix For: 8.1.0.Final > > > This query > {code} > public void testGroupBy7() { > QueryFactory qf = getQueryFactory(); > Query q = qf.from(getModelFactory().getUserImplClass()) > .select(Expression.min("addresses.street")) > .having("name").eq("Spider").toBuilder() > .build(); > List<Object[]> list = q.list(); > assertEquals(list.get(0)[0], "Bond Street"); > } > {code} > returns in the context of QueryDslConditionsTest test class (https://github.com/infinispan/infinispan/blob/7634c0996cb3a174d2a379f2096...) the street "Old Street", while "Bond Street" is expected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5678) org.infinispan.functional javadocs not appearing

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-5678?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-5678: ------------------------------ Fix Version/s: 8.1.0.Final (was: 8.0.0.Final) > org.infinispan.functional javadocs not appearing > ------------------------------------------------ > > Key: ISPN-5678 > URL: https://issues.jboss.org/browse/ISPN-5678 > Project: Infinispan > Issue Type: Sub-task > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 8.1.0.Final > > > org.infinispan.functional javadocs missing in beta3 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues August 2015