July 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-12126) Performance drop when using auth in REST

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-12126?page=com.atlassian.jira.plugi... ] Gustavo Fernandes updated ISPN-12126: ------------------------------------- Status: Open (was: New) > Performance drop when using auth in REST > ---------------------------------------- > > Key: ISPN-12126 > URL: https://issues.redhat.com/browse/ISPN-12126 > Project: Infinispan > Issue Type: Bug > Components: REST, Security > Affects Versions: 11.0.1.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12126) Performance drop when using auth in REST

by Gustavo Fernandes (Jira)

Gustavo Fernandes created ISPN-12126: ---------------------------------------- Summary: Performance drop when using auth in REST Key: ISPN-12126 URL: https://issues.redhat.com/browse/ISPN-12126 Project: Infinispan Issue Type: Bug Components: REST, Security Affects Versions: 11.0.1.Final Reporter: Gustavo Fernandes Assignee: Gustavo Fernandes -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12125) IntelliJ copies infinispan-version.properties without filtering

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-12125?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-12125: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8553 > IntelliJ copies infinispan-version.properties without filtering > --------------------------------------------------------------- > > Key: ISPN-12125 > URL: https://issues.redhat.com/browse/ISPN-12125 > Project: Infinispan > Issue Type: Bug > Components: Build > Affects Versions: 11.0.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 12.0.0.Final > > > Sometimes IntelliJ fails to replace the properties in {{infinispan-version.properties}} when the {{Build}} task runs before a test. It always replaces the properties file, though, so the test will fail to start with an assertion in {{Version.java:66}}. > It seems to be connected to {{commons/all/pom.xml}} having a duplicate {{resource/filter=true}} element, but I was not able to reproduce the problem or to fix it consistently. > [https://youtrack.jetbrains.com/issue/IDEA-245995] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12125) IntelliJ copies infinispan-version.properties without filtering

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-12125?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-12125: -------------------------------- Status: Open (was: New) > IntelliJ copies infinispan-version.properties without filtering > --------------------------------------------------------------- > > Key: ISPN-12125 > URL: https://issues.redhat.com/browse/ISPN-12125 > Project: Infinispan > Issue Type: Bug > Components: Build > Affects Versions: 11.0.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 12.0.0.Final > > > Sometimes IntelliJ fails to replace the properties in {{infinispan-version.properties}} when the {{Build}} task runs before a test. It always replaces the properties file, though, so the test will fail to start with an assertion in {{Version.java:66}}. > It seems to be connected to {{commons/all/pom.xml}} having a duplicate {{resource/filter=true}} element, but I was not able to reproduce the problem or to fix it consistently. > [https://youtrack.jetbrains.com/issue/IDEA-245995] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12125) IntelliJ copies infinispan-version.properties without filtering

by Dan Berindei (Jira)

Dan Berindei created ISPN-12125: ----------------------------------- Summary: IntelliJ copies infinispan-version.properties without filtering Key: ISPN-12125 URL: https://issues.redhat.com/browse/ISPN-12125 Project: Infinispan Issue Type: Bug Components: Build Affects Versions: 11.0.1.Final Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 12.0.0.Final Sometimes IntelliJ fails to replace the properties in {{infinispan-version.properties}} when the {{Build}} task runs before a test. It always replaces the properties file, though, so the test will fail to start with an assertion in {{Version.java:66}}. It seems to be connected to {{commons/all/pom.xml}} having a duplicate {{resource/filter=true}} element, but I was not able to reproduce the problem or to fix it consistently. [https://youtrack.jetbrains.com/issue/IDEA-245995] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12124) OracleTableManager is overly conservative with object name max length

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/ISPN-12124?page=com.atlassian.jira.plugi... ] Paul Ferraro updated ISPN-12124: -------------------------------- Description: The OracleTableManager limits the size of generated object names to 30 characters. While 30 characters was the max object name length in 12.1 and earlier, since 12.2, this limit was increased to 128 characters. 30 characters is prohibitively restrictive when it come to objects like the index name, the names for which are auto-generated based on the cache name, table name, and, in the case of the segment column, a long hard coded prefix (e.g. "segment_index") uses up nearly half of the available characters. Rather than fixed lengths per database type, Infinispan should leverage the DatabaseMetaData to determine the max size for a given database object, e.g. getMaxTableNameLength(), getMaxColumnNameLength(), etc. was: The OracleTableManager limits the size of generated object names to 30 characters. While 30 characters was the max object name length in 12.1 and earlier, since 12.2, this limit was increased to 128 characters. 30 characters is prohibitively restrictive when it come to objects like the index name, the names for which are auto-generated based on the cache name, table name, and, in the case of the segment column, a long hard coded prefix (e.g. "segment_index") uses up nearly half of the available characters. Ideally, Infinispan should determine the max object name size at runtime based on the values returned by the DatabaseMetaData, e.g. getMaxTableNameLength(), getMaxColumnNameLength(), etc. > OracleTableManager is overly conservative with object name max length > --------------------------------------------------------------------- > > Key: ISPN-12124 > URL: https://issues.redhat.com/browse/ISPN-12124 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Affects Versions: 11.0.1.Final > Reporter: Paul Ferraro > Priority: Major > > The OracleTableManager limits the size of generated object names to 30 characters. While 30 characters was the max object name length in 12.1 and earlier, since 12.2, this limit was increased to 128 characters. > 30 characters is prohibitively restrictive when it come to objects like the index name, the names for which are auto-generated based on the cache name, table name, and, in the case of the segment column, a long hard coded prefix (e.g. "segment_index") uses up nearly half of the available characters. > Rather than fixed lengths per database type, Infinispan should leverage the DatabaseMetaData to determine the max size for a given database object, e.g. getMaxTableNameLength(), getMaxColumnNameLength(), etc. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12124) OracleTableManager is overly conservative with object name max length

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/ISPN-12124?page=com.atlassian.jira.plugi... ] Paul Ferraro updated ISPN-12124: -------------------------------- Description: The OracleTableManager limits the size of generated object names to 30 characters. While 30 characters was the max object name length in 12.1 and earlier, since 12.2, this limit was increased to 128 characters. 30 characters is prohibitively restrictive when it come to objects like the index name, the names for which are auto-generated based on the cache name, table name, and, in the case of the segment column, a long hard coded prefix (e.g. "segment_index") uses up nearly half of the available characters. Ideally, Infinispan should determine the max object name size at runtime based on the values returned by the DatabaseMetaData, e.g. getMaxTableNameLength(), getMaxColumnNameLength(), etc. was: The OracleTableManager limits the size of generated object names to 30 characters. While 30 characters was the max object name length in 12.1 and earlier, since 12.2, this limit was increased to 128 characters. 30 characters is prohibitively restrictive when it come to objects like the index name, the names for which are auto-generated based on the cache name, table name, and, in the case of the segment column, a long hard coded prefix (e.g. "segment_index"). Ideally, Infinispan should determine the max object name size at runtime based on the values returned by the DatabaseMetaData, e.g. getMaxTableNameLength(), getMaxColumnNameLength(), etc. > OracleTableManager is overly conservative with object name max length > --------------------------------------------------------------------- > > Key: ISPN-12124 > URL: https://issues.redhat.com/browse/ISPN-12124 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Affects Versions: 11.0.1.Final > Reporter: Paul Ferraro > Priority: Major > > The OracleTableManager limits the size of generated object names to 30 characters. While 30 characters was the max object name length in 12.1 and earlier, since 12.2, this limit was increased to 128 characters. > 30 characters is prohibitively restrictive when it come to objects like the index name, the names for which are auto-generated based on the cache name, table name, and, in the case of the segment column, a long hard coded prefix (e.g. "segment_index") uses up nearly half of the available characters. > Ideally, Infinispan should determine the max object name size at runtime based on the values returned by the DatabaseMetaData, e.g. getMaxTableNameLength(), getMaxColumnNameLength(), etc. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12124) OracleTableManager is overly conservative with object name max length

by Paul Ferraro (Jira)

Paul Ferraro created ISPN-12124: ----------------------------------- Summary: OracleTableManager is overly conservative with object name max length Key: ISPN-12124 URL: https://issues.redhat.com/browse/ISPN-12124 Project: Infinispan Issue Type: Enhancement Components: Loaders and Stores Affects Versions: 11.0.1.Final Reporter: Paul Ferraro The OracleTableManager limits the size of generated object names to 30 characters. While 30 characters was the max object name length in 12.1 and earlier, since 12.2, this limit was increased to 128 characters. 30 characters is prohibitively restrictive when it come to objects like the index name, the names for which are auto-generated based on the cache name, table name, and, in the case of the segment column, a long hard coded prefix (e.g. "segment_index"). Ideally, Infinispan should determine the max object name size at runtime based on the values returned by the DatabaseMetaData, e.g. getMaxTableNameLength(), getMaxColumnNameLength(), etc. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12002) Rolling Upgrades location aware data retrieving

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-12002?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-12002: ------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.4.20.Final Resolution: Done > Rolling Upgrades location aware data retrieving > ----------------------------------------------- > > Key: ISPN-12002 > URL: https://issues.redhat.com/browse/ISPN-12002 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Affects Versions: 9.4.19.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 9.4.20.Final > > > Currently the Rolling upgrades data retrieval is done using several tasks in parallel, where each task retrieves from the source cluster a subset of the data from one or more segments. > Each task should only retrieve data from segments that are confined to a single source server, to avoid further remote calls inside the source server. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12117) Add test driver dependencies to the bom

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-12117?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-12117: ------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 12.0.0.Dev01 Resolution: Done > Add test driver dependencies to the bom > --------------------------------------- > > Key: ISPN-12117 > URL: https://issues.redhat.com/browse/ISPN-12117 > Project: Infinispan > Issue Type: Enhancement > Components: Build > Affects Versions: 10.1.8.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Fix For: 12.0.0.Dev01 > > > Test drivers dependencies are missing in the bom -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 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 July 2020