August 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-12190) Re-add hibernate search for wildfly modules

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-12190?page=com.atlassian.jira.plugi... ] Ryan Emerson resolved ISPN-12190. --------------------------------- Fix Version/s: 12.0.0.Dev02 Resolution: Done > Re-add hibernate search for wildfly modules > ------------------------------------------- > > Key: ISPN-12190 > URL: https://issues.redhat.com/browse/ISPN-12190 > Project: Infinispan > Issue Type: Task > Components: WildFly modules > Affects Versions: 12.0.0.Dev01 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 12.0.0.Dev02 > > > They were commented out to speed-up Hibernate Search 6 integration -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12170) Query - Stop encoding the segment ID in document IDs

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-12170?page=com.atlassian.jira.plugi... ] Work on ISPN-12170 started by Gustavo Fernandes. ------------------------------------------------ > Query - Stop encoding the segment ID in document IDs > ---------------------------------------------------- > > Key: ISPN-12170 > URL: https://issues.redhat.com/browse/ISPN-12170 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying, Remote Querying > Affects Versions: 12.0.0.Dev01 > Reporter: Yoann Rodière > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 12.0.0.Dev02 > > > We're currently relying on a hack to determine routing keys for indexed documents in Infinispan Query. That is, we concatenate the ID with the segment ID, and use a routing key bridge to extract the segment ID then use it as a routing key. > > A nasty side-effect is that we include the segment ID in the ID of indexed documents in the index. > > With Hibernate Search 6.0.0.Beta9, this won't be necessary anymore: we'll be able to pass the segment ID (routing key) to Hibernate Search directly. This means we'll be able to remove the hack and to use cleaner document IDs. > > This removal means documents will have a different ID, and thus any existing index will have to be rebuilt. Thus this should be done ASAP. > > See the implementation of RoutingKeyBridge in Infinispan, and see [https://hibernate.atlassian.net/browse/HSEARCH-3891] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12170) Query - Stop encoding the segment ID in document IDs

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-12170?page=com.atlassian.jira.plugi... ] Gustavo Fernandes updated ISPN-12170: ------------------------------------- Status: Open (was: New) > Query - Stop encoding the segment ID in document IDs > ---------------------------------------------------- > > Key: ISPN-12170 > URL: https://issues.redhat.com/browse/ISPN-12170 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying, Remote Querying > Affects Versions: 12.0.0.Dev01 > Reporter: Yoann Rodière > Priority: Major > Fix For: 12.0.0.Dev02 > > > We're currently relying on a hack to determine routing keys for indexed documents in Infinispan Query. That is, we concatenate the ID with the segment ID, and use a routing key bridge to extract the segment ID then use it as a routing key. > > A nasty side-effect is that we include the segment ID in the ID of indexed documents in the index. > > With Hibernate Search 6.0.0.Beta9, this won't be necessary anymore: we'll be able to pass the segment ID (routing key) to Hibernate Search directly. This means we'll be able to remove the hack and to use cleaner document IDs. > > This removal means documents will have a different ID, and thus any existing index will have to be rebuilt. Thus this should be done ASAP. > > See the implementation of RoutingKeyBridge in Infinispan, and see [https://hibernate.atlassian.net/browse/HSEARCH-3891] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11421) Drop OSGi

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-11421?page=com.atlassian.jira.plugi... ] Ryan Emerson resolved ISPN-11421. --------------------------------- Resolution: Done > Drop OSGi > --------- > > Key: ISPN-11421 > URL: https://issues.redhat.com/browse/ISPN-11421 > Project: Infinispan > Issue Type: Task > Reporter: Tristan Tarrant > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 12.0.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11024) Unable to use binary memory eviction with protobuf

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-11024?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-11024: ------------------------------- Fix Version/s: 11.0.4.Final (was: 11.0.3.Final) > Unable to use binary memory eviction with protobuf > -------------------------------------------------- > > Key: ISPN-11024 > URL: https://issues.redhat.com/browse/ISPN-11024 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 10.0.1.Final > Reporter: Jens Reimann > Assignee: Will Burns > Priority: Critical > Fix For: 11.0.4.Final > > > Enabling binary eviction, e.g.: > {code:xml} > <memory> > <binary strategy="REMOVE" size="134217728" eviction="MEMORY"/> > </memory> > {code} > When storing protobuf based types, throws the following exception: > {code} > 15:36:29,859 ERROR [org.infinispan.interceptors.impl.InvocationContextInterceptor] (async-thread--p2-t18) ISPN000136: Error executing command PrepareCommand on Cache 'devices', writing keys []: java.lang.IllegalArgumentException: Size of Class class org.infinispan.query.remote.impl.indexing.ProtobufValueWrapper cannot be determined using given entry size calculator :class org.infinispan.container.entries.PrimitiveEntrySizeCalculator > {code} > As protobuf produces a binary representation of the data, it is possible to calculate a size for that object. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11189) Modules query and query-core have overlapping logging id ranges

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-11189?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-11189: ------------------------------- Fix Version/s: 11.0.4.Final (was: 11.0.3.Final) > Modules query and query-core have overlapping logging id ranges > --------------------------------------------------------------- > > Key: ISPN-11189 > URL: https://issues.redhat.com/browse/ISPN-11189 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 10.1.0.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Labels: SearchNG > Fix For: 11.0.4.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11279) Replace UUID.randomUUID() with Util.threadLocalRandomUUID()

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-11279?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-11279: ------------------------------- Fix Version/s: 11.0.4.Final (was: 11.0.3.Final) > Replace UUID.randomUUID() with Util.threadLocalRandomUUID() > ----------------------------------------------------------- > > Key: ISPN-11279 > URL: https://issues.redhat.com/browse/ISPN-11279 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 10.1.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 11.0.4.Final > > > {{UUID.randomUUID()}} is pretty expensive, because it uses {{SecureRandom}}. > We don't need cryptographically strong UUIDs, so we can generate all our UUIDs with {{Util.threadLocalRandomUUID()}} instead. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12005) Store purge should ignore errors

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-12005?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-12005: ------------------------------- Fix Version/s: 11.0.4.Final (was: 11.0.3.Final) > Store purge should ignore errors > -------------------------------- > > Key: ISPN-12005 > URL: https://issues.redhat.com/browse/ISPN-12005 > Project: Infinispan > Issue Type: Bug > Components: Core, Loaders and Stores > Affects Versions: 10.1.5.Final, 11.0.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 12.0.0.Final, 11.0.4.Final > > > Purging of expired entries from stores is a pretty involved process, especially with {{RocksDBStore}}. When there's a problem unmarshalling the expired bucket or deleting an expired key, the purge task bails out immediately, without processing the remaining keys. To make matters worse, the exception it not logged anywhere. The only sign that something is wrong is a growing store (in the case of {{RocksDBStore}}, a growing number of SST files). -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12022) Provide a REST command to reset microprofile metrics

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-12022?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-12022: ------------------------------- Fix Version/s: 11.0.4.Final (was: 11.0.3.Final) > Provide a REST command to reset microprofile metrics > ---------------------------------------------------- > > Key: ISPN-12022 > URL: https://issues.redhat.com/browse/ISPN-12022 > Project: Infinispan > Issue Type: Enhancement > Components: JMX, reporting and management > Affects Versions: 10.1.0.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 11.0.4.Final > > > The microprofile metrics API does not provide a standard way to reset metrics. > We'll need to add one REST handler for this, if possible. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11992) Convert RemoteStore to use new SPI

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-11992?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-11992: ------------------------------- Fix Version/s: 11.0.4.Final (was: 11.0.3.Final) > Convert RemoteStore to use new SPI > ---------------------------------- > > Key: ISPN-11992 > URL: https://issues.redhat.com/browse/ISPN-11992 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 12.0.0.Final, 11.0.4.Final > > > The RemoteStore already uses a non blocking client. We should convert it to the new SPI to utilize this. > We also need to add in a check for the old server to see how many segments it has. If the number is different than the current server we need to disable the segmentation characteristic and instead do the costlier iteration. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues August 2020