June 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6294) Query DSL should allow easy 'continuation' to assist with creating dynamic queries

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6294?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6294: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Query DSL should allow easy 'continuation' to assist with creating dynamic queries > ---------------------------------------------------------------------------------- > > Key: ISPN-6294 > URL: https://issues.jboss.org/browse/ISPN-6294 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Reporter: Adrian Nistor > Fix For: 9.4.0.Final > > > Conditional chaining of DSL conditions is cumbersome, as shown here: https://github.com/infinispan/infinispan/blob/af7f38ba1cf538be6b08d7b895f... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6279) Refactor CacheLoader API to make it thread safe

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6279?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6279: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Refactor CacheLoader API to make it thread safe > ----------------------------------------------- > > Key: ISPN-6279 > URL: https://issues.jboss.org/browse/ISPN-6279 > Project: Infinispan > Issue Type: Feature Request > Components: Loaders and Stores > Reporter: Sebastian Łaskawiec > Priority: Minor > Fix For: 9.4.0.Final > > > h3. Introduction > Currently {{CacheLoader}} thread safety can be easily compromised by broken implementations. We should provide a better implementation to make it more convenient and less error prone. > h3. Problem statement > CacheLoader API looks like this: > {code} > public interface AdvancedCacheLoader<K, V> extends CacheLoader<K, V> { > ... > void process(KeyFilter<? super K> filter, CacheLoaderTask<K, V> task, Executor executor, boolean fetchValue, boolean fetchMetadata); > ... > } > {code} > The CacheLoader implementation controls {{CacheLoaderTask}} as well as the number of threads used for processing (specified by {{Executor}}). If one wants to collect all keys (similarly to [AdvancedCacheLoader|https://github.com/infinispan/infinispan/blob/master/...]) it is very easy to hit concurrently issues while adding them to the set (See previous JIRAs: ISPN-3938 and ISPN-6276). > h3. Solution > The solution should take away currently control (Executor) and keyset (the simplest idea is to add it to {{CacheLoaderTask}}) from from the implementation. One of the ideas is to create a Lambda expression for pulling records from Cache Store. Note that similar changes will need to be performed to {{CacheWriter}} (to make it similar). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6224) Simplify configuration of Query with Indexing Affinity

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6224?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6224: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Simplify configuration of Query with Indexing Affinity > ------------------------------------------------------ > > Key: ISPN-6224 > URL: https://issues.jboss.org/browse/ISPN-6224 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Reporter: Sanne Grinovero > Fix For: 9.4.0.Final > > > We should try to enable the "Index Affinity" capabilities in an easier way from a configuration point of view. > For example I wonder if the capabilities provided by the {{AffinityPartitioner}} could not be enabled by default, for example automatically decorating any user defined {{HashFunctionPartitioner}} so that people can't neither forget to enable it, nor override it. > Second, should it be enabled by default when the cache configuration suggests it, for example in most clustered caches? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6220) Speedup index rebuilds but using ADD rather than UPDATE statements when safe

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6220?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6220: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Speedup index rebuilds but using ADD rather than UPDATE statements when safe > ---------------------------------------------------------------------------- > > Key: ISPN-6220 > URL: https://issues.jboss.org/browse/ISPN-6220 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Reporter: Sanne Grinovero > Fix For: 9.4.0.Final > > > The {{DistributedExecutorMassIndexer}} relies on update commands to index the new entries, but when we just run a full purge of the index it should be safe to use Add commands instead if we know that there aren't concurrent updates. > The lack of concurrent updates might be tricky but I think we can find such a condition when using Affinity as the index is being fully controlled by the current indexing engine, similarly to the checks to see if it's safe to use an NRT workspace. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6809) Monitor indexing status

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6809?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6809: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Monitor indexing status > ----------------------- > > Key: ISPN-6809 > URL: https://issues.jboss.org/browse/ISPN-6809 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Reporter: Pedro Zapata > Assignee: Vladimir Blagojevic > Fix For: 9.4.0.Final > > > Status of mass indexer and index status should be displayed per cache. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

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

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6639?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6639: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.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 > Fix For: 9.4.0.Final > > > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6638) Implement multi-tenancy for Web Sockets

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6638?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6638: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Implement multi-tenancy for Web Sockets > --------------------------------------- > > Key: ISPN-6638 > URL: https://issues.jboss.org/browse/ISPN-6638 > Project: Infinispan > Issue Type: Sub-task > Components: Server > Reporter: Sebastian Łaskawiec > Priority: Optional > Fix For: 9.4.0.Final > > > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6635) Multi tenancy

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6635?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6635: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Multi tenancy > ------------- > > Key: ISPN-6635 > URL: https://issues.jboss.org/browse/ISPN-6635 > Project: Infinispan > Issue Type: Feature Request > Components: Server > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Fix For: 9.4.0.Final > > > Hosting Infinispan as a Service requires support of multi tenancy. > The design for this feature might be found here: https://github.com/infinispan/infinispan/wiki/Multi-tenancy-for-Hotrod-Se... > And implementation plan in the subtasks. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6585) Persistence support in functional API

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6585?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6585: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Persistence support in functional API > ------------------------------------- > > Key: ISPN-6585 > URL: https://issues.jboss.org/browse/ISPN-6585 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Reporter: Radim Vansa > Assignee: Galder Zamarreño > Fix For: 9.4.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6479) CacheRpcCommandExternalizer should cache the cache name bytes

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6479?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6479: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > CacheRpcCommandExternalizer should cache the cache name bytes > ------------------------------------------------------------- > > Key: ISPN-6479 > URL: https://issues.jboss.org/browse/ISPN-6479 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 8.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.4.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 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 June 2018