January 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2454) The current SQL query that checks table existence is under optimized on big database

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2454?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-2454: ---------------------------------- Status: Resolved (was: Pull Request Sent) Assignee: Tristan Tarrant (was: Mircea Markus) Fix Version/s: 5.2.0.Beta4 (was: 6.0.0.Final) Resolution: Done > The current SQL query that checks table existence is under optimized on big database > ------------------------------------------------------------------------------------ > > Key: ISPN-2454 > URL: https://issues.jboss.org/browse/ISPN-2454 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Affects Versions: 5.1.0.FINAL > Reporter: Nicolas Filotto > Assignee: Tristan Tarrant > Labels: jdg, jdg6 > Fix For: 5.2.0.Beta4 > > > Last year I proposed an enhancement allowing to use the implicit db schema to ease life of end-user, unfortunately it seems that it affects the startup time of the product when the tables contain a lot of rows. Indeed the query can take several seconds to return a result. > The idea of this task would be to optimize this query for all supported databases in order to avoid this drawback. -- 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
0
0 / 0

[JBoss JIRA] (ISPN-2454) The current SQL query that checks table existence is under optimized on big database

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2454?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-2454: ---------------------------------- Git Pull Request: (was: https://github.com/infinispan/infinispan/pull/1439) > The current SQL query that checks table existence is under optimized on big database > ------------------------------------------------------------------------------------ > > Key: ISPN-2454 > URL: https://issues.jboss.org/browse/ISPN-2454 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Affects Versions: 5.1.0.FINAL > Reporter: Nicolas Filotto > Assignee: Mircea Markus > Labels: jdg, jdg6 > Fix For: 6.0.0.Final > > > Last year I proposed an enhancement allowing to use the implicit db schema to ease life of end-user, unfortunately it seems that it affects the startup time of the product when the tables contain a lot of rows. Indeed the query can take several seconds to return a result. > The idea of this task would be to optimize this query for all supported databases in order to avoid this drawback. -- 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
0
0 / 0

[JBoss JIRA] (ISPN-2454) The current SQL query that checks table existence is under optimized on big database

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2454?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-2454: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1439 > The current SQL query that checks table existence is under optimized on big database > ------------------------------------------------------------------------------------ > > Key: ISPN-2454 > URL: https://issues.jboss.org/browse/ISPN-2454 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Affects Versions: 5.1.0.FINAL > Reporter: Nicolas Filotto > Assignee: Mircea Markus > Labels: jdg, jdg6 > Fix For: 6.0.0.Final > > > Last year I proposed an enhancement allowing to use the implicit db schema to ease life of end-user, unfortunately it seems that it affects the startup time of the product when the tables contain a lot of rows. Indeed the query can take several seconds to return a result. > The idea of this task would be to optimize this query for all supported databases in order to avoid this drawback. -- 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
0
0 / 0

[JBoss JIRA] (ISPN-2684) Upgrade to Netty 3.6.1.Final

by Norman Maurer (JIRA)

Norman Maurer created ISPN-2684: ----------------------------------- Summary: Upgrade to Netty 3.6.1.Final Key: ISPN-2684 URL: https://issues.jboss.org/browse/ISPN-2684 Project: Infinispan Issue Type: Enhancement Reporter: Norman Maurer Assignee: Mircea Markus We should upgrade to Netty 3.6.1.Final as this allows us to fix ISPN-1954 and also fix some issues with SSL. -- 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
0
0 / 0

[JBoss JIRA] (ISPN-2683) Module packages for AS/EAP

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-2683: ------------------------------------- Summary: Module packages for AS/EAP Key: ISPN-2683 URL: https://issues.jboss.org/browse/ISPN-2683 Project: Infinispan Issue Type: Feature Request Components: Build process Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 5.2.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
0
0 / 0

[JBoss JIRA] (ISPN-2560) Distribution ZIP file polluted

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-2560?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-2560: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Integrated. Thanks! > Distribution ZIP file polluted > ------------------------------ > > Key: ISPN-2560 > URL: https://issues.jboss.org/browse/ISPN-2560 > Project: Infinispan > Issue Type: Bug > Components: Build process > Affects Versions: 5.2.0.Beta4 > Reporter: Manik Surtani > Assignee: Tristan Tarrant > Priority: Critical > Fix For: 5.2.0.CR1, 5.2.0.Final > > > There appear to be a lot of files packaged up and archived in various (incorrect and superfluous) places in the ZIP archives. > 1. Looking at 5.2.0.Beta4-all.zip, I see: > {code} > Multiverse:infinispan-5.2.0.Beta4-all manik $ jar tf infinispan-core.jar | grep "\.sh" > functions.sh > importConfig.sh > Multiverse:infinispan-5.2.0.Beta4-all manik $ > {code} > Why are these shell scripts in the JAR file? > 2. Also, I see similar things in other JAR files: > {code} > Multiverse:infinispan-5.2.0.Beta4-all manik $ jar tf modules/demos/ec2/infinispan-ec2-demo.jar | grep "\.sh" > runEC2Demo-all.sh > runEC2Demo-influenza.sh > runEC2Demo-nucleotide.sh > runEC2Demo-protein.sh > runEC2Demo-query.sh > runEC2Demo-reader.sh > Multiverse:infinispan-5.2.0.Beta4-all manik $ > {code} > {code} > Multiverse:infinispan-5.2.0.Beta4-all manik $ jar tf modules/cli-client/infinispan-cli-client.jar | grep "\.sh" > ispn-cli.sh > Multiverse:infinispan-5.2.0.Beta4-all manik $ > {code} > 3. I see these in {{/etc/}} which, if I now put {{/etc/}} in my classpath, causes things to break in spectacular ways due to the service loaded picking up incorrect metadata. > {code} > Multiverse:infinispan-5.2.0.Beta4-all manik $ ls etc/META-INF/services/ > org.infinispan.cli.commands.Command > org.infinispan.cli.connection.Connector > org.infinispan.commands.module.ModuleCommandExtensions > org.infinispan.configuration.parsing.ConfigurationParser > org.infinispan.distexec.mapreduce.spi.MapReduceTaskLifecycle > org.infinispan.distexec.spi.DistributedTaskLifecycle > org.infinispan.factories.components.ModuleMetadataFileFinder > org.infinispan.lifecycle.ModuleLifecycle > Multiverse:infinispan-5.2.0.Beta4-all manik $ > {code} > 4. Why do we package {{etc/infinispan-query-component-metadata.dat}}? That should be a part of infinispan-query.jar, and not in etc. > 5. What is in {{/etc/help}}? Looks like resource files for the CLI, which should really be in one of the CLI jars. > Marking this as critical, since this is messy and confusing for users, and can cause breakage when running some demos and makes things very confusing to debug. -- 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
0
0 / 0

[JBoss JIRA] (ISPN-2677) CLI remoting silent auth using JBoss SASL

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2677?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-2677: ---------------------------------- Fix Version/s: (was: 5.2.0.CR1) > CLI remoting silent auth using JBoss SASL > ----------------------------------------- > > Key: ISPN-2677 > URL: https://issues.jboss.org/browse/ISPN-2677 > Project: Infinispan > Issue Type: Enhancement > Components: CLI, Server > Affects Versions: 5.2.0.Beta6 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > -- 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
0
0 / 0

[JBoss JIRA] (ISPN-2677) CLI remoting silent auth using JBoss SASL

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2677?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-2677: ---------------------------------- Affects Version/s: (was: 5.2.0.Beta6) > CLI remoting silent auth using JBoss SASL > ----------------------------------------- > > Key: ISPN-2677 > URL: https://issues.jboss.org/browse/ISPN-2677 > Project: Infinispan > Issue Type: Enhancement > Components: CLI, Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > -- 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
0
0 / 0

[JBoss JIRA] (ISPN-2677) CLI remoting silent auth using JBoss SASL

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2677?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-2677: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/jdg/pull/58 > CLI remoting silent auth using JBoss SASL > ----------------------------------------- > > Key: ISPN-2677 > URL: https://issues.jboss.org/browse/ISPN-2677 > Project: Infinispan > Issue Type: Enhancement > Components: CLI, Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > -- 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
0
0 / 0

[JBoss JIRA] (ISPN-2677) CLI remoting silent auth using JBoss SASL

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2677?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-2677: ---------------------------------- Component/s: Server > CLI remoting silent auth using JBoss SASL > ----------------------------------------- > > Key: ISPN-2677 > URL: https://issues.jboss.org/browse/ISPN-2677 > Project: Infinispan > Issue Type: Enhancement > Components: CLI, Server > Affects Versions: 5.2.0.Beta6 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 5.2.0.CR1 > > -- 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
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2013