September 2020 - infinispan-issues

[JBoss JIRA] (ISPN-12280) Failfast if lsof is not present in unix

by Diego Lovison (Jira)

[ https://issues.redhat.com/browse/ISPN-12280?page=com.atlassian.jira.plugi... ] Diego Lovison reassigned ISPN-12280: ------------------------------------ Assignee: Diego Lovison > Failfast if lsof is not present in unix > --------------------------------------- > > Key: ISPN-12280 > URL: https://issues.redhat.com/browse/ISPN-12280 > Project: Infinispan > Issue Type: Enhancement > Components: Test Suite > Affects Versions: 12.0.0.Dev02 > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Major > > Some tests require lsof be present in order to work properly > Example: > {noformat} > 13:24:51.246 [INFO] Infinispan JCACHE (JSR-107) TCK Runner Remote ...... SUCCESS [05:58 min] > 13:24:51.246 [INFO] Server Integration ................................. SUCCESS [ 11.991 s] > 13:24:51.246 [INFO] Integration tests - WildFly Module Integration Tests SUCCESS [ 58.984 s] > {noformat} > when not present > {noformat} > [ERROR] Errors: > [ERROR] BaseHotRodQueryIT.testRemoteQuery ? HotRodClient org.infinispan.server.hotrod.... > [ERROR] BaseHotRodQueryIT.testUninverting ? HotRodClient org.infinispan.server.hotrod.... > [ERROR] HotRodClientIT.testCacheManager ? HotRodClient org.infinispan.server.hotrod.Ca... > [ERROR] HotRodQueryIT.testRemoteQuery ? HotRodClient org.infinispan.server.hotrod.Cach... > [ERROR] HotRodQueryIT.testUninverting ? HotRodClient org.infinispan.server.hotrod.Cach... > [ERROR] InfinispanRemoteWithQueryIT.testRemoteQuery ? HotRodClient org.infinispan.serv... > [ERROR] InfinispanRemoteWithQueryIT.testUninverting ? HotRodClient org.infinispan.serv... > {noformat} > It will take times to find out that the root cause is because lsof is missing -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12280) Failfast if lsof is not present in unix

by Diego Lovison (Jira)

[ https://issues.redhat.com/browse/ISPN-12280?page=com.atlassian.jira.plugi... ] Diego Lovison updated ISPN-12280: --------------------------------- Status: Open (was: New) > Failfast if lsof is not present in unix > --------------------------------------- > > Key: ISPN-12280 > URL: https://issues.redhat.com/browse/ISPN-12280 > Project: Infinispan > Issue Type: Enhancement > Components: Test Suite > Affects Versions: 12.0.0.Dev02 > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Major > > Some tests require lsof be present in order to work properly > Example: > {noformat} > 13:24:51.246 [INFO] Infinispan JCACHE (JSR-107) TCK Runner Remote ...... SUCCESS [05:58 min] > 13:24:51.246 [INFO] Server Integration ................................. SUCCESS [ 11.991 s] > 13:24:51.246 [INFO] Integration tests - WildFly Module Integration Tests SUCCESS [ 58.984 s] > {noformat} > when not present > {noformat} > [ERROR] Errors: > [ERROR] BaseHotRodQueryIT.testRemoteQuery ? HotRodClient org.infinispan.server.hotrod.... > [ERROR] BaseHotRodQueryIT.testUninverting ? HotRodClient org.infinispan.server.hotrod.... > [ERROR] HotRodClientIT.testCacheManager ? HotRodClient org.infinispan.server.hotrod.Ca... > [ERROR] HotRodQueryIT.testRemoteQuery ? HotRodClient org.infinispan.server.hotrod.Cach... > [ERROR] HotRodQueryIT.testUninverting ? HotRodClient org.infinispan.server.hotrod.Cach... > [ERROR] InfinispanRemoteWithQueryIT.testRemoteQuery ? HotRodClient org.infinispan.serv... > [ERROR] InfinispanRemoteWithQueryIT.testUninverting ? HotRodClient org.infinispan.serv... > {noformat} > It will take times to find out that the root cause is because lsof is missing -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12280) Failfast if lsof is not present in unix

by Diego Lovison (Jira)

Diego Lovison created ISPN-12280: ------------------------------------ Summary: Failfast if lsof is not present in unix Key: ISPN-12280 URL: https://issues.redhat.com/browse/ISPN-12280 Project: Infinispan Issue Type: Enhancement Components: Test Suite Affects Versions: 12.0.0.Dev02 Reporter: Diego Lovison Some tests require lsof be present in order to work properly Example: {noformat} 13:24:51.246 [INFO] Infinispan JCACHE (JSR-107) TCK Runner Remote ...... SUCCESS [05:58 min] 13:24:51.246 [INFO] Server Integration ................................. SUCCESS [ 11.991 s] 13:24:51.246 [INFO] Integration tests - WildFly Module Integration Tests SUCCESS [ 58.984 s] {noformat} when not present {noformat} [ERROR] Errors: [ERROR] BaseHotRodQueryIT.testRemoteQuery ? HotRodClient org.infinispan.server.hotrod.... [ERROR] BaseHotRodQueryIT.testUninverting ? HotRodClient org.infinispan.server.hotrod.... [ERROR] HotRodClientIT.testCacheManager ? HotRodClient org.infinispan.server.hotrod.Ca... [ERROR] HotRodQueryIT.testRemoteQuery ? HotRodClient org.infinispan.server.hotrod.Cach... [ERROR] HotRodQueryIT.testUninverting ? HotRodClient org.infinispan.server.hotrod.Cach... [ERROR] InfinispanRemoteWithQueryIT.testRemoteQuery ? HotRodClient org.infinispan.serv... [ERROR] InfinispanRemoteWithQueryIT.testUninverting ? HotRodClient org.infinispan.serv... {noformat} It will take times to find out that the root cause is because lsof is missing -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12279) Default value of @IndexedEmbedded.depth is not correctly interpreted

by Yoann Rodière (Jira)

Yoann Rodière created ISPN-12279: ------------------------------------ Summary: Default value of @IndexedEmbedded.depth is not correctly interpreted Key: ISPN-12279 URL: https://issues.redhat.com/browse/ISPN-12279 Project: Infinispan Issue Type: Task Components: Embedded Querying Affects Versions: 12.0.0.Dev02 Reporter: Yoann Rodière Fix For: 12.0.0.Dev03 There was a problem during the migration to Search 6, and the processor for the annotation {{@IndexedEmbedded}} apparently does not correctly intepret {{@IndexedEmbedded()}} as "no depth defined". As a result, {{@IndexedEmbedded(includePaths = { "foo" })}} will not set the depth to 0 as it should, but to {{Integer.MAX_VALUE}} (the default defined on the {{(a)IndexedEmbedded.depth()}} attribute) and will end up incorrectly including the whole embedded document. The code to change is this (in {{org.hibernate.search.annotations.IndexedEmbedded}}): {code} Integer cleanedUpMaxDepth = annotation.depth(); if ( cleanedUpMaxDepth.equals( -1 ) ) { cleanedUpMaxDepth = null; } {code} It should be instead: {code} Integer cleanedUpMaxDepth = annotation.depth(); if ( cleanedUpMaxDepth.equals( Integer.MAX_VALUE ) ) { cleanedUpMaxDepth = null; } {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12218) Indexed caches with non-indexed entities query inconsistency

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-12218?page=com.atlassian.jira.plugi... ] Gustavo Fernandes reassigned ISPN-12218: ---------------------------------------- Assignee: Gustavo Fernandes > Indexed caches with non-indexed entities query inconsistency > ------------------------------------------------------------ > > Key: ISPN-12218 > URL: https://issues.redhat.com/browse/ISPN-12218 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Affects Versions: 11.0.3.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Attachments: IndexedCacheNonIndexedQueryTest.java > > > When a cache is indexed, but the protobuf entitiy is not: > "FROM Entity" returns zero results > "FROM Entity WHERE <predicate>" return results > It appears in the first case the query goes to the index (that will be empty), but not in the second where it does a non-indexed query > On a side note, if I configure a cache as indexed, but do not index any type in the protobuf, it returns {{ISPN014054: Trying to execute query from xyz, but no type is indexed on cache}}. This should be improved to mention the schema needs to be changed -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12218) Indexed caches with non-indexed entities query inconsistency

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-12218?page=com.atlassian.jira.plugi... ] Gustavo Fernandes updated ISPN-12218: ------------------------------------- Description: When a cache is indexed, but the protobuf entitiy is not: "FROM Entity" returns zero results "FROM Entity WHERE <predicate>" return results It appears in the first case the query goes to the index (that will be empty), but not in the second where it does a non-indexed query On a side note, if I configure a cache as indexed, but do not index any type in the protobuf, it returns {{ISPN014054: Trying to execute query from xyz, but no type is indexed on cache}}. This should be improved to mention the schema needs to be changed was: When a cache is indexed, but the protobuf entitiy is not: "FROM Entity" returns zero results "FROM Entity WHERE <predicate>" return results It appears in the first case the query goes to the index (that will be empty), but not in the second where it does a non-indexed query > Indexed caches with non-indexed entities query inconsistency > ------------------------------------------------------------ > > Key: ISPN-12218 > URL: https://issues.redhat.com/browse/ISPN-12218 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Affects Versions: 11.0.3.Final > Reporter: Gustavo Fernandes > Priority: Major > Attachments: IndexedCacheNonIndexedQueryTest.java > > > When a cache is indexed, but the protobuf entitiy is not: > "FROM Entity" returns zero results > "FROM Entity WHERE <predicate>" return results > It appears in the first case the query goes to the index (that will be empty), but not in the second where it does a non-indexed query > On a side note, if I configure a cache as indexed, but do not index any type in the protobuf, it returns {{ISPN014054: Trying to execute query from xyz, but no type is indexed on cache}}. This should be improved to mention the schema needs to be changed -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12269) Indexed caches and Query not properly working

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-12269?page=com.atlassian.jira.plugi... ] Katia Aresti resolved ISPN-12269. --------------------------------- Resolution: Explained > Indexed caches and Query not properly working > --------------------------------------------- > > Key: ISPN-12269 > URL: https://issues.redhat.com/browse/ISPN-12269 > Project: Infinispan > Issue Type: Bug > Components: Console, REST > Affects Versions: 12.0.0.Dev02 > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > > When we create a cache that can be queried and we add a protobuf schema object, if the cache is indexed a query like 'from people.Person' won't work. > * create a protobuf schema > {code:java} > package people; > message Person { > required string name = 1; > }{code} > > * create a indexed cache > {code:java} > { > "distributed-cache": { > "mode": "SYNC", > "encoding": { > "key": { > "media-type": "application/x-protostream" > }, > "value": { > "media-type": "application/x-protostream" > } > }, > "transaction": { > "mode": "NONE" > }, > "indexing": { > "enabled": true > }, > "statistics": true > } > }{code} > > Add an entry > {code:java} > { > "_type": "people.Person", > "name": "katia" > }{code} > > Try the query: from people.Person > > The outcome from the REST API > > h2. Query error > Error executing search ISPN014054: Trying to execute query `from people.Person`, but no type is indexed on cache. > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12278) Restore support for @Field(norms = ...) and @Field(termVector = ...)

by Yoann Rodière (Jira)

Yoann Rodière created ISPN-12278: ------------------------------------ Summary: Restore support for @Field(norms = ...) and @Field(termVector = ...) Key: ISPN-12278 URL: https://issues.redhat.com/browse/ISPN-12278 Project: Infinispan Issue Type: Task Components: Embedded Querying Affects Versions: 12.0.0.Dev02 Reporter: Yoann Rodière Fix For: 12.0.0.Dev03 It looks like these attributes of the {{@Field}} annotations were removed by mistake during the migration to Search 6. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12266) shutdown cluster should have an option to not block restart if there is no or a shared persistence

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-12266?page=com.atlassian.jira.plugi... ] Dan Berindei commented on ISPN-12266: ------------------------------------- Caches with local storage could also be made available before all the members of the stable topology join, with the same rules as for keeping a cache AVAILABLE (need a majority of the nodes + at least one owner of each segment). We could also keep the shutdown command as-is and add a new command to force the cluster to become available if no data would be lost, and an optional {{--force}} argument skipping the data loss checks. > shutdown cluster should have an option to not block restart if there is no or a shared persistence > -------------------------------------------------------------------------------------------------- > > Key: ISPN-12266 > URL: https://issues.redhat.com/browse/ISPN-12266 > Project: Infinispan > Issue Type: Feature Request > Reporter: Wolf-Dieter Fink > Priority: Minor > Labels: graceful, graceful-start-stop > > The current implementation of a full cluster restart will save the CH and state for all caches. > If caches does not have a persistence or the persistence is a shared one this might not be necesarry as the cache can start correctly with one node (empty or consistent persistence). > In that case it should be allowed to start the cache and make it available. > There are two approaches > - use extra parameter for shutdown to allow it > This will leave the default behavior the same and the admin need to decide > - change the current behavior and add a parameter to flag a FULL cluster restart > The benefit of the full cluster restart is that the caches will be available for clients only if the cluster is completely restarted, so no further state-transfer is needed for optimal performance > > > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12276) Bump Testcontainers 1.14.3

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-12276?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-12276: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 12.0.0.Dev03 Resolution: Done > Bump Testcontainers 1.14.3 > -------------------------- > > Key: ISPN-12276 > URL: https://issues.redhat.com/browse/ISPN-12276 > Project: Infinispan > Issue Type: Task > Components: Test Suite > Affects Versions: 12.0.0.Dev02 > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Major > Fix For: 12.0.0.Dev03 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

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