[JBoss JIRA] (ISPN-12353) REST allow backup restore progress to be submitted and polled
by Ryan Emerson (Jira)
[ https://issues.redhat.com/browse/ISPN-12353?page=com.atlassian.jira.plugi... ]
Ryan Emerson updated ISPN-12353:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/8714
> REST allow backup restore progress to be submitted and polled
> -------------------------------------------------------------
>
> Key: ISPN-12353
> URL: https://issues.redhat.com/browse/ISPN-12353
> Project: Infinispan
> Issue Type: Enhancement
> Components: REST
> Affects Versions: 12.0.0.Dev03
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 12.0.0.Final
>
>
> The current rest endpoint for restoring backups is too restrictive, as there is no way to submit a restoration and then poll it's current status. We should add the following so that the endpoints are akin to the process for creating a backup:
> {code}
> # Create, return 202 or 409 if {restoreName} already exists
> POST /rest/v2/cache-managers/{cacheManagerName}/restores/{restoreName}
> # Poll progress 201 complete, 202 if in progress, or 404 if not found
> HEAD /rest/v2/cache-managers/{cacheManagerName}/restores/{restoreName}
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (ISPN-9776) Disconnected Near Cache
by Will Burns (Jira)
[ https://issues.redhat.com/browse/ISPN-9776?page=com.atlassian.jira.plugin... ]
Will Burns commented on ISPN-9776:
----------------------------------
So my take on this is having a setting, per cache, that when enabled would not throw an error if it cannot connect to a server. Instead it would return null and use near cache values if present. Then as mentioned in the description upon reconnecting with a given server we would clear the near cache. Also once we have found we are not connected to any server we should probably fall back to returning null quickly, until a connection can be reestablished asynchronously.
> Disconnected Near Cache
> -----------------------
>
> Key: ISPN-9776
> URL: https://issues.redhat.com/browse/ISPN-9776
> Project: Infinispan
> Issue Type: Bug
> Components: Hot Rod
> Reporter: Tristan Tarrant
> Priority: Major
> Labels: keycloak
>
> The Hot Rod client with near cache enabled should have the option to be able to work in disconnected mode. On reconnection the near cache should be invalidated.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (ISPN-12352) Set license information when missing
by Donald Naro (Jira)
[ https://issues.redhat.com/browse/ISPN-12352?page=com.atlassian.jira.plugi... ]
Donald Naro updated ISPN-12352:
-------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Set license information when missing
> ------------------------------------
>
> Key: ISPN-12352
> URL: https://issues.redhat.com/browse/ISPN-12352
> Project: Infinispan
> Issue Type: Enhancement
> Components: Build
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Priority: Major
> Fix For: 11.0.4.Final, 12.0.0.Dev04
>
>
> There are some dependencies that don't report the licenses in the expected places (pom.xml for maven, package.json for nodejs). In those cases, the license is reported as "unknown" or empty.
> Create a new class in infinispan-tools where it receives an XML (manually created) with the licenses for "problematic" dependencies and merge it in the licenses.xml file. It shouldn't touch correct reported licenses.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years