January 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7391) Provide simple username/password/realm configuration attributes for the Hot Rod client

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-7391?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-7391: -------------------------------- Fix Version/s: 9.0.0.CR1 > Provide simple username/password/realm configuration attributes for the Hot Rod client > -------------------------------------------------------------------------------------- > > Key: ISPN-7391 > URL: https://issues.jboss.org/browse/ISPN-7391 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.CR1, 9.0.0.Final > > > Asking the user to specify a callback handler is overkill when most of the time he just needs username/password/realm. Allow these to be set easily by using an internal basic callbackhandler. This configuration would be mutually exclusive with an explicit callback handler -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7391) Provide simple username/password/realm configuration attributes for the Hot Rod client

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-7391?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-7391: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Provide simple username/password/realm configuration attributes for the Hot Rod client > -------------------------------------------------------------------------------------- > > Key: ISPN-7391 > URL: https://issues.jboss.org/browse/ISPN-7391 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.Final > > > Asking the user to specify a callback handler is overkill when most of the time he just needs username/password/realm. Allow these to be set easily by using an internal basic callbackhandler. This configuration would be mutually exclusive with an explicit callback handler -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7392) The policy elements are ignored in the server sasl configuration

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-7392?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-7392: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.CR1 Resolution: Done > The policy elements are ignored in the server sasl configuration > ---------------------------------------------------------------- > > Key: ISPN-7392 > URL: https://issues.jboss.org/browse/ISPN-7392 > Project: Infinispan > Issue Type: Bug > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.CR1 > > > Server SASL mech policies can be specified via properties or policy elements. When using the latter, the policy elements are not converted to the corresponding properties and applied to the mech config -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7402) Expose ProtobufMetadataManager.getFileErrors and ProtobufMetadataManager.getFilesWithErrors as DMR operations

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-7402?page=com.atlassian.jira.plugin.... ] Adrian Nistor commented on ISPN-7402: ------------------------------------- Anyway, thanks for spotting that. I'll make it throw a more meaningful exception in this case instead of the NPE. > Expose ProtobufMetadataManager.getFileErrors and ProtobufMetadataManager.getFilesWithErrors as DMR operations > ------------------------------------------------------------------------------------------------------------- > > Key: ISPN-7402 > URL: https://issues.jboss.org/browse/ISPN-7402 > Project: Infinispan > Issue Type: Enhancement > Components: Console, Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.CR1 > > Attachments: 7402.txt > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7402) Expose ProtobufMetadataManager.getFileErrors and ProtobufMetadataManager.getFilesWithErrors as DMR operations

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-7402?page=com.atlassian.jira.plugin.... ] Adrian Nistor commented on ISPN-7402: ------------------------------------- [~vblagojevic] The NPE you're getting now seems to indicate the service controller for the given cache-container is null, ie. the cache container is not running yet. Can you check ? > Expose ProtobufMetadataManager.getFileErrors and ProtobufMetadataManager.getFilesWithErrors as DMR operations > ------------------------------------------------------------------------------------------------------------- > > Key: ISPN-7402 > URL: https://issues.jboss.org/browse/ISPN-7402 > Project: Infinispan > Issue Type: Enhancement > Components: Console, Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.CR1 > > Attachments: 7402.txt > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7422) REST enhancements for transcoding

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-7422: -------------------------------------- Summary: REST enhancements for transcoding Key: ISPN-7422 URL: https://issues.jboss.org/browse/ISPN-7422 Project: Infinispan Issue Type: Sub-task Reporter: Galder Zamarreño Enhance the REST protocol: * Cache writes can provide key+value MIME type information. * Cache reads of values can provide MIME type information to transform data sent to the client on the fly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (HRJS-35) Implement transcoding Hot Rod changes

by Galder Zamarreño (JIRA)

Galder Zamarreño created HRJS-35: ------------------------------------ Summary: Implement transcoding Hot Rod changes Key: HRJS-35 URL: https://issues.jboss.org/browse/HRJS-35 Project: Infinispan Javascript client Issue Type: Enhancement Reporter: Galder Zamarreño Implement Hot Rod protocol changes to enable JS client to read data from Hot Rod in a particular MIME type, e.g. JSON. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7421) Make transcoders deployable in server

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-7421: -------------------------------------- Summary: Make transcoders deployable in server Key: ISPN-7421 URL: https://issues.jboss.org/browse/ISPN-7421 Project: Infinispan Issue Type: Sub-task Reporter: Galder Zamarreño Transcoder implementations created for ISPN-7418 should be deployable in server. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7420) Hot Rod enhancements for transcoding

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-7420: -------------------------------------- Summary: Hot Rod enhancements for transcoding Key: ISPN-7420 URL: https://issues.jboss.org/browse/ISPN-7420 Project: Infinispan Issue Type: Sub-task Reporter: Galder Zamarreño Several enhancements will need to be made to the Hot Rod protocol to work with transcoding: h3. Cache Writes (key + value) * Cache write operations that include values should have an optional parameter to be able to define the MIME type of the key and value that is being written. When the optional parameter is sent to the server, it will enable the server to implicitly discover what the types of the key+value are. * Once the first cache write has determined the key+value types, the clients do not need to send them again. If the client sends different types for the same cache, it should either result in the server ignoring it or an error (the former is preferable). * To avoid sending unnecessary data, advanced clients could cache the key+value type for a given cache after the first write request and then don't send it again. h3. Cache reads * Any operation that involves retrieving data should optionally take the type that the value should be transcoded to when returning it back to the client. This enables data to be read in different formats. * Within these operations, write operations that return previous values should be included. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

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

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7418?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-7418: ---------------------------------------- Something to consider: * If the cache has a MIME type configured for key/value, should a cache write be able to override it? Maybe only if its the first write? Needs some thought... > 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, 2 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