January 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7419) Enable system property replacement in Hot Rod configuration

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-7419: ------------------------------------- Summary: Enable system property replacement in Hot Rod configuration Key: ISPN-7419 URL: https://issues.jboss.org/browse/ISPN-7419 Project: Infinispan Issue Type: Enhancement Components: Remote Protocols Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 9.0.0.CR1 The Hot Rod configuration does not expand system properties. This should be enabled. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4663) Support JSR 107 keyType/valueType in Infinispan xml config

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4663?page=com.atlassian.jira.plugin.... ] Galder Zamarreño resolved ISPN-4663. ------------------------------------ Resolution: Deferred Will be implemented as part of ISPN-7418. > Support JSR 107 keyType/valueType in Infinispan xml config > ---------------------------------------------------------- > > Key: ISPN-4663 > URL: https://issues.jboss.org/browse/ISPN-4663 > Project: Infinispan > Issue Type: Bug > Reporter: Ryan Dunckel > Labels: hackathon > > There currently isn't an attribute/element on the infinispan xml config that can be used to set the expected keyType and valueType for type-safe caching. While this issue is being opened in the context of supporting JSR 107 type safe caches, it seems like a logical feature to support in infinispan core as well. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7418) Add per-cache key/value type information

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-7418: -------------------------------------- Summary: Add per-cache key/value type information Key: ISPN-7418 URL: https://issues.jboss.org/browse/ISPN-7418 Project: Infinispan Issue Type: Sub-task Reporter: Galder Zamarreño This part of the transcoding enhancement is related to the changes required to the core cache code to force the cache to store keys and values of a certain type. The type information should be defined via a MIME type, and should be configured by the user. A cache can only have a single key+value type combination. A single cache will not support storing data of different key and/or value types. Amongst other reasons, this is done for space efficiency. Once a cache can be configured with a specific key and value type, the user should be able to retrieve the value with an alternative MIME type. Behind the scenes, the cache should be able to transform the value from the give type to target type on the fly. As suggested in the wiki, there should be the possibility for the key/value type to be implicitly determined by the key+value type passed in during the first cache write. The aim of this is to enable remote clients to decide what the key+value type are upon writing to the cache for the first time, and hence avoid cache pre-configuration. Some transcoders might require additional configuration. The cache needs to be able to be configured with the necessary options to do on the fly transcoding for clients. E.g. schema for protobuf...etc. An important aspect here is that consistent hashing should not be affected by transcoding. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7417) Implement transcoding

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-7417: -------------------------------------- Summary: Implement transcoding Key: ISPN-7417 URL: https://issues.jboss.org/browse/ISPN-7417 Project: Infinispan Issue Type: Enhancement Reporter: Galder Zamarreño Assignee: Galder Zamarreño The aim of this JIRA is to implement transcoding so that data of any type can be stored and it can be transformed on the fly, regardless of the endpoint. The work of the JIRA will be split into different subtasks to be able to split the work. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7359) Allow cache statuses to be retrieved by profile at the container level

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7359?page=com.atlassian.jira.plugin.... ] Ryan Emerson commented on ISPN-7359: ------------------------------------ [~vblagojevic] I think it would still be a nice feature to have for CLI users and obviously we can simplify the console code if it is ever implemented. I'll keep it open but set the priority to optional. It could be a low-hanging fruit when we're exposing other cache info in the future. > Allow cache statuses to be retrieved by profile at the container level > ---------------------------------------------------------------------- > > Key: ISPN-7359 > URL: https://issues.jboss.org/browse/ISPN-7359 > Project: Infinispan > Issue Type: Enhancement > Components: JMX, reporting and management, Server > Affects Versions: 9.0.0.Beta1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Optional > > Currently to get the status of a cache, it's necessary to perform the following DMR request on a host/server that contains the cache: > `/host=master/server=server-one/subsystem=datagrid-infinispan/cache-container=container/distributed-cache=default:read-attribute(name=cache-availability)` > This is acceptable when the status of only a few cache's is required, however this can result in many management requests from the console etc if a container contains many cache's. Therefore we should expose a method at the profile level, that retrieves the status of all cache's within a given container. For example: > `profile=clustered/subsystem=datagrid-infinispan/cache-container=clustered:get-cache-statuses()` -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7066) The default cache configuration should not be applied to other caches

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7066?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7066: ---------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/4744, https://github.com/infinispan/infinispan/pull/4811 (was: https://github.com/infinispan/infinispan/pull/4744) > The default cache configuration should not be applied to other caches > --------------------------------------------------------------------- > > Key: ISPN-7066 > URL: https://issues.jboss.org/browse/ISPN-7066 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Affects Versions: 8.2.3.Final, 8.2.4.Final > Reporter: Vladimir Dzhuvinov > Assignee: Tristan Tarrant > Fix For: 9.0.0.Beta2, 9.0.0.Final > > > Hi guys, > We noticed a weird behaviour of the Infinispan config where caches that are configured with no persistence assume the persistence configuration of the default cache for the cache container. This can potentially lead to some serious errors as data put into the other caches is getting written into the store of the default cache. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6223) Create an integration test to verify that cache api is not needed for infinispan-embedded

by Vaclav Dedik (JIRA)

[ https://issues.jboss.org/browse/ISPN-6223?page=com.atlassian.jira.plugin.... ] Vaclav Dedik reassigned ISPN-6223: ---------------------------------- Assignee: Jakub Senko (was: Vaclav Dedik) Assigning all my issues to [~jsenko] as I am leaving Red Hat tomorrow. > Create an integration test to verify that cache api is not needed for infinispan-embedded > ----------------------------------------------------------------------------------------- > > Key: ISPN-6223 > URL: https://issues.jboss.org/browse/ISPN-6223 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 8.2.0.Beta1 > Reporter: Vaclav Dedik > Assignee: Jakub Senko > > See this PR: > https://github.com/infinispan/infinispan/pull/3897 > And this ticket: > https://issues.jboss.org/browse/ISPN-6025 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6796) Administration console - improve error messages when executing script

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6796?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic commented on ISPN-6796: ------------------------------------------- We should delegate this one [~rmacor] [~NadirX] as the fix has to come from server side in DMR. We (console) automatically parse the error and display whatever DMR response we get! > Administration console - improve error messages when executing script > --------------------------------------------------------------------- > > Key: ISPN-6796 > URL: https://issues.jboss.org/browse/ISPN-6796 > Project: Infinispan > Issue Type: Enhancement > Components: JMX, reporting and management > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Priority: Minor > > When executing javascript which results in error, the error message displayed by Administration console is not very helpful: > Error Some unexpected problem happened when launching the task: DGISPN0118: Failed to invoke operation: ISPN026003: Script execution error > Executing the same script through hotrod client throws more descriptive exception: > ReferenceError: "console" is not defined in <eval> at line number 4 > The script is: > console.debug("test"); -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7359) Allow cache statuses to be retrieved by profile at the container level

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7359?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-7359: ------------------------------- Priority: Optional (was: Major) > Allow cache statuses to be retrieved by profile at the container level > ---------------------------------------------------------------------- > > Key: ISPN-7359 > URL: https://issues.jboss.org/browse/ISPN-7359 > Project: Infinispan > Issue Type: Enhancement > Components: JMX, reporting and management, Server > Affects Versions: 9.0.0.Beta1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Optional > > Currently to get the status of a cache, it's necessary to perform the following DMR request on a host/server that contains the cache: > `/host=master/server=server-one/subsystem=datagrid-infinispan/cache-container=container/distributed-cache=default:read-attribute(name=cache-availability)` > This is acceptable when the status of only a few cache's is required, however this can result in many management requests from the console etc if a container contains many cache's. Therefore we should expose a method at the profile level, that retrieves the status of all cache's within a given container. For example: > `profile=clustered/subsystem=datagrid-infinispan/cache-container=clustered:get-cache-statuses()` -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6796) Administration console - improve error messages when executing script

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6796?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic commented on ISPN-6796: ------------------------------------------- We don't have this information available. We can only access whatever DMR gives us. Closing it. If this is a requirement reopen another issue where this info is provided in DMR. If it is provided it will be automatically shown in error dialog > Administration console - improve error messages when executing script > --------------------------------------------------------------------- > > Key: ISPN-6796 > URL: https://issues.jboss.org/browse/ISPN-6796 > Project: Infinispan > Issue Type: Enhancement > Components: JMX, reporting and management > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Priority: Minor > > When executing javascript which results in error, the error message displayed by Administration console is not very helpful: > Error Some unexpected problem happened when launching the task: DGISPN0118: Failed to invoke operation: ISPN026003: Script execution error > Executing the same script through hotrod client throws more descriptive exception: > ReferenceError: "console" is not defined in <eval> at line number 4 > The script is: > console.debug("test"); -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2017