August 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5537) Upgrade to Lucene 5

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5537?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5537: ------------------------------------ Fix Version/s: 8.0.0.Beta3 8.0.0.Final (was: 8.1.0.Final) > Upgrade to Lucene 5 > ------------------- > > Key: ISPN-5537 > URL: https://issues.jboss.org/browse/ISPN-5537 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying > Affects Versions: 8.0.0.Alpha1 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 8.0.0.Beta3, 8.0.0.Final > > > Update Infinispan directory to Lucene 5. Also required update to Hibernate Search 5.5.0.Alpha1, Hibernate ORM 5.0.0.CR3, Wildfly 10.0.0.Alpha6 (integration tests only) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5537) Upgrade to Lucene 5

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5537?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5537: ------------------------------------ Description: Update Infinispan directory to Lucene 5. Also required update to Hibernate Search 5.5.0.Alpha1, Hibernate ORM 5.0.0.CR3, Wildfly 10.0.0.Alpha6 (integration tests only) (was: Update Infinispan directory to Lucene 5) > Upgrade to Lucene 5 > ------------------- > > Key: ISPN-5537 > URL: https://issues.jboss.org/browse/ISPN-5537 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying > Affects Versions: 8.0.0.Alpha1 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 8.0.0.Beta3, 8.0.0.Final > > > Update Infinispan directory to Lucene 5. Also required update to Hibernate Search 5.5.0.Alpha1, Hibernate ORM 5.0.0.CR3, Wildfly 10.0.0.Alpha6 (integration tests only) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5668) Unable to sort on numeric field that can be null

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5668?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5668: ------------------------------------ Description: Currently test {QueryDslConditionsTest.testIsNullNumericWithProjection1} is disabled > Unable to sort on numeric field that can be null > ------------------------------------------------ > > Key: ISPN-5668 > URL: https://issues.jboss.org/browse/ISPN-5668 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 8.0.0.Beta3 > Reporter: Gustavo Fernandes > > Currently test {QueryDslConditionsTest.testIsNullNumericWithProjection1} is disabled -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5668) Unable to sort on numeric field that can be null

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5668?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5668: ------------------------------------ Description: Currently {{QueryDslConditionsTest.testIsNullNumericWithProjection1}} is disabled (was: Currently test {QueryDslConditionsTest.testIsNullNumericWithProjection1} is disabled) > Unable to sort on numeric field that can be null > ------------------------------------------------ > > Key: ISPN-5668 > URL: https://issues.jboss.org/browse/ISPN-5668 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 8.0.0.Beta3 > Reporter: Gustavo Fernandes > > Currently {{QueryDslConditionsTest.testIsNullNumericWithProjection1}} is disabled -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5668) Unable to sort on numeric field that can be null

by Gustavo Fernandes (JIRA)

Gustavo Fernandes created ISPN-5668: --------------------------------------- Summary: Unable to sort on numeric field that can be null Key: ISPN-5668 URL: https://issues.jboss.org/browse/ISPN-5668 Project: Infinispan Issue Type: Bug Components: Embedded Querying Affects Versions: 8.0.0.Beta3 Reporter: Gustavo Fernandes -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5553) Functional Java 8 API

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5553?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5553: ---------------------------------- Status: Open (was: New) > Functional Java 8 API > --------------------- > > Key: ISPN-5553 > URL: https://issues.jboss.org/browse/ISPN-5553 > Project: Infinispan > Issue Type: Feature Request > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 8.0.0.Beta3, 8.0.0.Final > > > Infinispan 8 is baselining on Java 8 and that enables a more advanced , functional, APIs to be built instead of relying on the traditional Map-like APIs. Such APIs, taking lambda functions, can improve on the current APIs in the following way: > * Being able to provide a write operation, where the operation is defined as a lambda, better enables conditional (CAS) like operations that are based in functions other than equality, e.g. version equality. If this functions can be executed atomically, they provide a better solution for Hot Rod version-based replace operations that currently can cause some weird behaviour (ISPN-4972) > * When operations are defined as lambdas, it's easier to move towards a model that tracks/replicates operations leading to state, rather than replicating state itself. This makes it easier to implement more-efficiently replicated alternative data structures, such as counts, lists...etc, and paths the way towards CRDTs, particularly CmRDT (Commutative Replicated Data Types) or operation-based CRDTs. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5553) Functional Java 8 API

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5553?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5553: ---------------------------------- Status: Pull Request Sent (was: Open) > Functional Java 8 API > --------------------- > > Key: ISPN-5553 > URL: https://issues.jboss.org/browse/ISPN-5553 > Project: Infinispan > Issue Type: Feature Request > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 8.0.0.Beta3, 8.0.0.Final > > > Infinispan 8 is baselining on Java 8 and that enables a more advanced , functional, APIs to be built instead of relying on the traditional Map-like APIs. Such APIs, taking lambda functions, can improve on the current APIs in the following way: > * Being able to provide a write operation, where the operation is defined as a lambda, better enables conditional (CAS) like operations that are based in functions other than equality, e.g. version equality. If this functions can be executed atomically, they provide a better solution for Hot Rod version-based replace operations that currently can cause some weird behaviour (ISPN-4972) > * When operations are defined as lambdas, it's easier to move towards a model that tracks/replicates operations leading to state, rather than replicating state itself. This makes it easier to implement more-efficiently replicated alternative data structures, such as counts, lists...etc, and paths the way towards CRDTs, particularly CmRDT (Commutative Replicated Data Types) or operation-based CRDTs. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5553) Functional Java 8 API

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5553?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5553: ---------------------------------- Fix Version/s: 8.0.0.Beta3 > Functional Java 8 API > --------------------- > > Key: ISPN-5553 > URL: https://issues.jboss.org/browse/ISPN-5553 > Project: Infinispan > Issue Type: Feature Request > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 8.0.0.Beta3, 8.0.0.Final > > > Infinispan 8 is baselining on Java 8 and that enables a more advanced , functional, APIs to be built instead of relying on the traditional Map-like APIs. Such APIs, taking lambda functions, can improve on the current APIs in the following way: > * Being able to provide a write operation, where the operation is defined as a lambda, better enables conditional (CAS) like operations that are based in functions other than equality, e.g. version equality. If this functions can be executed atomically, they provide a better solution for Hot Rod version-based replace operations that currently can cause some weird behaviour (ISPN-4972) > * When operations are defined as lambdas, it's easier to move towards a model that tracks/replicates operations leading to state, rather than replicating state itself. This makes it easier to implement more-efficiently replicated alternative data structures, such as counts, lists...etc, and paths the way towards CRDTs, particularly CmRDT (Commutative Replicated Data Types) or operation-based CRDTs. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5652) Change isEmpty to use anyMatch to prevent serializing entries

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5652?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5652: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Change isEmpty to use anyMatch to prevent serializing entries > ------------------------------------------------------------- > > Key: ISPN-5652 > URL: https://issues.jboss.org/browse/ISPN-5652 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Reporter: William Burns > Assignee: William Burns > Fix For: 8.0.0.Beta3 > > > isEmpty should use anyMatch so that we don't have to serialize all of the iterated values across the stream and allows for short circuiting of loops. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5343) Make eviction max-entries parameter configurable at runtime

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-5343?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-5343: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3639 > Make eviction max-entries parameter configurable at runtime > ----------------------------------------------------------- > > Key: ISPN-5343 > URL: https://issues.jboss.org/browse/ISPN-5343 > Project: Infinispan > Issue Type: Feature Request > Components: Eviction > Affects Versions: 7.2.0.Beta2 > Environment: Infinispan 7/ JDG > Reporter: Duncan Doyle > Assignee: Sebastian Łaskawiec > Fix For: 8.0.0.Final > > > I've got a use-case where I would like to be able to dynamically (at runtime) configure the max-entries parameter of my eviction configuration. This would allow to, for example, decrease the max-entries dynamically when my system starts running oom. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 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 August 2015