accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-4554) Fail gracefully on an un-parseable version string
Date Wed, 02 Aug 2017 18:45:01 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-4554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16111507#comment-16111507
] 

Christopher Tubbs commented on ACCUMULO-4554:
---------------------------------------------

Updating fixVersion, since [~milleruntime] backported [~glitch]'s fix to 1.7.4 and 1.8.2

> Fail gracefully on an un-parseable version string
> -------------------------------------------------
>
>                 Key: ACCUMULO-4554
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4554
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Minor
>             Fix For: 1.7.4, 1.8.2, 2.0.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Just had a delightfully odd failure case where every single IT that used a minicluster
would timeout and fail.
> Turns out, if you happen to set a version on Accumulo (e.g. what I might do if I were
testing locally and wanted to be isolated) which doesn't match what Version.java *wants* your
version to be, an {{IllegalArgumentException}} is thrown which brings down all of the processes.
> The fun part is that this Version is used no-where, save the {{accumulo version}} command.
We can and should fail gracefully -- there is no reason we should fail hard as we do now.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message