March 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9012) /bin/reversion.sh not compatible with MacOS

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-9012?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-9012: ------------------------------------ Summary: /bin/reversion.sh not compatible with MacOS (was: /bin/reversion.sh not compatible to MacOS) > /bin/reversion.sh not compatible with MacOS > ------------------------------------------- > > Key: ISPN-9012 > URL: https://issues.jboss.org/browse/ISPN-9012 > Project: Infinispan > Issue Type: Bug > Reporter: Gustavo Fernandes > > One idea is to rewrite this script in python. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-9012) /bin/reversion.sh not compatible to MacOS

by Gustavo Fernandes (JIRA)

Gustavo Fernandes created ISPN-9012: --------------------------------------- Summary: /bin/reversion.sh not compatible to MacOS Key: ISPN-9012 URL: https://issues.jboss.org/browse/ISPN-9012 Project: Infinispan Issue Type: Bug Reporter: Gustavo Fernandes One idea is to rewrite this script in python. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[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)

8 years

1
0
0 / 0

[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)

8 years

1
0
0 / 0

[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)

8 years

1
0
0 / 0

[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)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7940) Deprecate Compatibility Mode

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7940?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7940: ---------------------------------- Sprint: Sprint 9.3.0.Beta1 > Deprecate Compatibility Mode > ---------------------------- > > Key: ISPN-7940 > URL: https://issues.jboss.org/browse/ISPN-7940 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying, Remote Querying > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 9.3.0.Final > > > Compatibility Mode should be marked for removal and internally all the remaining usages should be routed to the related encoder -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[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)

8 years

1
0
0 / 0

[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)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8915) Support CORS in the REST server

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8915?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8915: ---------------------------------- Sprint: Sprint 9.3.0.CR1 (was: Sprint 9.3.0.Alpha1) > Support CORS in the REST server > ------------------------------- > > Key: ISPN-8915 > URL: https://issues.jboss.org/browse/ISPN-8915 > Project: Infinispan > Issue Type: Enhancement > Components: REST > Affects Versions: 9.2.0.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2018