[
https://issues.apache.org/jira/browse/BLUR-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gagan Deep Juneja updated BLUR-54:
----------------------------------
Attachment: 0001-BLUR-ID-54-Error-handling-for-bad-Shard-Id.patch
This issue been fixed. I am attaching patch here. please provide your feedback.
Regards,
Gagan
> Improve the error when a bad shard index is provided.
> -----------------------------------------------------
>
> Key: BLUR-54
> URL: https://issues.apache.org/jira/browse/BLUR-54
> 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: http://www.atlassian.com/software/jira
