February 2016 - infinispan-issues

[JBoss JIRA] (ISPN-5715) Perform AST caching for DSL queries with parameters

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5715?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5715: ---------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.2.0.Beta2) > Perform AST caching for DSL queries with parameters > --------------------------------------------------- > > Key: ISPN-5715 > URL: https://issues.jboss.org/browse/ISPN-5715 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying, Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.2.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5712) Remove buckets from JdbcBinaryStore

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5712?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5712: ---------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.2.0.Beta2) > Remove buckets from JdbcBinaryStore > ----------------------------------- > > Key: ISPN-5712 > URL: https://issues.jboss.org/browse/ISPN-5712 > Project: Infinispan > Issue Type: Enhancement > Components: Core, Loaders and Stores > Affects Versions: 7.2.4.Final, 8.0.0.CR1 > Reporter: Dan Berindei > Fix For: 8.2.0.CR1 > > > Unlike a file system, relational databases can easily deal with millions of entries in the same table, so there's no reason to group entries into buckets. > Some databases may not be able to index on a binary column, in which case the serialized key will need encoding (e.g. BASE64), but grouping entries by hash code should not be necessary. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5709) Support for running Infinispan as an Application in YARN

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5709?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5709: ---------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.2.0.Beta2) > Support for running Infinispan as an Application in YARN > -------------------------------------------------------- > > Key: ISPN-5709 > URL: https://issues.jboss.org/browse/ISPN-5709 > Project: Infinispan > Issue Type: Feature Request > Components: Hadoop Integration > Reporter: Gustavo Fernandes > Fix For: 8.2.0.CR1 > > > Hadoop 2.x allows custom "applications" to be managed by the resource scheduler framework. As an example, Apache Spark, Apache Tez, HBase and others can be bootstrapped and managed on top of Yarn. > Running on top of Yarn offers the following capabilities: > * Creating on demand (or long running) clusters with a simple command line, possibly targeting different versions and/or number of nodes > * Increase/Decrease the number of nodes as required > * Fine grained control of memory/CPU/disk/network utilized > * Submit arbitrary jobs targeting the application -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5704) Enhancements for Functional Map API

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5704?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5704: ---------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.2.0.Beta2) > Enhancements for Functional Map API > ----------------------------------- > > Key: ISPN-5704 > URL: https://issues.jboss.org/browse/ISPN-5704 > Project: Infinispan > Issue Type: Enhancement > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 8.2.0.CR1 > > > List of enhancements that didn't make it into 8.0: > * Transaction support. > * Verify locks are acquired for all operations (once tx is in place, locks can be checked easily) > * Complete persistence support (remove many returning previous, put many returning previous, remove many) > * Replication of per-invocation parameters. > * Port mode *Becoming*Test to functional APIs, and expand on testing other functional APIs. > * Test interoperability with cache, e.g. cache put with lifespan can be retrieved via functional map with lifespan, and viceversa > * Test compatibility mode > * Add more listener events: activation, passivation and expiration. > * Use check isLocal instead of `e == null` in command impls > * Fix branch skip issue (see previous PR: https://github.com/infinispan/infinispan/pull/3571) > * Add externalizers for primitive versions of Optional. > * ValueMatcherMode indexes in MarshallableFunctionExternalizers should be based on {{ordinal()}} calls to annotation. Also, could the core's enumeration use the annotations defined in commons? > * Add AdvancedExternalizer version for functions that takes value matcher > * Complete support for MetaCreated and MetaLastUsed (which should be separated into MetaLastModified and MetaLastAccessed) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5671) Implement missing RemoteCache read operations using near cache

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5671?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5671: ---------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.2.0.Beta2) > Implement missing RemoteCache read operations using near cache > -------------------------------------------------------------- > > Key: ISPN-5671 > URL: https://issues.jboss.org/browse/ISPN-5671 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 8.2.0.CR1 > > > For example: getAll, getWithMetadata, containsKey, getBulk, getAsync, values, retrieveEntries, and entrySet. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5665) Query should not rely on the results of return values of write commands

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5665?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5665: ---------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.2.0.Beta2) > Query should not rely on the results of return values of write commands > ----------------------------------------------------------------------- > > Key: ISPN-5665 > URL: https://issues.jboss.org/browse/ISPN-5665 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 8.0.0.Beta2 > Reporter: Dan Berindei > Assignee: Gustavo Fernandes > Fix For: 8.2.0.CR1 > > > The query interceptor relies on the return value of the write commands to know the previous value of the modified entries. This is not correct, because some write commands do not return the previous value, e.g. {{remove(key, value)}}, {{replace(key, oldValue, newValue)}}, and {{putAll(map)}}. > The query interceptor should instead look up the previous values in the invocation context, and also force the loading of old values in the invocation context if the command doesn't do it explicitly (e.g. {{putAll(map)}}, or {{put(k, v)}} with the {{IGNORE_RETURN_VALUES}} flag). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5657) Add missing embedded configuration elements to server schema

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5657?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5657: ---------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.2.0.Beta2) > Add missing embedded configuration elements to server schema > ------------------------------------------------------------ > > Key: ISPN-5657 > URL: https://issues.jboss.org/browse/ISPN-5657 > Project: Infinispan > Issue Type: Bug > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.2.0.CR1 > > > The embedded and server schema, while mostly compatible with each other, still differ in a number of aspects, e.g. store-as-binary, unsafe, etc. > The server should be able to parse these additional elements. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

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

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5642?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5642: ---------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.2.0.Beta2) > 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.2.0.CR1 > > > 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.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5617) Clearly define which cachestores are shared and which are non-shared

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5617?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5617: ---------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.2.0.Beta2) > Clearly define which cachestores are shared and which are non-shared > -------------------------------------------------------------------- > > Key: ISPN-5617 > URL: https://issues.jboss.org/browse/ISPN-5617 > Project: Infinispan > Issue Type: Task > Reporter: Tristan Tarrant > Fix For: 8.2.0.CR1 > > > Cache stores should explicitly declare if they work in shared or non-shared mode, so that unsupported configurations cannot be started. > See http://lists.jboss.org/pipermail/infinispan-dev/2015-July/016076.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5636) Test server modules against WildFly 10 Alpha

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5636?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5636: ---------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.2.0.Beta2) > Test server modules against WildFly 10 Alpha > -------------------------------------------- > > Key: ISPN-5636 > URL: https://issues.jboss.org/browse/ISPN-5636 > Project: Infinispan > Issue Type: Component Upgrade > Components: WildFly modules > Affects Versions: 8.0.0.Beta2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.2.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2016