[JBoss JIRA] (ISPN-10698) Remove InternalDataContainerAdapter
by Will Burns (Jira)
Will Burns created ISPN-10698:
---------------------------------
Summary: Remove InternalDataContainerAdapter
Key: ISPN-10698
URL: https://issues.jboss.org/browse/ISPN-10698
Project: Infinispan
Issue Type: Task
Components: Core
Reporter: Will Burns
The InternalDataContainerAdapter class was originally added for when a user could define a custom data container. Now that this has been removed, we no longer need the class.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (ISPN-10513) Docs: Server Monitoring
by Donald Naro (Jira)
[ https://issues.jboss.org/browse/ISPN-10513?page=com.atlassian.jira.plugin... ]
Donald Naro updated ISPN-10513:
-------------------------------
Summary: Docs: Server Monitoring (was: Docs: Monitoring)
> Docs: Server Monitoring
> -----------------------
>
> Key: ISPN-10513
> URL: https://issues.jboss.org/browse/ISPN-10513
> Project: Infinispan
> Issue Type: Enhancement
> Components: Documentation-Servers
> Reporter: Donald Naro
> Assignee: Donald Naro
> Priority: Major
>
> As an admin, I need to monitor servers and gather statistics for performance and troubleshooting.
> As an admin, I need to view log files and configure logging levels.
> As an admin, I need to gather statistics and perform remote operations via JMX.
> As an admin, I want to enable Prometheus monitoring.
> As an admin, I want to retrieve server health from the REST endpoint.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (ISPN-10513) Docs: Monitoring
by Donald Naro (Jira)
[ https://issues.jboss.org/browse/ISPN-10513?page=com.atlassian.jira.plugin... ]
Donald Naro closed ISPN-10513.
------------------------------
Resolution: Duplicate Issue
JDG-3215
> Docs: Monitoring
> ----------------
>
> Key: ISPN-10513
> URL: https://issues.jboss.org/browse/ISPN-10513
> Project: Infinispan
> Issue Type: Enhancement
> Components: Documentation-Servers
> Reporter: Donald Naro
> Assignee: Donald Naro
> Priority: Major
>
> As an admin, I need to monitor servers and gather statistics for performance and troubleshooting.
> As an admin, I need to view log files and configure logging levels.
> As an admin, I need to gather statistics and perform remote operations via JMX.
> As an admin, I want to enable Prometheus monitoring.
> As an admin, I want to retrieve server health from the REST endpoint.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (ISPN-10513) Docs: Monitoring
by Donald Naro (Jira)
[ https://issues.jboss.org/browse/ISPN-10513?page=com.atlassian.jira.plugin... ]
Donald Naro reopened ISPN-10513:
--------------------------------
> Docs: Monitoring
> ----------------
>
> Key: ISPN-10513
> URL: https://issues.jboss.org/browse/ISPN-10513
> Project: Infinispan
> Issue Type: Enhancement
> Components: Documentation-Servers
> Reporter: Donald Naro
> Assignee: Donald Naro
> Priority: Major
>
> As an admin, I need to monitor servers and gather statistics for performance and troubleshooting.
> As an admin, I need to view log files and configure logging levels.
> As an admin, I need to gather statistics and perform remote operations via JMX.
> As an admin, I want to enable Prometheus monitoring.
> As an admin, I want to retrieve server health from the REST endpoint.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (ISPN-10513) Docs: Monitoring
by Donald Naro (Jira)
[ https://issues.jboss.org/browse/ISPN-10513?page=com.atlassian.jira.plugin... ]
Donald Naro updated ISPN-10513:
-------------------------------
Comment: was deleted
(was: JDG-3215)
> Docs: Monitoring
> ----------------
>
> Key: ISPN-10513
> URL: https://issues.jboss.org/browse/ISPN-10513
> Project: Infinispan
> Issue Type: Enhancement
> Components: Documentation-Servers
> Reporter: Donald Naro
> Assignee: Donald Naro
> Priority: Major
>
> As an admin, I need to monitor servers and gather statistics for performance and troubleshooting.
> As an admin, I need to view log files and configure logging levels.
> As an admin, I need to gather statistics and perform remote operations via JMX.
> As an admin, I want to enable Prometheus monitoring.
> As an admin, I want to retrieve server health from the REST endpoint.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (IPROTO-119) Introduce a customizable TypeId mapper to support changing type ids (and names) for schema evolution
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/IPROTO-119?page=com.atlassian.jira.plugin... ]
Ryan Emerson edited comment on IPROTO-119 at 10/1/19 6:32 AM:
--------------------------------------------------------------
I'm happy for {{mapTypeName}} to be removed, as like you say type names should never be changed as per protobuf conventions. However, as TypeId is a protostream construct I think we should try and provide a mechanism for mapping.
We could add methods to ProtobufUtil that have a boolean param, which if true indicates that the legacy Ids from the configured mapper should be used. Something like {{ProtobufUtil.toWrappedStream(ImmutableSerializationContext ctx, OutputStream out, Object t, boolean legacyTypeIds)}} and the same for the corresponding read method(s). In Infinispan, we then set this boolean to true if an old client is used.
was (Author: ryanemerson):
I'm happy for {{mapTypeName}} to be removed, as like you say type names should never be changed as per protobuf conventions. However, as TypeId is a protostream construct I think we should try and provide a mechanism for mapping.
We could add methods to ProtobufUtil that have a boolean param, which if true indicates that the legacy Ids should be used. Something like {{ProtobufUtil.toWrappedStream(ImmutableSerializationContext ctx, OutputStream out, Object t, boolean legacyTypeIds)}} and the same for the corresponding read method(s). In Infinispan, we then set this boolean to true if an old client is used.
> Introduce a customizable TypeId mapper to support changing type ids (and names) for schema evolution
> ----------------------------------------------------------------------------------------------------
>
> Key: IPROTO-119
> URL: https://issues.jboss.org/browse/IPROTO-119
> Project: Infinispan ProtoStream
> Issue Type: Enhancement
> Reporter: Nistor Adrian
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 4.3.0.Alpha13
>
>
> This should be a simple interface for mapping type ids in and out. Should be specified in Configuration
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (IPROTO-119) Introduce a customizable TypeId mapper to support changing type ids (and names) for schema evolution
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/IPROTO-119?page=com.atlassian.jira.plugin... ]
Ryan Emerson commented on IPROTO-119:
-------------------------------------
I'm happy for {{mapTypeName}} to be removed, as like you say type names should never be changed as per protobuf conventions. However, as TypeId is a protostream construct I think we should try and provide a mechanism for mapping.
We could add methods to ProtobufUtil that have a boolean param, which if true indicates that the legacy Ids should be used. Something like {{ProtobufUtil.toWrappedStream(ImmutableSerializationContext ctx, OutputStream out, Object t, boolean legacyTypeIds)}} and the same for the corresponding read method(s). In Infinispan, we then set this boolean to true if an old client is used.
> Introduce a customizable TypeId mapper to support changing type ids (and names) for schema evolution
> ----------------------------------------------------------------------------------------------------
>
> Key: IPROTO-119
> URL: https://issues.jboss.org/browse/IPROTO-119
> Project: Infinispan ProtoStream
> Issue Type: Enhancement
> Reporter: Nistor Adrian
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 4.3.0.Alpha13
>
>
> This should be a simple interface for mapping type ids in and out. Should be specified in Configuration
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months