You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jim Challenger (JIRA)" <de...@uima.apache.org> on 2014/07/30 21:14:39 UTC
[jira] [Created] (UIMA-3967) DUCC SM cannot "undo" manual
modification to default ping parameters.
Jim Challenger created UIMA-3967:
------------------------------------
Summary: DUCC SM cannot "undo" manual modification to default ping parameters.
Key: UIMA-3967
URL: https://issues.apache.org/jira/browse/UIMA-3967
Project: UIMA
Issue Type: Improvement
Components: DUCC
Affects Versions: 1.0.0-Ducc
Reporter: Jim Challenger
Assignee: Jim Challenger
Fix For: 1.1.0-Ducc
Although it is possible to modify any service registration parameter, it can be difficult to undo an update to one of the pinger-related parameters - i.e. revert to the default. The ideal operation is simply to delete the modification, not to re-modify the pinger with another value.
The answer is to allow the value of an option under --modify to be 'delete', in which case the SM simply removes it from the service registration.
This is implemented only for pinger-related operations.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
Re: [jira] [Created] (UIMA-3967) DUCC SM cannot "undo" manual
modification to default ping parameters.
Posted by Burn Lewis <bu...@gmail.com>.
How about "default"?
On Wed, Jul 30, 2014 at 3:14 PM, Jim Challenger (JIRA) <de...@uima.apache.org>
wrote:
> Jim Challenger created UIMA-3967:
> ------------------------------------
>
> Summary: DUCC SM cannot "undo" manual modification to default
> ping parameters.
> Key: UIMA-3967
> URL: https://issues.apache.org/jira/browse/UIMA-3967
> Project: UIMA
> Issue Type: Improvement
> Components: DUCC
> Affects Versions: 1.0.0-Ducc
> Reporter: Jim Challenger
> Assignee: Jim Challenger
> Fix For: 1.1.0-Ducc
>
>
> Although it is possible to modify any service registration parameter, it
> can be difficult to undo an update to one of the pinger-related parameters
> - i.e. revert to the default. The ideal operation is simply to delete the
> modification, not to re-modify the pinger with another value.
>
> The answer is to allow the value of an option under --modify to be
> 'delete', in which case the SM simply removes it from the service
> registration.
>
> This is implemented only for pinger-related operations.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.2#6252)
>