April 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10249) Upgrade to Hibernate Search 6 and Lucene 8

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-10249?page=com.atlassian.jira.plugi... ] Gustavo Fernandes updated ISPN-10249: ------------------------------------- Fix Version/s: 11.0.0.Final > Upgrade to Hibernate Search 6 and Lucene 8 > ------------------------------------------ > > Key: ISPN-10249 > URL: https://issues.redhat.com/browse/ISPN-10249 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 11.0.0.Dev04 > Reporter: Nistor Adrian > Priority: Major > Labels: SearchNG > Fix For: 11.0.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10249) Upgrade to Hibernate Search 6 and Lucene 8

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-10249?page=com.atlassian.jira.plugi... ] Gustavo Fernandes updated ISPN-10249: ------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8226 > Upgrade to Hibernate Search 6 and Lucene 8 > ------------------------------------------ > > Key: ISPN-10249 > URL: https://issues.redhat.com/browse/ISPN-10249 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 11.0.0.Dev04 > Reporter: Nistor Adrian > Priority: Major > Labels: SearchNG > Fix For: 11.0.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11714) Auto-enable XML config elements when the element is present but its 'enabled' attribute is omitted

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11714?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-11714: --------------------------------- Affects Version/s: 11.0.0.Alpha1 > Auto-enable XML config elements when the element is present but its 'enabled' attribute is omitted > -------------------------------------------------------------------------------------------------- > > Key: ISPN-11714 > URL: https://issues.redhat.com/browse/ISPN-11714 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 11.0.0.Alpha1 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > > This is a generic issue that applies to multiple config areas: stores, xsite, security, jmx, indexing, partition handling.... We do have an 'enabled' attribute in other areas also, like state transfer where it is enabled by default, but we are not concerned with those. This issue only touches the cases where the XSD default value is false requiring the user to explicitly put enabled="true" in the config element. Rather than doing that we should simplify things , for usability, and if the element is present and the attribute is omitted we should auto-enable it. > This touches strictly xml config. Programmatic config still requires and explicit enable call. > The xml parser will only have this behaviour for schemas starting with 11. > TBD: 1. what do we do for JSON based config or other possible text formats? > 2. What do we do about programmatic auto-enable, like in AbstractGlobalConfigurationBuilder.globalState() ? > NOTE: The indexing case is handled separately as it stands better chance to be resolved by next major release, here: https://issues.redhat.com/browse/ISPN-11712 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11714) Auto-enable XML config elements when the element is present but its 'enabled' attribute is omitted

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11714?page=com.atlassian.jira.plugi... ] Nistor Adrian reassigned ISPN-11714: ------------------------------------ Assignee: Nistor Adrian > Auto-enable XML config elements when the element is present but its 'enabled' attribute is omitted > -------------------------------------------------------------------------------------------------- > > Key: ISPN-11714 > URL: https://issues.redhat.com/browse/ISPN-11714 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 11.0.0.Alpha1 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > > This is a generic issue that applies to multiple config areas: stores, xsite, security, jmx, indexing, partition handling.... We do have an 'enabled' attribute in other areas also, like state transfer where it is enabled by default, but we are not concerned with those. This issue only touches the cases where the XSD default value is false requiring the user to explicitly put enabled="true" in the config element. Rather than doing that we should simplify things , for usability, and if the element is present and the attribute is omitted we should auto-enable it. > This touches strictly xml config. Programmatic config still requires and explicit enable call. > The xml parser will only have this behaviour for schemas starting with 11. > TBD: 1. what do we do for JSON based config or other possible text formats? > 2. What do we do about programmatic auto-enable, like in AbstractGlobalConfigurationBuilder.globalState() ? > NOTE: The indexing case is handled separately as it stands better chance to be resolved by next major release, here: https://issues.redhat.com/browse/ISPN-11712 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11714) Auto-enable XML config elements when the element is present but its 'enabled' attribute is omitted

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11714?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-11714: --------------------------------- Status: Open (was: New) > Auto-enable XML config elements when the element is present but its 'enabled' attribute is omitted > -------------------------------------------------------------------------------------------------- > > Key: ISPN-11714 > URL: https://issues.redhat.com/browse/ISPN-11714 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 11.0.0.Alpha1 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > > This is a generic issue that applies to multiple config areas: stores, xsite, security, jmx, indexing, partition handling.... We do have an 'enabled' attribute in other areas also, like state transfer where it is enabled by default, but we are not concerned with those. This issue only touches the cases where the XSD default value is false requiring the user to explicitly put enabled="true" in the config element. Rather than doing that we should simplify things , for usability, and if the element is present and the attribute is omitted we should auto-enable it. > This touches strictly xml config. Programmatic config still requires and explicit enable call. > The xml parser will only have this behaviour for schemas starting with 11. > TBD: 1. what do we do for JSON based config or other possible text formats? > 2. What do we do about programmatic auto-enable, like in AbstractGlobalConfigurationBuilder.globalState() ? > NOTE: The indexing case is handled separately as it stands better chance to be resolved by next major release, here: https://issues.redhat.com/browse/ISPN-11712 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11714) Auto-enable XML config elements when the element is present but its 'enabled' attribute is omitted

by Nistor Adrian (Jira)

Nistor Adrian created ISPN-11714: ------------------------------------ Summary: Auto-enable XML config elements when the element is present but its 'enabled' attribute is omitted Key: ISPN-11714 URL: https://issues.redhat.com/browse/ISPN-11714 Project: Infinispan Issue Type: Enhancement Reporter: Nistor Adrian This is a generic issue that applies to multiple config areas: stores, xsite, security, jmx, indexing, partition handling.... We do have an 'enabled' attribute in other areas also, like state transfer where it is enabled by default, but we are not concerned with those. This issue only touches the cases where the XSD default value is false requiring the user to explicitly put enabled="true" in the config element. Rather than doing that we should simplify things , for usability, and if the element is present and the attribute is omitted we should auto-enable it. This touches strictly xml config. Programmatic config still requires and explicit enable call. The xml parser will only have this behaviour for schemas starting with 11. TBD: 1. what do we do for JSON based config or other possible text formats? 2. What do we do about programmatic auto-enable, like in AbstractGlobalConfigurationBuilder.globalState() ? NOTE: The indexing case is handled separately as it stands better chance to be resolved by next major release, here: https://issues.redhat.com/browse/ISPN-11712 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11713) Upgrade to Hibernate Search 6

by Gustavo Fernandes (Jira)

Gustavo Fernandes created ISPN-11713: ---------------------------------------- Summary: Upgrade to Hibernate Search 6 Key: ISPN-11713 URL: https://issues.redhat.com/browse/ISPN-11713 Project: Infinispan Issue Type: Enhancement Components: Embedded Querying, Remote Querying Affects Versions: 11.0.0.Dev04 Reporter: Gustavo Fernandes -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11712) Indexing configured via XML should be automatically enabled if the 'enabled' attribute is missing

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11712?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-11712: --------------------------------- Description: The 'enabled' attribute has a default of 'false' in xsd, which is fine for all purposes when indexing is not configured for a cache. Indexing should generally not be enabled by default as it is costly, unless the <indexing> element is present and the 'enabled' attributive was omitted (and if the a tribute was not omitted, then we do what the attribute says). Also, this auto-enabling based on <indexing> element presence should only be performed since schema ver. 11. Programmatic config is not going to be affected by this; `enable()` will have to be called explicitly. was: The 'enabled' attribute has a default of 'false' in xsd, which is fine for all purposes when indexing is not configured for a cache. Indexing should generally not be enabled by default as it is costly, unless the <indexing> element is present and the 'enabled' attributive was omitted (and if the a tribute was not omitted, then we do what the attribute says). Also, this auto-enabling based on <indexing> element presence should only be performed since schema ver. 11. Programmatic config is not going to be affected by this; ```enable()``` will have to be called explicitly. > Indexing configured via XML should be automatically enabled if the 'enabled' attribute is missing > ------------------------------------------------------------------------------------------------- > > Key: ISPN-11712 > URL: https://issues.redhat.com/browse/ISPN-11712 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying, Remote Querying > Affects Versions: 11.0.0.Dev03 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 11.0.0.Dev05 > > > The 'enabled' attribute has a default of 'false' in xsd, which is fine for all purposes when indexing is not configured for a cache. Indexing should generally not be enabled by default as it is costly, unless the <indexing> element is present and the 'enabled' attributive was omitted (and if the a tribute was not omitted, then we do what the attribute says). > Also, this auto-enabling based on <indexing> element presence should only be performed since schema ver. 11. > Programmatic config is not going to be affected by this; `enable()` will have to be called explicitly. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11712) Indexing configured via XML should be automatically enabled if the 'enabled' attribute is missing

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11712?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-11712: --------------------------------- Description: The 'enabled' attribute has a default of 'false' in xsd, which is fine for all purposes when indexing is not configured for a cache. Indexing should generally not be enabled by default as it is costly, unless the <indexing> element is present and the 'enabled' attributive was omitted (and if the a tribute was not omitted, then we do what the attribute says). Also, this auto-enabling based on <indexing> element presence should only be performed since schema ver. 11. Programmatic config is not going to be affected by this; ```enable()``` will have to be called explicitly. was: The 'enabled' attribute has a default of 'false' in xsd, which is fine for all purposes when indexing is not configured for a cache. Indexing should generally not be enabled by default as it is costly, unless the <indexing> element is present and the 'enabled' attributive was omitted (and if the a tribute was not omitted, then we do what the attribute says). Also, this auto-enabling based on <indexing> element presence should only be performed since schema ver. 11. > Indexing configured via XML should be automatically enabled if the 'enabled' attribute is missing > ------------------------------------------------------------------------------------------------- > > Key: ISPN-11712 > URL: https://issues.redhat.com/browse/ISPN-11712 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying, Remote Querying > Affects Versions: 11.0.0.Dev03 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 11.0.0.Dev05 > > > The 'enabled' attribute has a default of 'false' in xsd, which is fine for all purposes when indexing is not configured for a cache. Indexing should generally not be enabled by default as it is costly, unless the <indexing> element is present and the 'enabled' attributive was omitted (and if the a tribute was not omitted, then we do what the attribute says). > Also, this auto-enabling based on <indexing> element presence should only be performed since schema ver. 11. > Programmatic config is not going to be affected by this; ```enable()``` will have to be called explicitly. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11712) Indexing configured via XML should be automatically enabled if the 'enabled' attribute is missing

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11712?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-11712: --------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8218 > Indexing configured via XML should be automatically enabled if the 'enabled' attribute is missing > ------------------------------------------------------------------------------------------------- > > Key: ISPN-11712 > URL: https://issues.redhat.com/browse/ISPN-11712 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying, Remote Querying > Affects Versions: 11.0.0.Dev03 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 11.0.0.Dev05 > > > The 'enabled' attribute has a default of 'false' in xsd, which is fine for all purposes when indexing is not configured for a cache. Indexing should generally not be enabled by default as it is costly, unless the <indexing> element is present and the 'enabled' attributive was omitted (and if the a tribute was not omitted, then we do what the attribute says). > Also, this auto-enabling based on <indexing> element presence should only be performed since schema ver. 11. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 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 April 2020