[Red Hat JIRA] (ISPN-12634) Support Transcoding for the Remote Store
by Gustavo Fernandes (Jira)
Gustavo Fernandes created ISPN-12634:
----------------------------------------
Summary: Support Transcoding for the Remote Store
Key: ISPN-12634
URL: https://issues.redhat.com/browse/ISPN-12634
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 12.0.0.CR1
Reporter: Gustavo Fernandes
Assignee: Gustavo Fernandes
The involves removing internal usages of the deprecated configs 'hotRodWrapping' and 'rawValues', and also deprecate and remove internal usages of the 'marshaller' configuration.
The remote store should make usage of Transcoders to convert to/from the data stored in the remote cache and the data stored in the local cache.
This will enable Rolling Upgrades between disparate caches storing different data formats, provided there is a path for conversion between them
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 3 months
[Red Hat JIRA] (ISPN-12633) Multimap in the console
by Katia Aresti (Jira)
Katia Aresti created ISPN-12633:
-----------------------------------
Summary: Multimap in the console
Key: ISPN-12633
URL: https://issues.redhat.com/browse/ISPN-12633
Project: Infinispan
Issue Type: Feature Request
Components: Console
Affects Versions: 12.0.0.CR1
Reporter: Katia Aresti
Assignee: Katia Aresti
Display multimaps in the console
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 3 months
[Red Hat JIRA] (ISPN-12632) Multimap REST API
by Katia Aresti (Jira)
Katia Aresti created ISPN-12632:
-----------------------------------
Summary: Multimap REST API
Key: ISPN-12632
URL: https://issues.redhat.com/browse/ISPN-12632
Project: Infinispan
Issue Type: Feature Request
Components: REST
Affects Versions: 12.0.0.CR1
Reporter: Katia Aresti
Assignee: Katia Aresti
GetEntries from a multimap cache is not working in REST
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 3 months
[Red Hat JIRA] (ISPN-12631) Adding Protobuf schema removes global errors
by Dan Berindei (Jira)
Dan Berindei created ISPN-12631:
-----------------------------------
Summary: Adding Protobuf schema removes global errors
Key: ISPN-12631
URL: https://issues.redhat.com/browse/ISPN-12631
Project: Infinispan
Issue Type: Bug
Components: Indexing
Affects Versions: 12.0.0.CR1
Reporter: Dan Berindei
Any write to the protobuf schema cache updates the global errors key ({{.errors}}).
But when a schema is added/updated, the new global errors key will contain only the errors in that schema, and any existing errors for other schemas will be removed.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 3 months
[Red Hat JIRA] (ISPN-12616) Rolling Upgrade fails for caches storing POJOs
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-12616?page=com.atlassian.jira.plugi... ]
Gustavo Fernandes updated ISPN-12616:
-------------------------------------
Fix Version/s: (was: 12.0.0.Final)
> Rolling Upgrade fails for caches storing POJOs
> ----------------------------------------------
>
> Key: ISPN-12616
> URL: https://issues.redhat.com/browse/ISPN-12616
> Project: Infinispan
> Issue Type: Bug
> Components: Hot Rod, Loaders and Stores
> Affects Versions: 12.0.0.CR1, 11.0.8.Final
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
> Fix For: 11.0.9.Final
>
>
> The Remote Store does not support transcoding yet, and the data conversions are done implicitly by combining the 'hotRodWrapping', 'marshaller' and 'rawValues' configurations.
> The rolling upgrade process forces the remote store to use 'hotRodWrapping', that prevents consuming a cache that stores "application/x-java-objects", since it assumes the data is already in "application/x-jboss-marshalling" format, causing lots of internal issues.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 3 months
[Red Hat JIRA] (ISPN-12476) Enable conflict resolution for IRAC state transfer
by Pedro Ruivo (Jira)
[ https://issues.redhat.com/browse/ISPN-12476?page=com.atlassian.jira.plugi... ]
Pedro Ruivo updated ISPN-12476:
-------------------------------
Git Pull Request: https://github.com/infinispan/infinispan/pull/8985
Status: Pull Request Sent (was: Coding In Progress)
> Enable conflict resolution for IRAC state transfer
> --------------------------------------------------
>
> Key: ISPN-12476
> URL: https://issues.redhat.com/browse/ISPN-12476
> Project: Infinispan
> Issue Type: Enhancement
> Components: Cross-Site Replication
> Affects Versions: 12.0.0.Dev05
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Priority: Major
> Fix For: 12.0.0.Final
>
>
> Current cross-site replication for asynchronous backups overwrites everything in the receiver site. This works fine for active-passive scenarios but IRAC fits active-active scenario better.
> We can improve the state transfer by "touching" all keys. IRAC will send them in the background and we can take advantage of conflict resolution.
> For performance reasons, we should touch the keys by segments to avoid queueing too many keys in memory.
> Also, opens the possibility of automatic state transfer for IRAC.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 3 months
[Red Hat JIRA] (ISPN-12535) Fix WARN messages org.hibernate.search in the server
by Katia Aresti (Jira)
[ https://issues.redhat.com/browse/ISPN-12535?page=com.atlassian.jira.plugi... ]
Katia Aresti updated ISPN-12535:
--------------------------------
Resolution: Done
Status: Resolved (was: Pull Request Sent)
> Fix WARN messages org.hibernate.search in the server
> ----------------------------------------------------
>
> Key: ISPN-12535
> URL: https://issues.redhat.com/browse/ISPN-12535
> Project: Infinispan
> Issue Type: Enhancement
> Components: Remote Querying
> Affects Versions: 12.0.0.Dev07
> Reporter: Diego Lovison
> Assignee: Gustavo Fernandes
> Priority: Major
> Attachments: query.diff
>
>
> When creating the caches using the attached test, we can see the following WARN messages in the server
>
> {noformat}
> 11:52:13,778 WARN (blocking-thread--p3-t1) [org.hibernate.search.engine.common.impl.IndexManagerBuildingStateHolder] HSEARCH000574: Using configuration property 'hibernate.search.default_backend' to set the name of the default backend to 'infinispan_backend'. This configuration property is deprecated and shouldn't be used anymore. Instead, do not assign a name your default backend and configure it using the 'hibernate.search.backend' prefix, e.g. hibernate.search.backend.type = elasticsearch.
> 11:52:13,857 WARN (blocking-thread--p3-t1) [org.hibernate.search.backend.lucene.impl.LuceneBackendFactory] HSEARCH000075: Configuration setting 'lucene_version' was not specified: using LATEST (currently '8.6.2'). Context: backend 'infinispan_backend'
> 11:52:14,428 WARN (blocking-thread--p3-t1) [org.hibernate.search.engine.cfg.impl.EngineConfigurationUtils] HSEARCH000585: Using configuration property 'index_defaults.indexing.queue_count'. The prefix 'index_defaults' is deprecated and its support will ultimately be removed. Instead, you should just set defaults for index properties at the backend level. For example, set 'hibernate.search.backend.indexing.queue_size' instead of 'hibernate.search.backend.index_defaults.indexing.queue_size'.
> {noformat}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 3 months