October 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3732) Add support for the grouping API in Hot Rod

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-3732?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-3732: ------------------------------------ Fix Version/s: 7.0.0.Final (was: 7.0.0.CR2) > Add support for the grouping API in Hot Rod > ------------------------------------------- > > Key: ISPN-3732 > URL: https://issues.jboss.org/browse/ISPN-3732 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols > Reporter: Emmanuel Bernard > Assignee: Pedro Ruivo > Fix For: 7.0.0.Final > > > Hibernate OGM makes heavy use of AtomicMaps which can't be reproduced today in Hot Rod. > You can read the discussion on > http://lists.jboss.org/pipermail/infinispan-dev/2013-November/014080.html > and the follow up messages on this thread. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3843) Remove broadcast/unicast optimization in JGroupsTransport

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-3843?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-3843: ------------------------------------ Fix Version/s: 7.0.0.Final (was: 7.0.0.CR2) > Remove broadcast/unicast optimization in JGroupsTransport > --------------------------------------------------------- > > Key: ISPN-3843 > URL: https://issues.jboss.org/browse/ISPN-3843 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.0.Final > Reporter: Dan Berindei > Fix For: 7.0.0.Final > > > The broadcast/unicast optimization in JGroupsTransport can break the message ordering for regular messages, because NAKACK[2] and UNICAST[2|3] have their own ordering. > We should test if this optimization really brings any performance benefits and eliminate it, at least for asynchronous commands. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

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

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-3835?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-3835: ------------------------------------ Fix Version/s: 7.0.0.Final (was: 7.0.0.CR2) > 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 > Assignee: Gustavo Fernandes > Priority: Critical > Labels: 64QueryBlockers > Fix For: 7.0.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 (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3851) Write tests for REST server using timeToLiveSeconds=0

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-3851?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-3851: ------------------------------------ Fix Version/s: (was: 7.0.0.CR2) > Write tests for REST server using timeToLiveSeconds=0 > ----------------------------------------------------- > > Key: ISPN-3851 > URL: https://issues.jboss.org/browse/ISPN-3851 > Project: Infinispan > Issue Type: Task > Components: Remote Protocols > Affects Versions: 6.0.0.Final > Reporter: Dan Berindei > Assignee: Galder Zamarreño > Fix For: 7.0.0.Final > > > ISPN-3786 fixed an issue with timeToLiveSeconds=0 being treated inconsistently, but more tests are needed. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3866) Parser60.parseStore() ignores store configurations if they are not a SingleFileStore or a ClusterLoader

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-3866?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-3866: ------------------------------------ Fix Version/s: 7.0.0.Final (was: 7.0.0.CR2) > Parser60.parseStore() ignores store configurations if they are not a SingleFileStore or a ClusterLoader > ------------------------------------------------------------------------------------------------------- > > Key: ISPN-3866 > URL: https://issues.jboss.org/browse/ISPN-3866 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Affects Versions: 6.0.1.Final > Reporter: Guillermo GARCIA OCHOA > Assignee: Tristan Tarrant > Priority: Critical > Fix For: 7.0.0.Final > > > The {{Parser60.parseStore()}} methods ignores all store definition that is not a {{SingleFileStore}} or a {{ClusterLoader}} > {code:java} > private void parseStore(final XMLExtendedStreamReader reader, final ConfigurationBuilderHolder holder) throws XMLStreamException { > ConfigurationBuilder builder = holder.getCurrentConfigurationBuilder(); > CacheLoader store = null; > Boolean fetchPersistentState = null; > Boolean ignoreModifications = null; > Boolean purgeOnStartup = null; > Boolean preload = null; > Boolean shared = null; > // Here it reads the attributes that the AbstractStoreConfiguration defines > for (int i = 0; i < reader.getAttributeCount(); i++) { > ParseUtils.requireNoNamespaceAttribute(reader, i); > String value = replaceProperties(reader.getAttributeValue(i)); > Attribute attribute = Attribute.forName(reader.getAttributeLocalName(i)); > ... > } > // Then it will use the read attributes (and parse the childrens tags) > // if and only if the configure store is a SingleFileStore or ClusterLoader > if (store != null) { > if (store instanceof SingleFileStore) { > ... > parseStoreChildren(reader, sfs); > } else if (store instanceof ClusterLoader) { > ... > parseLoaderChildren(reader, cscb); > } > } > } > {code} > This means that there is no way to set a configuration to my custom cache store with the default parser {{Parser60}}. > If there is another way to what I'm asking for, please let me know because in the documentation only refers to the {{SingleFileStore}} implementation. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3907) Define a Protobuf custom option for defining numeric IDs for types

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-3907?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-3907: ------------------------------------ Fix Version/s: (was: 7.0.0.CR2) > Define a Protobuf custom option for defining numeric IDs for types > ------------------------------------------------------------------ > > Key: ISPN-3907 > URL: https://issues.jboss.org/browse/ISPN-3907 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying > Affects Versions: 6.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.0.Final > > > Currently the wire format of all Protobuf encoded keys and values contains a header/envelope that has some metadata information, like the fully qualified type name (that is protobuf type name, not java) of the object encoded in the message. This information is needed so that the other end can decode the message. And we added it because the Protobuf spec assumes both ends are aware of the message type, which is not the case most of the time. > While this approach solves the problem nicely, it becomes very inefficient is the FQN is long, which is usually the case, as people tend to stick the domain name of their company + package app name into it. > Solution: provide alternative unique numeric IDs to all types. The IDs can be added to message type definitions in the protobuf schema and the user is in charge of guaranteeing their uniqueness while the system must check and enforce the uniqueness when a schema is registered ib the ProtobufMetadataManager. To do this we define a custom Protobuf Message type option that accepts a numeric value. If such a numeric ID was assigned to the type then when it is serialized in protobuf the system has to use this id in the header rather that the FQN string. > This option should not be mandatory. Existing apps should work without requiring source code changes or recompiling providing that the relevant jars are upgraded in both client and server to support the new header encoding. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3906) Do not place ProtobufValueWrapper instances in the cache

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-3906?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-3906: ------------------------------------ Fix Version/s: (was: 7.0.0.CR2) > Do not place ProtobufValueWrapper instances in the cache > -------------------------------------------------------- > > Key: ISPN-3906 > URL: https://issues.jboss.org/browse/ISPN-3906 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying > Affects Versions: 6.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.0.Final > > > ProtobufValueWrapper is only needed in order to provide a classbridge so we can integrate with Hibernate Search. Still, we should not need to wrap the protobuf encoded byte array put in the cache with this class. It should only be created as a temporary wrapper just before we feed the data to Hibernate Search. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3908) Security (Authentication, Authorization, Audit, Encryption)

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-3908?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-3908: ------------------------------------ Fix Version/s: (was: 7.0.0.CR2) > Security (Authentication, Authorization, Audit, Encryption) > ----------------------------------------------------------- > > Key: ISPN-3908 > URL: https://issues.jboss.org/browse/ISPN-3908 > Project: Infinispan > Issue Type: Task > Components: Core, Remote Protocols, Security, Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Critical > Labels: roadmap > Fix For: 7.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3941) Add pre-release stable version check for maven dependencies

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-3941?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-3941: ------------------------------------ Fix Version/s: 7.0.0.Final (was: 7.0.0.CR2) > Add pre-release stable version check for maven dependencies > ----------------------------------------------------------- > > Key: ISPN-3941 > URL: https://issues.jboss.org/browse/ISPN-3941 > Project: Infinispan > Issue Type: Enhancement > Components: Build process > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.0.Final > > > We need to enhance our maven build to perform the following dependecy checks before doing a release: > 1. no SNAPSHOT dependencies are used > 2. all dependencies are Final if the current build is a Final > Rule #2 might not be implementable for some external dependencies (some organizations use weird version schemes), so we might want to do this check only for org.jboss, org.infinispan artifact groups. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3927) rethinking ISPN transactions

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-3927?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-3927: ------------------------------------ Fix Version/s: (was: 7.0.0.CR2) > rethinking ISPN transactions > ---------------------------- > > Key: ISPN-3927 > URL: https://issues.jboss.org/browse/ISPN-3927 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Reporter: Mircea Markus > Assignee: Ion Savin > Labels: roadmap > Fix For: 7.0.0.Final > > > Umbrella JIRA for several transaction related improvements: > 1. Async options for commit/rollback > - they don't really make sense as a user you don't get any guarantee on the status of the transaction > - they complicate the code significantly > - I think they should be removed > 2. READ_COMMITTED > - it has the same performance as REPEATABLE_READ, but offers less guarantees. > - unlike REPEATABLE_READ, it also behaves inconsistently when the data is owned by transaction originator > - I think it should be removed > 3. Optimistic tx without Write Skew Check (WSC) > - well, without WSC the transactions are not optimistic by definition > - they are something else: an batch update of multiple key/values. If the batch is successful you know the update was atomic. If it failed you don't get any guarantee > - suggestion: optimistic tx should *always* have WSC enabled (no option to configure it) > - build our batching functionality on top of what currently is optimistic tx without WSC and document it as such > 4. Remove 1PC option > - I'm not totally sure about it, but does it really make sense to have 1PC as an option? they don't offer any consistency guarantees so async API + non tx do about the same thing > [1] http://markmail.org/thread/a7fjko4dyejxqgdy > [2] https://github.com/infinispan/infinispan/pull/2177 > [3] http://infinispan.markmail.org/thread/nl2bs7rjvayjcybv > [4] http://infinispan.markmail.org/thread/vbg6g4otu7djazbc -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 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 October 2014