May 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7833) Adjust server node icons according to UI/X Patternfly guidelines

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7833?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-7833: -------------------------------------- Status: Open (was: New) > Adjust server node icons according to UI/X Patternfly guidelines > ---------------------------------------------------------------- > > Key: ISPN-7833 > URL: https://issues.jboss.org/browse/ISPN-7833 > Project: Infinispan > Issue Type: Sub-task > Components: Console > Affects Versions: 9.0.0.Final > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Fix For: 9.1.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7835) Adjust resource create modal dialogs (cache, server, task, endpoint etc) - follow Patternfly UI/X guidelines

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7835?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-7835: -------------------------------------- Status: Open (was: New) > Adjust resource create modal dialogs (cache, server, task, endpoint etc) - follow Patternfly UI/X guidelines > ------------------------------------------------------------------------------------------------------------ > > Key: ISPN-7835 > URL: https://issues.jboss.org/browse/ISPN-7835 > Project: Infinispan > Issue Type: Sub-task > Components: Console > Affects Versions: 9.0.0.Final > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Fix For: 9.1.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7832) Adjust cache card icons according to Patternfly UI/X guidelines

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7832?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-7832: -------------------------------------- Status: Open (was: New) > Adjust cache card icons according to Patternfly UI/X guidelines > --------------------------------------------------------------- > > Key: ISPN-7832 > URL: https://issues.jboss.org/browse/ISPN-7832 > Project: Infinispan > Issue Type: Sub-task > Components: Console > Affects Versions: 9.0.0.Final > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Fix For: 9.1.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7832) Adjust cache card icons according to Patternfly UI/X guidelines

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7832?page=com.atlassian.jira.plugin.... ] Work on ISPN-7832 started by Vladimir Blagojevic. ------------------------------------------------- > Adjust cache card icons according to Patternfly UI/X guidelines > --------------------------------------------------------------- > > Key: ISPN-7832 > URL: https://issues.jboss.org/browse/ISPN-7832 > Project: Infinispan > Issue Type: Sub-task > Components: Console > Affects Versions: 9.0.0.Final > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Fix For: 9.1.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5775) Clean shutdown cluster action

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-5775?page=com.atlassian.jira.plugin.... ] Work on ISPN-5775 started by Vladimir Blagojevic. ------------------------------------------------- > Clean shutdown cluster action > ----------------------------- > > Key: ISPN-5775 > URL: https://issues.jboss.org/browse/ISPN-5775 > Project: Infinispan > Issue Type: Sub-task > Components: Console > Reporter: Pedro Zapata > Assignee: Vladimir Blagojevic > > As an administrator, I want to gracefully shutdown the cluster for maintenance. For caches which have a cache-store configured, I want their data to get persisted without losing any data. For caches that do not have a cache store configured, data will be lost - therefore, I want prior warning before proceeding -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7829) Upgrade Administration Console UI/X using Patternfly best practices

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-7829?page=com.atlassian.jira.plugin.... ] Pedro Zapata updated ISPN-7829: ------------------------------- Status: Open (was: New) > Upgrade Administration Console UI/X using Patternfly best practices > ------------------------------------------------------------------- > > Key: ISPN-7829 > URL: https://issues.jboss.org/browse/ISPN-7829 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Affects Versions: 9.0.0.Final > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Fix For: 9.1.0.Final > > Attachments: InfinispanReview.pdf > > > Up to 9.0.0.Final Infinispan release we have mostly relied on common sense when it comes to UI/X of Administration Console. We have now feedback from Patternfly UI/X team and we should upgrade overall UI/X to the highest standard and the best UIX practices. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7879) Release.py fails on python 2.6.x

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7879?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7879: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Release.py fails on python 2.6.x > -------------------------------- > > Key: ISPN-7879 > URL: https://issues.jboss.org/browse/ISPN-7879 > Project: Infinispan > Issue Type: Bug > Components: Build process > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.1.0.Alpha1 > > > The release script fails on python 2.6 (the version currently used by CI) due to calls to super. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2133) Provide a context for object de-serialization

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-2133?page=com.atlassian.jira.plugin.... ] Sanne Grinovero edited comment on ISPN-2133 at 5/30/17 11:23 AM: ----------------------------------------------------------------- One more thought: traditionally such problems are solved by Java's standard Serialization. Imagine you're sending in bulk / batches, writing many objects which have some large string in common, or sharing any other large object. Standard serialization - including JBoss Marshalling - already do support object graphs and therefore re-materialize the object as one. So it could be that serializing all values of a batch / transaction / queue of operations into one single Blob is much more efficient than serializing multiple commands independently and pack them together after individual serialization; if we could improve on this, we'd be able to reap benefits at basically no API change cost. Incidentally there would be two benefits: * smaller payload on the wire * smaller heap consumption on the receiver's size, as same objects would be deserialized "as one" rather than being materialized as multiple copies Thinking about this, it implies that Infinispan might have a problem with "size amplification": if I estimate my object size locally to try to estimate how much space my data grid will need, I'm doing it wrong as the estimate we'd do today would not take into account of this size amplification. was (Author: sannegrinovero): One more thought: traditionally such problems are solved by Java's standard Serialization. Imagine you're sending in bulk / batches, writing many objects which have some large string in common, or sharing any other large object. Standard serialization - including JBoss Marshalling - already do support object graphs and therefore re-materialize the object as one. So it could be that serializing all values into one single Blob is much more efficient than serializing multiple commands independently; if we could do that, we'd be able to reap benefits at basically no API change cost. Incidentally there would be two benefits: * smaller payload on the wire * smaller heap consumption on the receiver's size, as same objects would be deserialized "as one" rather than being materialized as multiple copies Thinking about this, it implies that Infinispan might have a problem with "size amplification": if I estimate my object size locally to try to estimate how much space my data grid will need, I'm doing it wrong as the estimate we'd do today would not take into account of this size amplification. > Provide a context for object de-serialization > --------------------------------------------- > > Key: ISPN-2133 > URL: https://issues.jboss.org/browse/ISPN-2133 > Project: Infinispan > Issue Type: Feature Request > Components: Core, Marshalling > Reporter: Sanne Grinovero > Assignee: Galder Zamarreño > Labels: SLOWING_OGM, for_OGM > > See proposal description at > http://lists.jboss.org/pipermail/infinispan-dev/2012-June/010925.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2133) Provide a context for object de-serialization

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-2133?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on ISPN-2133: --------------------------------------- One more thought: traditionally such problems are solved by Java's standard Serialization. Imagine you're sending in bulk / batches, writing many objects which have some large string in common, or sharing any other large object. Standard serialization - including JBoss Marshalling - already do support object graphs and therefore re-materialize the object as one. So it could be that serializing all values into one single Blob is much more efficient than serializing multiple commands independently; if we could do that, we'd be able to reap benefits at basically no API change cost. Incidentally there would be two benefits: * smaller payload on the wire * smaller heap consumption on the receiver's size, as same objects would be deserialized "as one" rather than being materialized as multiple copies Thinking about this, it implies that Infinispan might have a problem with "size amplification": if I estimate my object size locally to try to estimate how much space my data grid will need, I'm doing it wrong as the estimate we'd do today would not take into account of this size amplification. > Provide a context for object de-serialization > --------------------------------------------- > > Key: ISPN-2133 > URL: https://issues.jboss.org/browse/ISPN-2133 > Project: Infinispan > Issue Type: Feature Request > Components: Core, Marshalling > Reporter: Sanne Grinovero > Assignee: Galder Zamarreño > Labels: SLOWING_OGM, for_OGM > > See proposal description at > http://lists.jboss.org/pipermail/infinispan-dev/2012-June/010925.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7879) Release.py fails on python 2.6.x

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7879?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-7879: ------------------------------- Status: Open (was: New) > Release.py fails on python 2.6.x > -------------------------------- > > Key: ISPN-7879 > URL: https://issues.jboss.org/browse/ISPN-7879 > Project: Infinispan > Issue Type: Bug > Components: Build process > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.1.0.Alpha1 > > > The release script fails on python 2.6 (the version currently used by CI) due to calls to super. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 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 May 2017