February 2016 - infinispan-issues

[JBoss JIRA] (ISPN-6162) Drop Query.getResultSize() method

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6162?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6162: -------------------------------- Status: Open (was: New) > Drop Query.getResultSize() method > --------------------------------- > > Key: ISPN-6162 > URL: https://issues.jboss.org/browse/ISPN-6162 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying, Remote Querying > Reporter: Tristan Tarrant > Assignee: Adrian Nistor > Fix For: 9.0.0.Alpha1 > > > Do we keep org.infinispan.query.dsl.Query.getResultSize? Does it return int or long? Return -1 if actual figure unknown/hard to compute? Result size might be non-trivial for non-indexed or hybrid case and will require full scan even for queries with limit. Deprecate it now, remove in ispn 9. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6161) Indexes should be created only for annotated fields

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6161?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6161: -------------------------------- Status: Open (was: New) > Indexes should be created only for annotated fields > --------------------------------------------------- > > Key: ISPN-6161 > URL: https://issues.jboss.org/browse/ISPN-6161 > Project: Infinispan > Issue Type: Task > Components: Remote Querying > Reporter: Tristan Tarrant > Assignee: Adrian Nistor > Fix For: 9.0.0.Alpha1 > > > Modify behaviour of indexing for protobuf entities: Current behaviour is: if nothing is annotated then we index all fields;if some fields are annotated then index those fields only. New behaviour: index only the annotated fields. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6175) Server throwing warning about wrong eviction configuration

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-6175?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-6175: -------------------------------- Fix Version/s: 8.2.0.CR1 > Server throwing warning about wrong eviction configuration > ---------------------------------------------------------- > > Key: ISPN-6175 > URL: https://issues.jboss.org/browse/ISPN-6175 > Project: Infinispan > Issue Type: Bug > Components: Eviction, Server > Reporter: Martin Gencur > Assignee: William Burns > Priority: Minor > Fix For: 8.2.0.CR1 > > > After building the latest ISPN snapshot (HEAD == ISPN-6137 Fix ScriptMetadataTest.testBrokenParameters), the server throws the following warning: > ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > This happens whether I use default standalone.xml configuration or add eviction and passivation elements in the config. I.e. tried this config and still getting the warning: > {code} > <eviction strategy="LRU" size="1" type="COUNT"/> > <file-store passivation="true" path="dc" purge="true" shared="false"/> > {code} > It looks like the eviction is working properly, it's just the warning that makes confusion. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6175) Server throwing warning about wrong eviction configuration

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-6175?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-6175: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/3983 > Server throwing warning about wrong eviction configuration > ---------------------------------------------------------- > > Key: ISPN-6175 > URL: https://issues.jboss.org/browse/ISPN-6175 > Project: Infinispan > Issue Type: Bug > Components: Eviction, Server > Reporter: Martin Gencur > Assignee: William Burns > Priority: Minor > > After building the latest ISPN snapshot (HEAD == ISPN-6137 Fix ScriptMetadataTest.testBrokenParameters), the server throws the following warning: > ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > This happens whether I use default standalone.xml configuration or add eviction and passivation elements in the config. I.e. tried this config and still getting the warning: > {code} > <eviction strategy="LRU" size="1" type="COUNT"/> > <file-store passivation="true" path="dc" purge="true" shared="false"/> > {code} > It looks like the eviction is working properly, it's just the warning that makes confusion. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6175) Server throwing warning about wrong eviction configuration

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-6175?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-6175: -------------------------------- Status: Open (was: New) > Server throwing warning about wrong eviction configuration > ---------------------------------------------------------- > > Key: ISPN-6175 > URL: https://issues.jboss.org/browse/ISPN-6175 > Project: Infinispan > Issue Type: Bug > Components: Eviction, Server > Reporter: Martin Gencur > Assignee: William Burns > Priority: Minor > > After building the latest ISPN snapshot (HEAD == ISPN-6137 Fix ScriptMetadataTest.testBrokenParameters), the server throws the following warning: > ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > This happens whether I use default standalone.xml configuration or add eviction and passivation elements in the config. I.e. tried this config and still getting the warning: > {code} > <eviction strategy="LRU" size="1" type="COUNT"/> > <file-store passivation="true" path="dc" purge="true" shared="false"/> > {code} > It looks like the eviction is working properly, it's just the warning that makes confusion. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6175) Server throwing warning about wrong eviction configuration

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-6175?page=com.atlassian.jira.plugin.... ] Work on ISPN-6175 started by William Burns. ------------------------------------------- > Server throwing warning about wrong eviction configuration > ---------------------------------------------------------- > > Key: ISPN-6175 > URL: https://issues.jboss.org/browse/ISPN-6175 > Project: Infinispan > Issue Type: Bug > Components: Eviction, Server > Reporter: Martin Gencur > Assignee: William Burns > Priority: Minor > > After building the latest ISPN snapshot (HEAD == ISPN-6137 Fix ScriptMetadataTest.testBrokenParameters), the server throws the following warning: > ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > This happens whether I use default standalone.xml configuration or add eviction and passivation elements in the config. I.e. tried this config and still getting the warning: > {code} > <eviction strategy="LRU" size="1" type="COUNT"/> > <file-store passivation="true" path="dc" purge="true" shared="false"/> > {code} > It looks like the eviction is working properly, it's just the warning that makes confusion. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5809) View of cluster events

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-5809?page=com.atlassian.jira.plugin.... ] Pedro Zapata updated ISPN-5809: ------------------------------- Status: Open (was: New) > View of cluster events > ---------------------- > > Key: ISPN-5809 > URL: https://issues.jboss.org/browse/ISPN-5809 > Project: Infinispan > Issue Type: Sub-task > Components: Console > Reporter: Pedro Zapata > Assignee: Pedro Zapata > > As an Adminstrator, I want to view all cluster-split and cluster-merge events in the last 7 days. Each event should indicate the following information: time-stamp of event, Merge/Split, the cluster View before Merge/Split, the cluster View after Merge/Split. > Cluster events will be visualized as a summary in the cache containers page > https://rawgit.com/infinispan/infinispan-console-mockup/master/cache-cont... > and in the cluster list page > https://rawgit.com/infinispan/infinispan-console-mockup/master/clusters.html > A detailed ‘Grid events’ page will be added: > https://rawgit.com/infinispan/infinispan-console-mockup/master/events.html > Type of logs: > * Task execution (as requested by users) > * Node join/leave > * Split/Merge > * Rebalancing start / stop > * Mass indexer > * Server start/shutdown > * Site up / down > * Cache related events > Log properties: > * Timestamp > * Title > * Description > Logs will be of severity INFO and ERROR. > Logs will be stored in a persistent, eviction, 7 days expiration cache. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5809) View of cluster events

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-5809?page=com.atlassian.jira.plugin.... ] Pedro Zapata updated ISPN-5809: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/39 > View of cluster events > ---------------------- > > Key: ISPN-5809 > URL: https://issues.jboss.org/browse/ISPN-5809 > Project: Infinispan > Issue Type: Sub-task > Components: Console > Reporter: Pedro Zapata > Assignee: Pedro Zapata > > As an Adminstrator, I want to view all cluster-split and cluster-merge events in the last 7 days. Each event should indicate the following information: time-stamp of event, Merge/Split, the cluster View before Merge/Split, the cluster View after Merge/Split. > Cluster events will be visualized as a summary in the cache containers page > https://rawgit.com/infinispan/infinispan-console-mockup/master/cache-cont... > and in the cluster list page > https://rawgit.com/infinispan/infinispan-console-mockup/master/clusters.html > A detailed ‘Grid events’ page will be added: > https://rawgit.com/infinispan/infinispan-console-mockup/master/events.html > Type of logs: > * Task execution (as requested by users) > * Node join/leave > * Split/Merge > * Rebalancing start / stop > * Mass indexer > * Server start/shutdown > * Site up / down > * Cache related events > Log properties: > * Timestamp > * Title > * Description > Logs will be of severity INFO and ERROR. > Logs will be stored in a persistent, eviction, 7 days expiration cache. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6176) Rename DummyTransactionManager to something that better represents its properties

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/ISPN-6176?page=com.atlassian.jira.plugin.... ] Radoslav Husar reassigned ISPN-6176: ------------------------------------ Assignee: Tristan Tarrant > Rename DummyTransactionManager to something that better represents its properties > --------------------------------------------------------------------------------- > > Key: ISPN-6176 > URL: https://issues.jboss.org/browse/ISPN-6176 > Project: Infinispan > Issue Type: Enhancement > Components: Transactions > Reporter: Radoslav Husar > Assignee: Tristan Tarrant > Priority: Optional > Labels: ux > > I am under impression that DummyTransactionManager doesn't really stand for its name. It gives out an impression of stupid/fake/incomplete transaction manager implementation however one of its main properties is that it maintains its state in-memory only and has no persistent state. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6176) Rename DummyTransactionManager to something that better represents its properties

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/ISPN-6176?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated ISPN-6176: --------------------------------- Description: I am under impression that DummyTransactionManager doesn't really stand for its name. It gives out an impression of stupid/fake/incomplete transaction manager implementation however one of its main properties is that it maintains its state in-memory only and has no persistent state. (was: I am under impression that DummyTransactionManager doesn't really stand for its name. It gives out an impression of stupid/face/incomplete transaction manager implementation however one of its main properties is that it maintains its state in-memory only and has no persistent state.) > Rename DummyTransactionManager to something that better represents its properties > --------------------------------------------------------------------------------- > > Key: ISPN-6176 > URL: https://issues.jboss.org/browse/ISPN-6176 > Project: Infinispan > Issue Type: Enhancement > Components: Transactions > Reporter: Radoslav Husar > Priority: Optional > Labels: ux > > I am under impression that DummyTransactionManager doesn't really stand for its name. It gives out an impression of stupid/fake/incomplete transaction manager implementation however one of its main properties is that it maintains its state in-memory only and has no persistent state. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2016