February 2014 - infinispan-issues

[JBoss JIRA] (ISPN-3953) JPACacheStore should not load all entities in memory

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3953?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3953: -------------------------------- Labels: 630 (was: ) > JPACacheStore should not load all entities in memory > ---------------------------------------------------- > > Key: ISPN-3953 > URL: https://issues.jboss.org/browse/ISPN-3953 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Emmanuel Bernard > Assignee: Radim Vansa > Labels: 630 > > Today several methods use getResultList() and load either all keys or all entities for a given entity type in- memory at the same time. > This will likely blow up for big tables. > There are two solutions: > ## Use Hibernate's specific features > Hibernate ORM has a session.scroll() method that offers a FORWARD_ONLY scrollable result set. You can then load data and regularly (every 100?) clear the session before hitting the next result. This will diminish greatly the memory pressure. > ## Use a window model > get the number of entities in the table select count(*) > Then use setFirstResult / setMaxResults to navigate the data with a sliding window and clear the session every time you move the window. > This won't be as efficient as Hibernate ORM's specific approach but will do the work except on database that don't support the ability to start the results at the nth element. Look up Hibernate dialects for more info. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3954) Use Hibernate's StatelessSession for the JPACacheStore

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3954?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3954: -------------------------------- Labels: 630 (was: ) > Use Hibernate's StatelessSession for the JPACacheStore > ------------------------------------------------------ > > Key: ISPN-3954 > URL: https://issues.jboss.org/browse/ISPN-3954 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Emmanuel Bernard > Assignee: Radim Vansa > Labels: 630 > > The current model uses the regular session even though operations are tailored toward actions (insert, update, delete). > It would be better to make use of the Hibernate StatelessSession API which has been designed for these use cases. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-4010) Allow configuring the LevelDB cache store through JON

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-4010?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-4010: -------------------------------- Labels: 630 (was: ) > Allow configuring the LevelDB cache store through JON > ----------------------------------------------------- > > Key: ISPN-4010 > URL: https://issues.jboss.org/browse/ISPN-4010 > Project: Infinispan > Issue Type: Feature Request > Reporter: Mircea Markus > Assignee: William Burns > Labels: 630 > > Although a JON console can create a cache, the JON can not set a levelDB store configuration. Our customer wants to set a levelDB store setting using the JON when creating the cache. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3492) Upgrade JPA Cache Store to 6.0 API

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3492?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3492: -------------------------------- Labels: 630 (was: ) > Upgrade JPA Cache Store to 6.0 API > ---------------------------------- > > Key: ISPN-3492 > URL: https://issues.jboss.org/browse/ISPN-3492 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Ray Tsang > Assignee: Radim Vansa > Labels: 630 > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-4010) Allow configuring the LevelDB cache store through JON

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-4010?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-4010: -------------------------------- Assignee: William Burns (was: Mircea Markus) > Allow configuring the LevelDB cache store through JON > ----------------------------------------------------- > > Key: ISPN-4010 > URL: https://issues.jboss.org/browse/ISPN-4010 > Project: Infinispan > Issue Type: Feature Request > Reporter: Mircea Markus > Assignee: William Burns > > Although a JON console can create a cache, the JON can not set a levelDB store configuration. Our customer wants to set a levelDB store setting using the JON when creating the cache. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-4010) Allow configuring the LevelDB cache store through JON

by Mircea Markus (JIRA)

Mircea Markus created ISPN-4010: ----------------------------------- Summary: Allow configuring the LevelDB cache store through JON Key: ISPN-4010 URL: https://issues.jboss.org/browse/ISPN-4010 Project: Infinispan Issue Type: Feature Request Reporter: Mircea Markus Assignee: Mircea Markus Although a JON console can create a cache, the JON can not set a levelDB store configuration. Our customer wants to set a levelDB store setting using the JON when creating the cache. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3953) JPACacheStore should not load all entities in memory

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3953?page=com.atlassian.jira.plugin.... ] Mircea Markus commented on ISPN-3953: ------------------------------------- [~rvansa] I think we should still keep the name (JPA cache store) as from a user will only rely for JPA annotations/configurations for using this cache store. Relying on Hibernate directly is just an implementation detail. > JPACacheStore should not load all entities in memory > ---------------------------------------------------- > > Key: ISPN-3953 > URL: https://issues.jboss.org/browse/ISPN-3953 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Emmanuel Bernard > Assignee: Radim Vansa > > Today several methods use getResultList() and load either all keys or all entities for a given entity type in- memory at the same time. > This will likely blow up for big tables. > There are two solutions: > ## Use Hibernate's specific features > Hibernate ORM has a session.scroll() method that offers a FORWARD_ONLY scrollable result set. You can then load data and regularly (every 100?) clear the session before hitting the next result. This will diminish greatly the memory pressure. > ## Use a window model > get the number of entities in the table select count(*) > Then use setFirstResult / setMaxResults to navigate the data with a sliding window and clear the session every time you move the window. > This won't be as efficient as Hibernate ORM's specific approach but will do the work except on database that don't support the ability to start the results at the nth element. Look up Hibernate dialects for more info. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-4009) Implement a table-based role mapper for security

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-4009: ------------------------------------- Summary: Implement a table-based role mapper for security Key: ISPN-4009 URL: https://issues.jboss.org/browse/ISPN-4009 Project: Infinispan Issue Type: Feature Request Components: Security Reporter: Tristan Tarrant Assignee: Tristan Tarrant Also persist the mapping table to the server configuration -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3917) Allow execution of queries on non-indexed fields

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3917?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3917: -------------------------------- Labels: 6.3remotequeries (was: ) > Allow execution of queries on non-indexed fields > ------------------------------------------------ > > Key: ISPN-3917 > URL: https://issues.jboss.org/browse/ISPN-3917 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying > Reporter: William Burns > Assignee: Adrian Nistor > Labels: 6.3remotequeries > Fix For: 7.0.0.Final > > > The cluster listeners will want to use the Query DSL for filtering and projection views. We don't want to have to tie ourselves to Lucene to do this. It was discussed to implement this using reflection. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-4008) Server CLI should be based on WF/EAP CLI

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-4008: ------------------------------------- Summary: Server CLI should be based on WF/EAP CLI Key: ISPN-4008 URL: https://issues.jboss.org/browse/ISPN-4008 Project: Infinispan Issue Type: Task Components: CLI, Server Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 7.0.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

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 2014