January 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3909) Authorization for Cache and CacheManager access

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-3909: ------------------------------------- Summary: Authorization for Cache and CacheManager access Key: ISPN-3909 URL: https://issues.jboss.org/browse/ISPN-3909 Project: Infinispan Issue Type: Sub-task Reporter: Tristan Tarrant Assignee: Mircea Markus -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3909) Authorization for Cache and CacheManager access

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3909?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-3909: ------------------------------------- Assignee: Tristan Tarrant (was: Mircea Markus) > Authorization for Cache and CacheManager access > ----------------------------------------------- > > Key: ISPN-3909 > URL: https://issues.jboss.org/browse/ISPN-3909 > Project: Infinispan > Issue Type: Sub-task > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

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

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-3908: ------------------------------------- Summary: Security (Authentication, Authorization, Encryption) Key: ISPN-3908 URL: https://issues.jboss.org/browse/ISPN-3908 Project: Infinispan Issue Type: Task Reporter: Tristan Tarrant Assignee: Mircea Markus Priority: Critical -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

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

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3908?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-3908: ------------------------------------- Assignee: Tristan Tarrant (was: Mircea Markus) > Security (Authentication, Authorization, Encryption) > ---------------------------------------------------- > > Key: ISPN-3908 > URL: https://issues.jboss.org/browse/ISPN-3908 > Project: Infinispan > Issue Type: Task > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Critical > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

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

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-3907: ----------------------------------- Summary: 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: Querying Affects Versions: 6.0.0.Final Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 7.0.0.Alpha1, 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

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

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3906?page=com.atlassian.jira.plugin.... ] Work on ISPN-3906 started by Adrian Nistor. > 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: Querying > Affects Versions: 6.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.0.Alpha1, 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

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

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-3906: ----------------------------------- Summary: 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: Querying Affects Versions: 6.0.0.Final Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 7.0.0.Alpha1, 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3905) Murmurhash3 implementation is slow on String keys

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-3905: ------------------------------------- Summary: Murmurhash3 implementation is slow on String keys Key: ISPN-3905 URL: https://issues.jboss.org/browse/ISPN-3905 Project: Infinispan Issue Type: Enhancement Affects Versions: 6.0.1.Final, 6.0.0.Final Reporter: Sanne Grinovero Assignee: Mircea Markus Fix For: 7.0.0.Final String instances are a common choice for being used as key entries, still the getBytes() operation being performed allocates costly buffers, and the computation to get those bytes looks like expensive too. I suspect there might be good reasons for not using the String's own hashcode directly as an input to Murmurhash? Still that's what other implementations seem to do. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2342) Cross-Site Replication: State Transfer between sites

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-2342?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-2342: ------------------------------ Summary: Cross-Site Replication: State Transfer between sites (was: The x-site implementation needs an inter-site state transfer mechanism) > Cross-Site Replication: State Transfer between sites > ---------------------------------------------------- > > Key: ISPN-2342 > URL: https://issues.jboss.org/browse/ISPN-2342 > Project: Infinispan > Issue Type: Feature Request > Components: Cross-Site Replication > Affects Versions: 6.0.1.Final > Reporter: Erik Salter > Assignee: Pedro Ruivo > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > To bring up a new site or recover a failed site, I need an inter-site state transfer mechanism for synchronizing keys. > Note that initially, this should a manual process that is invoked on one site to one of its configured backups. > This should be based on the non-blocking state transfer mechanism for consistency. > The pseudo-design may look similar to the following: > - Manually invokable, background thread > - Since the bridge end is open, there are writes happening to keys. Keep track of the puts/removes on the main data owner. > - Iterate through the key set. > - If the key has already been modified since the process started, discard. > - Else synchronously write the key value in a TX context -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2342) The x-site implementation needs an inter-site state transfer mechanism

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-2342?page=com.atlassian.jira.plugin.... ] Pedro Ruivo commented on ISPN-2342: ----------------------------------- Design document: https://github.com/infinispan/infinispan/wiki/Design-For-Cross-Site-Repli... > The x-site implementation needs an inter-site state transfer mechanism > ---------------------------------------------------------------------- > > Key: ISPN-2342 > URL: https://issues.jboss.org/browse/ISPN-2342 > Project: Infinispan > Issue Type: Feature Request > Components: Cross-Site Replication > Affects Versions: 6.0.1.Final > Reporter: Erik Salter > Assignee: Pedro Ruivo > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > To bring up a new site or recover a failed site, I need an inter-site state transfer mechanism for synchronizing keys. > Note that initially, this should a manual process that is invoked on one site to one of its configured backups. > This should be based on the non-blocking state transfer mechanism for consistency. > The pseudo-design may look similar to the following: > - Manually invokable, background thread > - Since the bridge end is open, there are writes happening to keys. Keep track of the puts/removes on the main data owner. > - Iterate through the key set. > - If the key has already been modified since the process started, discard. > - Else synchronously write the key value in a TX context -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 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 January 2014