You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Kevin Sweeney (JIRA)" <ji...@apache.org> on 2014/12/22 19:40:13 UTC
[jira] [Commented] (AURORA-978) Client should confirm it's running
a valid version
[ https://issues.apache.org/jira/browse/AURORA-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14256021#comment-14256021 ]
Kevin Sweeney commented on AURORA-978:
--------------------------------------
+1 to better compatibility checks. We've got the APIVersion struct but haven't done much with it.
I'm generally -1 to self-updating; that's a concern for a package manager and will vary a lot based on environment. However, I do think that many of the clusters.json parameters should be configured on the scheduler, with the client just needing the scheduler's URL (zk:// or http(s)://).
> Client should confirm it's running a valid version
> --------------------------------------------------
>
> Key: AURORA-978
> URL: https://issues.apache.org/jira/browse/AURORA-978
> Project: Aurora
> Issue Type: Story
> Components: Client, Reliability
> Reporter: Joe Smith
>
> Right now there's no validation for client version, although there is a check for API compatibility.
> Since someone could have received an older client and failed to have it updated, we should consider an additional check which confirms accepted client versions, and prints a message + update instructions if not (or even more rad would be to self-update if possible)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)