[JBoss JIRA] (ISPN-9010) Hibernate cache modules claim to be ASL while these are LGPL
by Radim Vansa (JIRA)
Radim Vansa created ISPN-9010:
---------------------------------
Summary: Hibernate cache modules claim to be ASL while these are LGPL
Key: ISPN-9010
URL: https://issues.jboss.org/browse/ISPN-9010
Project: Infinispan
Issue Type: Bug
Components: Hibernate Cache
Affects Versions: 9.2.1.Final
Reporter: Radim Vansa
Assignee: Tristan Tarrant
Some package-info.java files contains LGPL preamble and as the modules are ported from Hibernate ORM (which is LGPL) I think the license stays.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (ISPN-9011) Automate docker image release
by Gustavo Fernandes (JIRA)
Gustavo Fernandes created ISPN-9011:
---------------------------------------
Summary: Automate docker image release
Key: ISPN-9011
URL: https://issues.jboss.org/browse/ISPN-9011
Project: Infinispan
Issue Type: Enhancement
Components: Docker
Reporter: Gustavo Fernandes
Assignee: Gustavo Fernandes
Currently releasing the docker image involves:
- Changing the Dockerfile to bump Infinispan version
- Create a PR
- Wait for CI
- Merge PR
- Tag the repo with the desired version
Those steps should be handled by a script in a similar way that Infinispan does with its release.py script.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (ISPN-9009) Add test interrupting conflict resolution
by Dan Berindei (JIRA)
Dan Berindei created ISPN-9009:
----------------------------------
Summary: Add test interrupting conflict resolution
Key: ISPN-9009
URL: https://issues.jboss.org/browse/ISPN-9009
Project: Infinispan
Issue Type: Task
Components: Test Suite - Core
Affects Versions: 9.2.1.Final
Reporter: Dan Berindei
Assignee: Ryan Emerson
Fix For: 9.3.0.Alpha1
We need a test that starts conflict resolution and then crashes a node or starts another merge, to verify that conflict resolution is properly interrupted or restarted as necessary.
{{HotRodMergeTest}} was unintentionally testing this by starting the 2nd test before the 1st test's merge finished in all the server caches, but we need something more deterministic in core.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (ISPN-9009) Add test interrupting conflict resolution
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-9009?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-9009:
-------------------------------
Status: Open (was: New)
> Add test interrupting conflict resolution
> -----------------------------------------
>
> Key: ISPN-9009
> URL: https://issues.jboss.org/browse/ISPN-9009
> Project: Infinispan
> Issue Type: Task
> Components: Test Suite - Core
> Affects Versions: 9.2.1.Final
> Reporter: Dan Berindei
> Assignee: Ryan Emerson
> Fix For: 9.3.0.Alpha1
>
>
> We need a test that starts conflict resolution and then crashes a node or starts another merge, to verify that conflict resolution is properly interrupted or restarted as necessary.
> {{HotRodMergeTest}} was unintentionally testing this by starting the 2nd test before the 1st test's merge finished in all the server caches, but we need something more deterministic in core.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (ISPN-7420) Hot Rod enhancements for transcoding
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-7420?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-7420:
----------------------------------
Sprint: Sprint 9.3.0.Alpha1
> Hot Rod enhancements for transcoding
> ------------------------------------
>
> Key: ISPN-7420
> URL: https://issues.jboss.org/browse/ISPN-7420
> Project: Infinispan
> Issue Type: Feature Request
> Reporter: Galder Zamarreño
> Assignee: Gustavo Fernandes
>
> 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.5.0#75005)
6 years, 2 months
[JBoss JIRA] (ISPN-7420) Hot Rod enhancements for transcoding
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-7420?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-7420:
----------------------------------
Parent: (was: ISPN-7417)
Issue Type: Feature Request (was: Sub-task)
> Hot Rod enhancements for transcoding
> ------------------------------------
>
> Key: ISPN-7420
> URL: https://issues.jboss.org/browse/ISPN-7420
> Project: Infinispan
> Issue Type: Feature Request
> Reporter: Galder Zamarreño
> Assignee: Gustavo Fernandes
>
> 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.5.0#75005)
6 years, 2 months