November 2013 - infinispan-issues

[JBoss JIRA] (ISPN-3686) Fix the release script to upload the xsd

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3686?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3686: -------------------------------- Fix Version/s: (was: 6.0.0.CR2) > Fix the release script to upload the xsd > ---------------------------------------- > > Key: ISPN-3686 > URL: https://issues.jboss.org/browse/ISPN-3686 > Project: Infinispan > Issue Type: Task > Reporter: Mircea Markus > Assignee: Adrian Nistor > > I just noticed that our new website does not host the infinispan schemas > which should be at: > http://www.infinispan.org/schemas/infinispan-config-6.0.xsd > We need to fix the release script to handle this -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3622) Configuration schema is not published at documented URL

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3622?page=com.atlassian.jira.plugin.... ] Work on ISPN-3622 started by Adrian Nistor. > Configuration schema is not published at documented URL > ------------------------------------------------------- > > Key: ISPN-3622 > URL: https://issues.jboss.org/browse/ISPN-3622 > Project: Infinispan > Issue Type: Bug > Components: Configuration, Documentation > Affects Versions: 6.0.0.CR1 > Reporter: Sanne Grinovero > Assignee: Adrian Nistor > Priority: Critical > Fix For: 6.0.0.CR2, 6.0.0.Final > > > Some examples refer to URL http://www.infinispan.org/schemas/infinispan-config-6.0.xsd to find the XSD, but it's not there. > This combined with the missing documentation makes it quite a guesswork on how to configure it. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3686) Fix the release script to upload the xsd

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3686?page=com.atlassian.jira.plugin.... ] Adrian Nistor resolved ISPN-3686. --------------------------------- Resolution: Duplicate Issue > Fix the release script to upload the xsd > ---------------------------------------- > > Key: ISPN-3686 > URL: https://issues.jboss.org/browse/ISPN-3686 > Project: Infinispan > Issue Type: Task > Reporter: Mircea Markus > Assignee: Adrian Nistor > Fix For: 6.0.0.CR2 > > > I just noticed that our new website does not host the infinispan schemas > which should be at: > http://www.infinispan.org/schemas/infinispan-config-6.0.xsd > We need to fix the release script to handle this -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3708) The HotRod endpoint in Server doesn't return the cache set as default in the container configuration

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3708?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3708: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > The HotRod endpoint in Server doesn't return the cache set as default in the container configuration > ---------------------------------------------------------------------------------------------------- > > Key: ISPN-3708 > URL: https://issues.jboss.org/browse/ISPN-3708 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols, Server > Affects Versions: 6.0.0.CR1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 6.0.0.Final > > > The HotRod protocol defines that when a client requests a cache using an empty name ("") it should return the default cache. In embedded mode this is defined by a constant, but in server mode the default cache can be set in the container configuration. The HotRod server should allow setting a different cache to use as default -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3615) Add user documentation for the remote query modules

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3615?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3615: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Add user documentation for the remote query modules > --------------------------------------------------- > > Key: ISPN-3615 > URL: https://issues.jboss.org/browse/ISPN-3615 > Project: Infinispan > Issue Type: Task > Reporter: Mircea Markus > Assignee: Adrian Nistor > Fix For: 6.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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3713) Add an unit test to validate all the links within the documentation

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3713?page=com.atlassian.jira.plugin.... ] Adrian Nistor commented on ISPN-3713: ------------------------------------- I've already spotted a few broken links of the form <<sid-NUMBER,caption text>> which could be caused by the migration from the old CMS. > Add an unit test to validate all the links within the documentation > ------------------------------------------------------------------- > > Key: ISPN-3713 > URL: https://issues.jboss.org/browse/ISPN-3713 > Project: Infinispan > Issue Type: Feature Request > Reporter: Mircea Markus > Assignee: Mircea Markus > > This should make sure that all the links from the documentation are functional. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3708) The HotRod endpoint in Server doesn't return the cache set as default in the container configuration

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3708?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3708: ---------------------------------- Status: Pull Request Sent (was: Pull Request Sent) Git Pull Request: https://github.com/infinispan/infinispan/pull/2227, https://github.com/infinispan/infinispan-server/pull/189 (was: https://github.com/infinispan/infinispan/pull/2227) > The HotRod endpoint in Server doesn't return the cache set as default in the container configuration > ---------------------------------------------------------------------------------------------------- > > Key: ISPN-3708 > URL: https://issues.jboss.org/browse/ISPN-3708 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols, Server > Affects Versions: 6.0.0.CR1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 6.0.0.Final > > > The HotRod protocol defines that when a client requests a cache using an empty name ("") it should return the default cache. In embedded mode this is defined by a constant, but in server mode the default cache can be set in the container configuration. The HotRod server should allow setting a different cache to use as default -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3708) The HotRod endpoint in Server doesn't return the cache set as default in the container configuration

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3708?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3708: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2227 > The HotRod endpoint in Server doesn't return the cache set as default in the container configuration > ---------------------------------------------------------------------------------------------------- > > Key: ISPN-3708 > URL: https://issues.jboss.org/browse/ISPN-3708 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols, Server > Affects Versions: 6.0.0.CR1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 6.0.0.Final > > > The HotRod protocol defines that when a client requests a cache using an empty name ("") it should return the default cache. In embedded mode this is defined by a constant, but in server mode the default cache can be set in the container configuration. The HotRod server should allow setting a different cache to use as default -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3534) Investigate performance regressions in Infinispan 6.0.0

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-3534?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-3534: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Investigate performance regressions in Infinispan 6.0.0 > ------------------------------------------------------- > > Key: ISPN-3534 > URL: https://issues.jboss.org/browse/ISPN-3534 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 5.3.0.Final, 6.0.0.CR1 > Reporter: Mircea Markus > Assignee: Dan Berindei > Priority: Critical > Labels: 620 > Fix For: 6.0.0.Final > > > As per QE: > 30% performance regression in distributed, udp, tx, async library stress tests > 20% performance regression in distributed, udp, tx, sync library stress tests > 20% performance regression in memcached client stress tests > 50%+ performance regression in REST client stress > tests -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3718) Select which protobuf fields to index

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-3718: ----------------------------------- Summary: Select which protobuf fields to index Key: ISPN-3718 URL: https://issues.jboss.org/browse/ISPN-3718 Project: Infinispan Issue Type: Feature Request Components: Querying Reporter: Adrian Nistor Assignee: Adrian Nistor Currently we index all fields. An interesting idea is to use a custom protobuf Option (see 'Custom Options' section here https://developers.google.com/protocol-buffers/docs/proto) to indicate which message types and specifically which fields should be indexed, similar to Hibernate Search annotations. -- 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, 5 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 November 2013