incubator-blur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron McCurry (JIRA)" <>
Subject [jira] [Closed] (BLUR-54) Improve the error when a bad shard index is provided.
Date Fri, 08 Mar 2013 03:04:13 GMT


Aaron McCurry closed BLUR-54.

    Resolution: Fixed;a=commit;h=adeeabd7f615d2ecb99aea93316359b5aede1cd5

Thanks Gagan!
> Improve the error when a bad shard index is provided.
> -----------------------------------------------------
>                 Key: BLUR-54
>                 URL:
>             Project: Apache Blur
>          Issue Type: Bug
>    Affects Versions: 0.2.0
>            Reporter: Tim Williams
>            Priority: Trivial
>         Attachments: 0001-BLUR-ID-54-Error-handling-for-bad-Shard-Id.patch
> Currently, if a client passes an unknown shard index, they get a message about a bad
connection string when in fact that's just a side effect.  I'm thinking that the TableLayout
implemented in ThriftBlurServer should throw a RuntimeException if it isn't found - because
that's where we have some useful context.  Sound reasonable?  Another option is to throw it
in BlurServer's getConnection.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message