July 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-57) Support Google App Engine

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-57?page=com.atlassian.jira.plugin.sy... ] Sanne Grinovero updated ISPN-57: -------------------------------- Assignee: Mircea Markus (was: Manik Surtani) > Support Google App Engine > ------------------------- > > Key: ISPN-57 > URL: https://issues.jboss.org/browse/ISPN-57 > Project: Infinispan > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Reporter: Adrian Cole > Assignee: Mircea Markus > > Google App Engine for Java is a restricted JVM. It prevents such things as file access and thread creation. Currently, Infinispan requires at least thread creation and depending on the cachestore mechanism, potentially file as well. > This is a container to investigate other related issues that may prevent Infinispan from running on GAE. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1302) Check cache store implementations if they profit by the improvements in FileCacheStore

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-1302?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-1302: ---------------------------------- Assignee: Dan Berindei (was: Manik Surtani) > Check cache store implementations if they profit by the improvements in FileCacheStore > -------------------------------------------------------------------------------------- > > Key: ISPN-1302 > URL: https://issues.jboss.org/browse/ISPN-1302 > Project: Infinispan > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Loaders and Stores > Affects Versions: 5.0.0.CR8 > Reporter: Robert Stupp > Assignee: Dan Berindei > Priority: Minor > > FileCacheStore has got a number of improvements > ISPN-1286 > ISPN-1288 > ISPN-1289 > ISPN-1290 > ISPN-1300 > ISPN-1301 > It should be checked, if other CacheStore implementation can benefit from these improvements. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-949) Have something like Hibernate's ResultTransformer for Query results

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-949?page=com.atlassian.jira.plugin.s... ] Sanne Grinovero resolved ISPN-949. ---------------------------------- Resolution: Won't Fix > Have something like Hibernate's ResultTransformer for Query results > ------------------------------------------------------------------- > > Key: ISPN-949 > URL: https://issues.jboss.org/browse/ISPN-949 > Project: Infinispan > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Embedded Querying > Reporter: Sanne Grinovero > Assignee: Manik Surtani > Priority: Minor > > Be able to transform an array of projected fields into a nice object. > So return a List<CustomBean>, instead of a List<Object[]> -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1401) Provide an easy API to retrieve the total numer of stored entried ( clusterWideSize() )

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-1401?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-1401: ---------------------------------- Assignee: Dan Berindei (was: Manik Surtani) > Provide an easy API to retrieve the total numer of stored entried ( clusterWideSize() ) > --------------------------------------------------------------------------------------- > > Key: ISPN-1401 > URL: https://issues.jboss.org/browse/ISPN-1401 > Project: Infinispan > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 5.1.0.FINAL > Reporter: Sanne Grinovero > Assignee: Dan Berindei > Priority: Minor > > This looks like easy to implement with a distributed executor and a common request. We will also need it as a building block. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1402) Limit rate of incoming requests on Hot Rod server

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-1402?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-1402: ---------------------------------- Assignee: Galder Zamarreño > Limit rate of incoming requests on Hot Rod server > ------------------------------------------------- > > Key: ISPN-1402 > URL: https://issues.jboss.org/browse/ISPN-1402 > Project: Infinispan > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Remote Protocols > Reporter: Sanne Grinovero > Assignee: Galder Zamarreño > Priority: Minor > > Like application servers have a way to configure a limit of parallel incoming requests, if a too high number of requests is incoming some of these should be put in a queue, to protect the server performance. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

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

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2133?page=com.atlassian.jira.plugin.... ] Dan Berindei edited comment on ISPN-2133 at 7/11/14 11:55 AM: -------------------------------------------------------------- We don't currently allow SPIs to use our injection mechanism, so we'd need to start a discussion about that before we can think about the injection option. Modifying the marshalling API to give the externalizer a reference to the cache manager would be possible, but I don't think doing a component lookup on every deserialization is a good idea. As a workaround, you can construct your externalizer with a reference to your service, and register it with {code} globalConfigBuilder.serialization().addAdvancedExternalizer(new CustomExternalizer(service)) {code} was (Author: dan.berindei): We don't currently allow SPIs to use our injection mechanism, so we'd need to start a discussion about that before we can think about the injection option. Modifying the marshalling API to give the externalizer a reference to the cache manager would be possible, but I don't think doing a component lookup on every deserialization is a good idea. As a workaround, you can construct your externalizer with a reference to your service, and register it with {{globalConfigBuilder.serialization().addAdvancedExternalizer(new CustomExternalizer(service))}}. > Provide a context for object de-serialization > --------------------------------------------- > > Key: ISPN-2133 > URL: https://issues.jboss.org/browse/ISPN-2133 > Project: Infinispan > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Reporter: Sanne Grinovero > Assignee: Manik Surtani > > See proposal description at > http://lists.jboss.org/pipermail/infinispan-dev/2012-June/010925.html -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

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

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2133?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-2133: ------------------------------------ We don't currently allow SPIs to use our injection mechanism, so we'd need to start a discussion about that before we can think about the injection option. Modifying the marshalling API to give the externalizer a reference to the cache manager would be possible, but I don't think doing a component lookup on every deserialization is a good idea. As a workaround, you can construct your externalizer with a reference to your service, and register it with {{globalConfigBuilder.serialization().addAdvancedExternalizer(new CustomExternalizer(service))}}. > Provide a context for object de-serialization > --------------------------------------------- > > Key: ISPN-2133 > URL: https://issues.jboss.org/browse/ISPN-2133 > Project: Infinispan > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Reporter: Sanne Grinovero > Assignee: Manik Surtani > > See proposal description at > http://lists.jboss.org/pipermail/infinispan-dev/2012-June/010925.html -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1790) Release script should not rip off comments from POM.XML files

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-1790?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-1790: ---------------------------------- Assignee: Dan Berindei (was: Manik Surtani) > Release script should not rip off comments from POM.XML files > ------------------------------------------------------------- > > Key: ISPN-1790 > URL: https://issues.jboss.org/browse/ISPN-1790 > Project: Infinispan > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Build process > Affects Versions: 5.1.0.FINAL > Reporter: Sanne Grinovero > Assignee: Dan Berindei > Priority: Minor > Labels: release.py > > Comparing the git commit which was used to release 5.1.0.Final to the final tag of the released version, reveals some changes which are likely unintended: > * All Copyright statements removed > * All comments removed (useful and unuseful) > * In some way changed the inlined scripts for Google analytics - not sure if it's still working -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1856) Allow independent configuration of buffer allocation size vs segment chunks maximum size

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-1856?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-1856: ---------------------------------- Labels: performance (was: ) > Allow independent configuration of buffer allocation size vs segment chunks maximum size > ---------------------------------------------------------------------------------------- > > Key: ISPN-1856 > URL: https://issues.jboss.org/browse/ISPN-1856 > Project: Infinispan > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Lucene Directory > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Labels: performance > > Especially make sure that we can allocate buffers efficiently when having chunk_size=MAX_INTEGER or other very high values. > Maybe reuse them as well? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1947) Automate staging repository step in release script

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-1947?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-1947: ---------------------------------- Assignee: Mircea Markus (was: Manik Surtani) > Automate staging repository step in release script > -------------------------------------------------- > > Key: ISPN-1947 > URL: https://issues.jboss.org/browse/ISPN-1947 > Project: Infinispan > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build process > Reporter: Sanne Grinovero > Assignee: Mircea Markus > Priority: Optional > > The following plugin can be used to control the staging repository from command line (including authenticating with your account as set in your settings file) > {code:xml} > <plugin> > <groupId>org.sonatype.plugins</groupId> > <artifactId>nexus-maven-plugin</artifactId> > <configuration> > <nexusUrl>https://repository.jboss.org/nexus</nexusUrl> > <automatic>true</automatic> > </configuration> > </plugin> > {code} > Goals are described at: https://repository.sonatype.org/content/sites/maven-sites/nexus-maven-plu... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2014