[JBoss JIRA] (ISPN-10836) Docs Productization: Marshalling
by Ryan Emerson (Jira)
[ https://issues.redhat.com/browse/ISPN-10836?page=com.atlassian.jira.plugi... ]
Ryan Emerson resolved ISPN-10836.
---------------------------------
Fix Version/s: 10.1.2.Final
11.0.0.Alpha1
Resolution: Done
> 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.2.Final, 11.0.0.Alpha1
>
>
> 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, 2 months
[JBoss JIRA] (ISPN-11266) Split CacheTopologyControlCommand into individual commands
by Ryan Emerson (Jira)
[ https://issues.redhat.com/browse/ISPN-11266?page=com.atlassian.jira.plugi... ]
Work on ISPN-11266 started by Ryan Emerson.
-------------------------------------------
> Split CacheTopologyControlCommand into individual commands
> ----------------------------------------------------------
>
> Key: ISPN-11266
> URL: https://issues.redhat.com/browse/ISPN-11266
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core
> Affects Versions: 10.1.1.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 11.0.0.Alpha1
>
>
> Currently the {{CacheTopologyControlCommand}} uses a Type field and a switch statement to differentiate between various topology actions. This worked well for the old Externalizer approach, however it does not fit well with protobuf messages. Instead, the CacheTopologyControlCommand should be split into individual commands, e.g. a TopologyJoinCommand etc.
> This enables the logic of the command types to be separated, making it easier to maintain backwards compatibility in the long term. Each command will use a ProtoStream TypeId in the range of 1000 -> 3999, so the cost of two bytes is the same as the existing class ID plus enum Type that we require with the single CacheTopologyControlCommand.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (ISPN-10362) Unify command initialization and invocation
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-10362?page=com.atlassian.jira.plugi... ]
Dan Berindei updated ISPN-10362:
--------------------------------
Fix Version/s: 11.0.0.Final
> Unify command initialization and invocation
> -------------------------------------------
>
> Key: ISPN-10362
> URL: https://issues.redhat.com/browse/ISPN-10362
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core
> Affects Versions: 10.0.0.Beta3
> Reporter: Dan Berindei
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 11.0.0.Alpha1, 11.0.0.Final
>
>
> ISPN-10322 unified command initialization with {{InitializableCommand}}, but we should go further and unify initialization with invocation.
> We can replace the current {{ReplicableCommand.invokeAsync}} and {{InitializableCommand.init(ComponentRegistry()}} methods with a method {{CacheRpcCommand.invokeAsync(ComponentRegistry)}} (or maybe {{execute}}?).
> For global commands we can create a {{GlobalRpcCommand}} interface with a method {{invokeAsync(GlobalComponentRegistry)}}.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (ISPN-10362) Unify command initialization and invocation
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-10362?page=com.atlassian.jira.plugi... ]
Dan Berindei updated ISPN-10362:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 11.0.0.Alpha1
Resolution: Done
> Unify command initialization and invocation
> -------------------------------------------
>
> Key: ISPN-10362
> URL: https://issues.redhat.com/browse/ISPN-10362
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core
> Affects Versions: 10.0.0.Beta3
> Reporter: Dan Berindei
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 11.0.0.Alpha1
>
>
> ISPN-10322 unified command initialization with {{InitializableCommand}}, but we should go further and unify initialization with invocation.
> We can replace the current {{ReplicableCommand.invokeAsync}} and {{InitializableCommand.init(ComponentRegistry()}} methods with a method {{CacheRpcCommand.invokeAsync(ComponentRegistry)}} (or maybe {{execute}}?).
> For global commands we can create a {{GlobalRpcCommand}} interface with a method {{invokeAsync(GlobalComponentRegistry)}}.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (ISPN-11282) CLI: site command isn't working properly
by Ryan Emerson (Jira)
[ https://issues.redhat.com/browse/ISPN-11282?page=com.atlassian.jira.plugi... ]
Ryan Emerson resolved ISPN-11282.
---------------------------------
Resolution: Done
> CLI: site command isn't working properly
> ----------------------------------------
>
> Key: ISPN-11282
> URL: https://issues.redhat.com/browse/ISPN-11282
> Project: Infinispan
> Issue Type: Bug
> Components: CLI
> Affects Versions: 10.1.1.Final
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Priority: Major
> Fix For: 10.1.2.Final, 11.0.0.Alpha1
>
>
> * {{site status}}: option {{--site}} isn't working properly. It returns all the backups even if you use a non-existing site:
> {noformat}
> [pedro-laptop-3-35787@cluster//containers/default]> site status --cache=xsiteCache
> {
> "NYC" : "online"
> }
> [pedro-laptop-3-35787@cluster//containers/default]> site status --cache=xsiteCache --site=NYC
> {
> "NYC" : "online"
> }
> [pedro-laptop-3-35787@cluster//containers/default]> site status --cache=xsiteCache --site=ajdhds
> {
> "NYC" : "online"
> }
> {noformat}
> * {{clear-push-state-status}} operation isn't registered
> * {{bring-online}} and {{take-offline}} operations seems to fail:
> {noformat}
> [pedro-laptop-3-35787@cluster//containers/default]> site take-offline --cache=xsiteCache --site=NYC
> Not Found
> [pedro-laptop-3-35787@cluster//containers/default]> site status --cache=xsiteCache
> {
> "NYC" : "offline"
> }
> [pedro-laptop-3-35787@cluster//containers/default]> site bring-online --cache=xsiteCache --site=NYC
> Not Found
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months