April 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5521) Upgrade to Hibernate ORM 5.0.9.Final

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-5521?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-5521: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4243 > Upgrade to Hibernate ORM 5.0.9.Final > ------------------------------------ > > Key: ISPN-5521 > URL: https://issues.jboss.org/browse/ISPN-5521 > Project: Infinispan > Issue Type: Component Upgrade > Components: Loaders and Stores > Reporter: Sanne Grinovero > Assignee: Tristan Tarrant > Fix For: 9.0.0.Alpha2 > > > I'm opening this to make sure we keep Infinispan aligned with the other platforms, now moving to Hibernate 5. > This affects at least the JPA CacheStore, I'm not sure if other components. > Among many improvements, noticeable for Infinispan there is better OSGi support. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5521) Upgrade to Hibernate ORM 5.0.9.Final

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-5521?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-5521: ---------------------------------- Status: Open (was: New) > Upgrade to Hibernate ORM 5.0.9.Final > ------------------------------------ > > Key: ISPN-5521 > URL: https://issues.jboss.org/browse/ISPN-5521 > Project: Infinispan > Issue Type: Component Upgrade > Components: Loaders and Stores > Reporter: Sanne Grinovero > Assignee: Tristan Tarrant > Fix For: 9.0.0.Alpha2 > > > I'm opening this to make sure we keep Infinispan aligned with the other platforms, now moving to Hibernate 5. > This affects at least the JPA CacheStore, I'm not sure if other components. > Among many improvements, noticeable for Infinispan there is better OSGi support. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6509) Configuration of write-behind cachestore threading should refer to executors by name

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-6509: ------------------------------------- Summary: Configuration of write-behind cachestore threading should refer to executors by name Key: ISPN-6509 URL: https://issues.jboss.org/browse/ISPN-6509 Project: Infinispan Issue Type: Enhancement Components: Configuration, Documentation-Core, Loaders and Stores Reporter: Sanne Grinovero Assignee: Tristan Tarrant The configuration for the {{write-behind}} settings are documented as having for example the following format: {code:xml}<write-behind flush-lock-timeout="12321" modification-queue-size="123" shutdown-timeout="321" thread-pool-size="23" />{code} I believe this should rather hallow to refer an executor by name, so that executors can be defined in the executors sections and allow (and encourage) people to reuse the executors across multiple cachestores if that makes sense. We probably could also validate that it's not allowed to pick some specific executors, for example I believe some choices could lead to deadlocks. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5521) Upgrade to Hibernate ORM 5.0.9.Final

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-5521?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-5521: ---------------------------------- Summary: Upgrade to Hibernate ORM 5.0.9.Final (was: Upgrade to Hibernate ORM 5.0.1.Final) > Upgrade to Hibernate ORM 5.0.9.Final > ------------------------------------ > > Key: ISPN-5521 > URL: https://issues.jboss.org/browse/ISPN-5521 > Project: Infinispan > Issue Type: Component Upgrade > Components: Loaders and Stores > Reporter: Sanne Grinovero > Assignee: Tristan Tarrant > Fix For: 9.0.0.Alpha2 > > > I'm opening this to make sure we keep Infinispan aligned with the other platforms, now moving to Hibernate 5. > This affects at least the JPA CacheStore, I'm not sure if other components. > Among many improvements, noticeable for Infinispan there is better OSGi support. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5617) Clearly define which cachestores are shared and which are non-shared

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-5617?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on ISPN-5617: --------------------------------------- +1 I hope this gets considered as a natural next step, now that there's persistence of the View state, so that we can validate configurations against horrible nonsense. > Clearly define which cachestores are shared and which are non-shared > -------------------------------------------------------------------- > > Key: ISPN-5617 > URL: https://issues.jboss.org/browse/ISPN-5617 > Project: Infinispan > Issue Type: Task > Reporter: Tristan Tarrant > Fix For: 9.0.0.Alpha2 > > > Cache stores should explicitly declare if they work in shared or non-shared mode, so that unsupported configurations cannot be started. > See http://lists.jboss.org/pipermail/infinispan-dev/2015-July/016076.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5617) Clearly define which cachestores are shared and which are non-shared

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-5617?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-5617: ---------------------------------- Status: Open (was: New) > Clearly define which cachestores are shared and which are non-shared > -------------------------------------------------------------------- > > Key: ISPN-5617 > URL: https://issues.jboss.org/browse/ISPN-5617 > Project: Infinispan > Issue Type: Task > Reporter: Tristan Tarrant > Fix For: 9.0.0.Alpha2 > > > Cache stores should explicitly declare if they work in shared or non-shared mode, so that unsupported configurations cannot be started. > See http://lists.jboss.org/pipermail/infinispan-dev/2015-July/016076.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4247) JPA cachestore fails with Oracle12c and PostgreadPlus 9

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-4247?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on ISPN-4247: --------------------------------------- Is this still the case on Hibernate 5? I'm assuming this can be closed as out of date, please let me know if I'm wrong.. > JPA cachestore fails with Oracle12c and PostgreadPlus 9 > ------------------------------------------------------- > > Key: ISPN-4247 > URL: https://issues.jboss.org/browse/ISPN-4247 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Vojtech Juranek > Labels: 63gablocker > > JPA cache store fails on Oracle12c and PostgreadPlus 9 as Hibernate is not able to determine the dialect to be used: > {noformat} > [java] Caused by: org.hibernate.HibernateException: Unable to determine Dialect to use [name=Oracle, majorVersion=12]; user must register resolver or explicitly set 'hibernate.dialect' > {noformat} > resp. > {noformat} > [java] Caused by: org.hibernate.HibernateException: Unable to determine Dialect to use [name=EnterpriseDB, majorVersion=9]; user must register resolver or explicitly set 'hibernate.dialect' > {noformat} > To fix it, HIbernate upgrade is needed. PotgresPlus is fixed in 4.3.0.Beta4 (tracking JIRA is [HHH-8349|https://hibernate.atlassian.net/browse/HHH-8349]), Oracle12c is fixed in Hibernate 5.0.0 (tracking JIRA is [HHH-9044|https://hibernate.atlassian.net/browse/HHH-9044]) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4247) JPA cachestore fails with Oracle12c and PostgreadPlus 9

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-4247?page=com.atlassian.jira.plugin.... ] Sanne Grinovero resolved ISPN-4247. ----------------------------------- Resolution: Out of Date > JPA cachestore fails with Oracle12c and PostgreadPlus 9 > ------------------------------------------------------- > > Key: ISPN-4247 > URL: https://issues.jboss.org/browse/ISPN-4247 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Vojtech Juranek > Labels: 63gablocker > > JPA cache store fails on Oracle12c and PostgreadPlus 9 as Hibernate is not able to determine the dialect to be used: > {noformat} > [java] Caused by: org.hibernate.HibernateException: Unable to determine Dialect to use [name=Oracle, majorVersion=12]; user must register resolver or explicitly set 'hibernate.dialect' > {noformat} > resp. > {noformat} > [java] Caused by: org.hibernate.HibernateException: Unable to determine Dialect to use [name=EnterpriseDB, majorVersion=9]; user must register resolver or explicitly set 'hibernate.dialect' > {noformat} > To fix it, HIbernate upgrade is needed. PotgresPlus is fixed in 4.3.0.Beta4 (tracking JIRA is [HHH-8349|https://hibernate.atlassian.net/browse/HHH-8349]), Oracle12c is fixed in Hibernate 5.0.0 (tracking JIRA is [HHH-9044|https://hibernate.atlassian.net/browse/HHH-9044]) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6506) Cache the Lucene query instead of re-creating it from the filter's AST

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6506?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6506: -------------------------------- Description: The AST is already cached so the parsing effort is skipped for both param and param-less queries when are executed repeatedly. A further minor perf improvement can be achieved by caching also the output of the AST to Lucene transformation phase. This can only be done for queries without parameters (because the params would become bound to the Lucene query objects - which are immutable, btw). The Lucene transformation is a low complexity/effort process but even so it is better to skip it entirely when possible. was: The AST is already cached so most of the parsing effort is skipped for both param and param-less queries. A further minor perf improvement can be achieved by caching also the output of the AST to Lucene transformation phase. This can only be done for queries without parameters. > Cache the Lucene query instead of re-creating it from the filter's AST > ---------------------------------------------------------------------- > > Key: ISPN-6506 > URL: https://issues.jboss.org/browse/ISPN-6506 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 9.0.0.Alpha1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Alpha2, 9.0.0.Final > > > The AST is already cached so the parsing effort is skipped for both param and param-less queries when are executed repeatedly. > A further minor perf improvement can be achieved by caching also the output of the AST to Lucene transformation phase. This can only be done for queries without parameters (because the params would become bound to the Lucene query objects - which are immutable, btw). The Lucene transformation is a low complexity/effort process but even so it is better to skip it entirely when possible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6505) Test remote continuous query on a cache with compat mode enabled

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6505?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6505: -------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/4226 (was: https://github.com/infinispan/infinispan/pull/4241) > Test remote continuous query on a cache with compat mode enabled > ---------------------------------------------------------------- > > Key: ISPN-6505 > URL: https://issues.jboss.org/browse/ISPN-6505 > Project: Infinispan > Issue Type: Task > Components: Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 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 April 2016