[JBoss JIRA] (ISPN-5250) Semantics of write-skew configured cache undefined with flag SKIP_REMOTE_LOOKUP
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-5250?page=com.atlassian.jira.plugin... ]
Dan Berindei resolved ISPN-5250.
--------------------------------
Fix Version/s: 8.0.0.Final
Resolution: Done
ISPN-5643 clarified that {{SKIP_REMOTE_LOOKUP}} must not be used with any operations that need the previous value and that {{IGNORE_RETURN_VALUES}} should be used instead.
> Semantics of write-skew configured cache undefined with flag SKIP_REMOTE_LOOKUP
> -------------------------------------------------------------------------------
>
> Key: ISPN-5250
> URL: https://issues.redhat.com/browse/ISPN-5250
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 7.1.0.Final
> Reporter: Erik Salter
> Priority: Major
> Fix For: 8.0.0.Final
>
>
> The semantics of how a write-skew cache should behave with the SKIP_REMOTE_LOOKUP flag are currently undefined. For instance, if a RemoveCommand (cache.remove(key)) is invoked on a write-skew-enabled cache with the SKIP_REMOTE_LOOKUP flag, the operation will fail with a WriteSkewException. In this setting, the expectation is that the flag will bypass any write-skew check and simply remove the key without the network cost of returning the object.
> While this flag may not make sense with conditional commands, with others it could be interpreted as "I don't care about the previous value". So maybe we should skip the write-skew check and simply return the current version -- perhaps log something if the flag is used with a conditional command?
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (ISPN-11091) Add feature to read server logs from ContainerInfinispanServerDriver
by Gustavo Lira e Silva (Jira)
Gustavo Lira e Silva created ISPN-11091:
-------------------------------------------
Summary: Add feature to read server logs from ContainerInfinispanServerDriver
Key: ISPN-11091
URL: https://issues.redhat.com/browse/ISPN-11091
Project: Infinispan
Issue Type: Enhancement
Components: Docker, Server, Test Suite
Affects Versions: 10.1.0.CR1
Reporter: Gustavo Lira e Silva
Assignee: Gustavo Lira e Silva
Will be very useful if we could get the server log from ContainerInfinispanServerDriver.
Something like?
{code:java}
SERVER.getServerDriver().getLog();
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (ISPN-10836) Docs Productization: Marshalling
by Donald Naro (Jira)
[ https://issues.redhat.com/browse/ISPN-10836?page=com.atlassian.jira.plugi... ]
Donald Naro updated ISPN-10836:
-------------------------------
Sprint: (was: DataGrid Sprint #38)
> Docs Productization: Marshalling
> --------------------------------
>
> Key: ISPN-10836
> URL: https://issues.redhat.com/browse/ISPN-10836
> Project: Infinispan
> Issue Type: Enhancement
> Components: Documentation
> Reporter: Donald Naro
> Assignee: Donald Naro
> Priority: Major
> Fix For: 10.1.0.Final
>
>
> Productize content for marshalling and protostream.
> Modularize existing content.
> Show consistent examples for usage (i.e. should match CLI example).
> Identify additional changes and work to develop customer content.
> Review Server Guide marshalling section (8. Adding Custom Marshaller Bridges) and make sure this is relevant and up to date for DG 8
> From Ryan:
> - protostream and marshalling:
> The important things to document are:
> Jboss marshalling no longer present by default, infinispan-jboss-marshalling jar must be added to the classpath of the client/server if required.
> - Externalizers ignored unless this is present
> Protostream is the default marshaller for user types. Need to document the process of generating marshallers using pojos, and configuring the serialization context.
> - Best practices on how to evolve schemas to ensure backwards-compatibility
> Possible to configure a custom user marshaller in embedded mode, for example if the user wants to use Java Serialization but not jboss marshalling.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (ISPN-11090) Docs: fixing maven build erros
by Donald Naro (Jira)
[ https://issues.redhat.com/browse/ISPN-11090?page=com.atlassian.jira.plugi... ]
Donald Naro updated ISPN-11090:
-------------------------------
Description:
[INFO] --- asciidoctor-maven-plugin:2.0.0-RC.1:process-asciidoc (html) @ infinispan-docs ---
...
[INFO] asciidoctor: INFO: possible invalid reference: protostream_cm_config
[INFO] asciidoctor: INFO: possible invalid reference: _configuration
[INFO] asciidoctor: WARN: topics/transactions.adoc: line 2: id assigned to section already in use: transactions
[INFO] asciidoctor: INFO: possible invalid reference: _building_infinispan
[INFO] asciidoctor: INFO: possible invalid reference: _comments
[INFO] asciidoctor: ERROR: titles/server/stories.adoc: line 9: include file not found: /home/dnaro/git/infinispan/documentation/src/main/asciidoc/stories/assembly_server_single_port.adoc
[INFO] asciidoctor: WARN: topics/con_memcached_client_encoding.adoc: line 2: section title out of sequence: expected level 2, got level 3
was:Productize server docs, chapter 7. Single Port
> Docs: fixing maven build erros
> ------------------------------
>
> Key: ISPN-11090
> URL: https://issues.redhat.com/browse/ISPN-11090
> Project: Infinispan
> Issue Type: Enhancement
> Components: Documentation
> Reporter: Donald Naro
> Assignee: Donald Naro
> Priority: Major
>
> [INFO] --- asciidoctor-maven-plugin:2.0.0-RC.1:process-asciidoc (html) @ infinispan-docs ---
> ...
> [INFO] asciidoctor: INFO: possible invalid reference: protostream_cm_config
> [INFO] asciidoctor: INFO: possible invalid reference: _configuration
> [INFO] asciidoctor: WARN: topics/transactions.adoc: line 2: id assigned to section already in use: transactions
> [INFO] asciidoctor: INFO: possible invalid reference: _building_infinispan
> [INFO] asciidoctor: INFO: possible invalid reference: _comments
> [INFO] asciidoctor: ERROR: titles/server/stories.adoc: line 9: include file not found: /home/dnaro/git/infinispan/documentation/src/main/asciidoc/stories/assembly_server_single_port.adoc
> [INFO] asciidoctor: WARN: topics/con_memcached_client_encoding.adoc: line 2: section title out of sequence: expected level 2, got level 3
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months