June 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11671) Start a State transfer for a cache

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-11671?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-11671: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Start a State transfer for a cache > ---------------------------------- > > Key: ISPN-11671 > URL: https://issues.redhat.com/browse/ISPN-11671 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Affects Versions: 10.1.6.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Labels: console-ng > > * Add a state transfer button in the list of sites > * Ask for confirmation > * Display alert confirming the state transfer > * When the transfer is over, display the result (Ok Error) > * Once the state transfer is going on, the button displayed is 'Cancel' > * Once the state transfer is over or canceled, we must clear the result to launch a new one -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11672) Cancel State transfer for a cache

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-11672?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-11672: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Cancel State transfer for a cache > --------------------------------- > > Key: ISPN-11672 > URL: https://issues.redhat.com/browse/ISPN-11672 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Affects Versions: 10.1.6.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Labels: console-ng > > When a state transfer is going on, we can cancel it with an action button > Confirmation message is asked > When cancelation is done, display a message > The status displayed is cancelled -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11669) Display Cross Site Replication Sites for a Cache

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-11669?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-11669: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Display Cross Site Replication Sites for a Cache > ------------------------------------------------ > > Key: ISPN-11669 > URL: https://issues.redhat.com/browse/ISPN-11669 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Affects Versions: 10.1.6.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Labels: console-ng > > Display the number of backups in the header of a cache that has remote backups > Add a link to manage those backups > https://marvelapp.com/620b19g/screen/68148080 > The link lands into a new page to manage those backups > The data displayed in a list > * Site name > * Status > https://marvelapp.com/620b19g/screen/68148081 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11670) Turn On/Off a Site for a cache

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-11670?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-11670: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Turn On/Off a Site for a cache > ------------------------------ > > Key: ISPN-11670 > URL: https://issues.redhat.com/browse/ISPN-11670 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Affects Versions: 10.1.6.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Labels: console-ng > > Add an action to turn On or Off a site > If the status is online, turn of offline > if the status is offline, turn online > If the status is mixed, allow both > https://marvelapp.com/620b19g/screen/68148081 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11991) Docs: Iteration during RU returns incorrect values if numSegments does not match

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-11991?page=com.atlassian.jira.plugi... ] Donald Naro closed ISPN-11991. ------------------------------ > Docs: Iteration during RU returns incorrect values if numSegments does not match > -------------------------------------------------------------------------------- > > Key: ISPN-11991 > URL: https://issues.redhat.com/browse/ISPN-11991 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > Fix For: 11.0.0.Final > > > {color:#172b4d}make sure it is documented that while a rolling upgrade procedure is occurring iteration upon the new server may result in incorrect values if the # of segments has changed{color} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11991) Docs: Iteration during RU returns incorrect values if numSegments does not match

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11991?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11991: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8466 > Docs: Iteration during RU returns incorrect values if numSegments does not match > -------------------------------------------------------------------------------- > > Key: ISPN-11991 > URL: https://issues.redhat.com/browse/ISPN-11991 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > {color:#172b4d}make sure it is documented that while a rolling upgrade procedure is occurring iteration upon the new server may result in incorrect values if the # of segments has changed{color} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11991) Docs: Iteration during RU returns incorrect values if numSegments does not match

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11991?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11991: ------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 11.0.0.Final Resolution: Done > Docs: Iteration during RU returns incorrect values if numSegments does not match > -------------------------------------------------------------------------------- > > Key: ISPN-11991 > URL: https://issues.redhat.com/browse/ISPN-11991 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > Fix For: 11.0.0.Final > > > {color:#172b4d}make sure it is documented that while a rolling upgrade procedure is occurring iteration upon the new server may result in incorrect values if the # of segments has changed{color} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11991) Docs: Iteration during RU returns incorrect values if numSegments does not match

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11991?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11991: ------------------------------ Status: Open (was: New) > Docs: Iteration during RU returns incorrect values if numSegments does not match > -------------------------------------------------------------------------------- > > Key: ISPN-11991 > URL: https://issues.redhat.com/browse/ISPN-11991 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > {color:#172b4d}make sure it is documented that while a rolling upgrade procedure is occurring iteration upon the new server may result in incorrect values if the # of segments has changed{color} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11993) Allow automatic registration of Protobuf schemas and marshallers

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-11993?page=com.atlassian.jira.plugi... ] Ryan Emerson updated ISPN-11993: -------------------------------- Description: Currently it's necessary for users to automatically add {{SerializationContextIntializer}} instances to the client via {{addContextInitializers}} and for .proto files to be registered like so: {code:java} Path proto = Paths.get(Query.class.getClassLoader().getResource("proto/sheep.proto").toURI()); cacheManager.getCache(ProtobufMetadataManagerConstants.PROTOBUF_METADATA_CACHE_NAME).put("sheep.proto", Files.readString(proto)); {code} Instead we should allow users to configure the client so that: # {{SerializationContextInitalizer}} services are automatically registerd if {{builder.autoAddAllContextInitializers()}} is configured. # {{*.proto}} files on the classpath and in available {{SerializationContextInitializers}} are automatically registered with the server if {{.autoRegisterSchemas()}} is configured. ProtoStreams {{AutoProtoSchemaBuilder}} already provides a `service` attribute to generate the service files for {{SerializationContextInitiailizer}}, however this is false by default. We should update this to true so that users have one less knob to confgure. NOTE: {{autoRegisterSchemas()}} will fail if authorization is enabled and the client does not have the ___schema_manager role. was: Currently it's necessary for users to automatically add {{SerializationContextIntializer}} instances to the client via {{addContextInitializers}} and for .proto files to be registered like so: {code:java} Path proto = Paths.get(Query.class.getClassLoader().getResource("proto/sheep.proto").toURI()); cacheManager.getCache(ProtobufMetadataManagerConstants.PROTOBUF_METADATA_CACHE_NAME).put("sheep.proto", Files.readString(proto)); {code} Instead we should allow users to configure the client so that: # {{SerializationContextInitalizer}} services are automatically registerd if {{builder.autoAddAllContextInitializers()}} is configured. # {{*.proto}} files on the classpath and in available {{SerializationContextInitializers}} are automatically registered with the server if {{.autoRegisterSchemas()}} is configured. ProtoStreams {{AutoProtoSchemaBuilder}} already provides a `service` attribute to generate the service files for {{SerializationContextInitiailizer}}, however this is false by default. We should update this to true so that users have one less knob to confgure. > Allow automatic registration of Protobuf schemas and marshallers > ---------------------------------------------------------------- > > Key: ISPN-11993 > URL: https://issues.redhat.com/browse/ISPN-11993 > Project: Infinispan > Issue Type: Feature Request > Components: Hot Rod, Marshalling > Affects Versions: 11.0.0.CR1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 12.0.0.Final > > > Currently it's necessary for users to automatically add {{SerializationContextIntializer}} instances to the client via {{addContextInitializers}} and for .proto files to be registered like so: > {code:java} > Path proto = Paths.get(Query.class.getClassLoader().getResource("proto/sheep.proto").toURI()); > cacheManager.getCache(ProtobufMetadataManagerConstants.PROTOBUF_METADATA_CACHE_NAME).put("sheep.proto", Files.readString(proto)); > {code} > Instead we should allow users to configure the client so that: > # {{SerializationContextInitalizer}} services are automatically registerd if {{builder.autoAddAllContextInitializers()}} is configured. > # {{*.proto}} files on the classpath and in available {{SerializationContextInitializers}} are automatically registered with the server if {{.autoRegisterSchemas()}} is configured. > ProtoStreams {{AutoProtoSchemaBuilder}} already provides a `service` attribute to generate the service files for {{SerializationContextInitiailizer}}, however this is false by default. We should update this to true so that users have one less knob to confgure. > NOTE: {{autoRegisterSchemas()}} will fail if authorization is enabled and the client does not have the ___schema_manager role. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11993) Allow automatic registration of Protobuf schemas and marshallers

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-11993?page=com.atlassian.jira.plugi... ] Ryan Emerson updated ISPN-11993: -------------------------------- Description: Currently it's necessary for users to automatically add {{SerializationContextIntializer}} instances to the client via {{addContextInitializers}} and for .proto files to be registered like so: {code:java} Path proto = Paths.get(Query.class.getClassLoader().getResource("proto/sheep.proto").toURI()); cacheManager.getCache(ProtobufMetadataManagerConstants.PROTOBUF_METADATA_CACHE_NAME).put("sheep.proto", Files.readString(proto)); {code} Instead we should allow users to configure the client so that: # {{SerializationContextInitalizer}} services are automatically registerd if {{builder.autoAddAllContextInitializers()}} is configured. # {{*.proto}} files on the classpath and in available {{SerializationContextInitializers}} are automatically registered with the server if {{.autoRegisterSchemas()}} is configured. ProtoStreams {{AutoProtoSchemaBuilder}} already provides a `service` attribute to generate the service files for {{SerializationContextInitiailizer}}, however this is false by default. We should update this to true so that users have one less knob to confgure. was: Currently it's necessary for users to automatically add {{SerializationContextIntializer}} instances to the client via {{addContextInitializers}} and for .proto files to be registered like so: {code:java} Path proto = Paths.get(Query.class.getClassLoader().getResource("proto/sheep.proto").toURI()); cacheManager.getCache(ProtobufMetadataManagerConstants.PROTOBUF_METADATA_CACHE_NAME).put("sheep.proto", Files.readString(proto)); {code} Instead we should allow users to configure the client so that: # {{SerializationContextInitalizer}} services are automatically registerd if {{builder.autoAddAllContextInitializers()}} is configured. # {{*.proto}} files on the classpath and in available {{SerializationContextInitializers}} are automatically registered with the server if {{.autoRegisterSchemas()}} is configured. ProtoStreams {{AutoProtoSchemaBuilder}} already provides a `service` attribute to generate the service files for {{SerializationContextInitiailizer}}, however this is false by default. We should update this to true so that users have one less knob to confgure. > Allow automatic registration of Protobuf schemas and marshallers > ---------------------------------------------------------------- > > Key: ISPN-11993 > URL: https://issues.redhat.com/browse/ISPN-11993 > Project: Infinispan > Issue Type: Feature Request > Components: Hot Rod, Marshalling > Affects Versions: 11.0.0.CR1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 12.0.0.Final > > > Currently it's necessary for users to automatically add {{SerializationContextIntializer}} instances to the client via {{addContextInitializers}} and for .proto files to be registered like so: > {code:java} > Path proto = Paths.get(Query.class.getClassLoader().getResource("proto/sheep.proto").toURI()); > cacheManager.getCache(ProtobufMetadataManagerConstants.PROTOBUF_METADATA_CACHE_NAME).put("sheep.proto", Files.readString(proto)); > {code} > Instead we should allow users to configure the client so that: > # {{SerializationContextInitalizer}} services are automatically registerd if {{builder.autoAddAllContextInitializers()}} is configured. > # {{*.proto}} files on the classpath and in available {{SerializationContextInitializers}} are automatically registered with the server if {{.autoRegisterSchemas()}} is configured. > ProtoStreams {{AutoProtoSchemaBuilder}} already provides a `service` attribute to generate the service files for {{SerializationContextInitiailizer}}, however this is false by default. We should update this to true so that users have one less knob to confgure. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2020