[JBoss JIRA] (ISPN-9459) Remove compat mode from the Memcached server
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-9459?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-9459:
------------------------------------
Description:
The memcached server makes it hard to enable interoperability with other endpoints, as it stores keys as java.lang.String and treats byte[] as opaque values.
It should respect the cache storage configuration and provide a way to specify what is the data type of the value that clients sends and receive, in order to convert it to/from the storage format.
was:
The memcached server makes it hard to enable interoperability with other endpoints, as it stores keys as java.lang.String and treats byte[] as opaque values.
It should respect the cache storage configuration and provide a way to specify what is the data type of the value that clients sends and receive, in order to convert it to/from the storage format.
> Remove compat mode from the Memcached server
> --------------------------------------------
>
> Key: ISPN-9459
> URL: https://issues.jboss.org/browse/ISPN-9459
> Project: Infinispan
> Issue Type: Sub-task
> Components: Memcached
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
>
> The memcached server makes it hard to enable interoperability with other endpoints, as it stores keys as java.lang.String and treats byte[] as opaque values.
> It should respect the cache storage configuration and provide a way to specify what is the data type of the value that clients sends and receive, in order to convert it to/from the storage format.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (ISPN-9459) Remove compat mode from the Memcached server
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-9459?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-9459:
------------------------------------
Description:
The memcached server makes it hard to enable interoperability with other endpoints, as it stores keys as java.lang.String and treats byte[] as opaque values.
It should respect the cache storage configuration and provide a way to specify what is the data type of the value that clients sends and receive, in order to convert it to/from the storage format.
was:
The memcached server makes it hard to enable interoperability with other endpoints, as it stores keys as java.lang.String and treats byte[] as opaque values.
It should respect the cache configuration storage configuration and provide a way to specify what is the data type of the value that clients sends and receive, in order to convert it to/from the storage format.
> Remove compat mode from the Memcached server
> --------------------------------------------
>
> Key: ISPN-9459
> URL: https://issues.jboss.org/browse/ISPN-9459
> Project: Infinispan
> Issue Type: Sub-task
> Components: Memcached
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
>
> The memcached server makes it hard to enable interoperability with other endpoints, as it stores keys as java.lang.String and treats byte[] as opaque values.
> It should respect the cache storage configuration and provide a way to specify what is the data type of the value that clients sends and receive, in order to convert it to/from the storage format.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (ISPN-9460) Exceptions thrown in post listener should always be ignored and logged
by William Burns (JIRA)
William Burns created ISPN-9460:
-----------------------------------
Summary: Exceptions thrown in post listener should always be ignored and logged
Key: ISPN-9460
URL: https://issues.jboss.org/browse/ISPN-9460
Project: Infinispan
Issue Type: Bug
Components: Listeners
Reporter: William Burns
Today we allow a sorta way to block operations by a listener throwing an exception. This only sorta works with pre events though (which are local only). However this has allowed for post events to throw exceptions and put data in possibly an unknown state (especially around clustered listeners).
We should ensure that during post event listener invocations that we always ignore exceptions and log them even if it is sync.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (ISPN-9460) Exceptions thrown in post listener should always be ignored and logged
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-9460?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-9460:
--------------------------------
Description:
Today we allow a sorta way to block operations by a listener throwing an exception. This only works with pre events though (which are local only). However this has allowed for post events to throw exceptions and put data in possibly an unknown state (especially around clustered listeners).
We should ensure that during post event listener invocations that we always ignore exceptions and log them even if it is sync.
was:
Today we allow a sorta way to block operations by a listener throwing an exception. This only sorta works with pre events though (which are local only). However this has allowed for post events to throw exceptions and put data in possibly an unknown state (especially around clustered listeners).
We should ensure that during post event listener invocations that we always ignore exceptions and log them even if it is sync.
> Exceptions thrown in post listener should always be ignored and logged
> ----------------------------------------------------------------------
>
> Key: ISPN-9460
> URL: https://issues.jboss.org/browse/ISPN-9460
> Project: Infinispan
> Issue Type: Bug
> Components: Listeners
> Reporter: William Burns
>
> Today we allow a sorta way to block operations by a listener throwing an exception. This only works with pre events though (which are local only). However this has allowed for post events to throw exceptions and put data in possibly an unknown state (especially around clustered listeners).
> We should ensure that during post event listener invocations that we always ignore exceptions and log them even if it is sync.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (ISPN-9459) Remove compat mode from the Memcached server
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-9459?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-9459:
------------------------------------
Parent: ISPN-7940
Issue Type: Sub-task (was: Bug)
> Remove compat mode from the Memcached server
> --------------------------------------------
>
> Key: ISPN-9459
> URL: https://issues.jboss.org/browse/ISPN-9459
> Project: Infinispan
> Issue Type: Sub-task
> Components: Memcached
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
>
> The memcached server makes it hard to enable interoperability with other endpoints, as it stores keys as java.lang.String and treats byte[] as opaque values.
> It should respect the cache configuration storage configuration and provide a way to specify what is the data type of the value that clients sends and receive, in order to convert it to/from the storage format.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (ISPN-9459) Remove compat mode from the Memcached server
by Gustavo Fernandes (JIRA)
Gustavo Fernandes created ISPN-9459:
---------------------------------------
Summary: Remove compat mode from the Memcached server
Key: ISPN-9459
URL: https://issues.jboss.org/browse/ISPN-9459
Project: Infinispan
Issue Type: Bug
Components: Memcached
Reporter: Gustavo Fernandes
Assignee: Gustavo Fernandes
The memcached server makes it hard to enable interoperability with other endpoints, as it stores keys as java.lang.String and treats byte[] as opaque values.
It should respect the cache configuration storage configuration and provide a way to specify what is the data type of the value that clients sends and receive, in order to convert it to/from the storage format.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (ISPN-9458) Remove wrapping of bytes from Multimap operation
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-9458?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes reassigned ISPN-9458:
---------------------------------------
Assignee: Gustavo Fernandes
> Remove wrapping of bytes from Multimap operation
> ------------------------------------------------
>
> Key: ISPN-9458
> URL: https://issues.jboss.org/browse/ISPN-9458
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
>
> Currently in the Hot Rod server the multimaps are maintained as:
> {code:java}
> EmbeddedMultimapCache<WrappedByteArray, WrappedByteArray>
> {code}
> And multimap implementation does wrapping and unwrapping of byte[] into WrappedByteArray.
> This conversion should be delegated to the underlying cache's DataConversion instead
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (ISPN-9458) Remove wrapping of bytes from Multimap operation
by Gustavo Fernandes (JIRA)
Gustavo Fernandes created ISPN-9458:
---------------------------------------
Summary: Remove wrapping of bytes from Multimap operation
Key: ISPN-9458
URL: https://issues.jboss.org/browse/ISPN-9458
Project: Infinispan
Issue Type: Bug
Components: Server
Reporter: Gustavo Fernandes
Currently in the Hot Rod server the multimaps are maintained as:
{code:java}
EmbeddedMultimapCache<WrappedByteArray, WrappedByteArray>
{code}
And multimap implementation does wrapping and unwrapping of byte[] into WrappedByteArray.
This conversion should be delegated to the underlying cache's DataConversion instead
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (ISPN-9442) Scripts with JSON datatype should be able to read data as String by default
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-9442?page=com.atlassian.jira.plugin.... ]
Adrian Nistor updated ISPN-9442:
--------------------------------
Fix Version/s: 9.4.0.CR1
> Scripts with JSON datatype should be able to read data as String by default
> ---------------------------------------------------------------------------
>
> Key: ISPN-9442
> URL: https://issues.jboss.org/browse/ISPN-9442
> Project: Infinispan
> Issue Type: Enhancement
> Components: Tasks
> Affects Versions: 9.4.0.Beta1
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Fix For: 9.4.0.CR1
>
>
> ISPN-9182 introduced support for application/json as a script datatype, but the data is presented as byte[].
> When protobuf is the storage, it is possible to read data as JSON from scripts in the String form, by applying the "type" parameters to the MediaType: "application/json; type=java.lang.String", but this is not available for other storages.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (ISPN-9442) Scripts with JSON datatype should be able to read data as String by default
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-9442?page=com.atlassian.jira.plugin.... ]
Adrian Nistor updated ISPN-9442:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
Integrated in master. Thanks [~gustavonalle]!
> Scripts with JSON datatype should be able to read data as String by default
> ---------------------------------------------------------------------------
>
> Key: ISPN-9442
> URL: https://issues.jboss.org/browse/ISPN-9442
> Project: Infinispan
> Issue Type: Enhancement
> Components: Tasks
> Affects Versions: 9.4.0.Beta1
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Fix For: 9.4.0.CR1
>
>
> ISPN-9182 introduced support for application/json as a script datatype, but the data is presented as byte[].
> When protobuf is the storage, it is possible to read data as JSON from scripts in the String form, by applying the "type" parameters to the MediaType: "application/json; type=java.lang.String", but this is not available for other storages.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months