[
https://issues.apache.org/jira/browse/LUCENE-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14652022#comment-14652022
]
Robert Muir commented on LUCENE-6714:
-------------------------------------
Looks good. Can we change resourceDescription/resourceDesc to just be one way
for all 3 exceptions? Then they will have a consistent API. I prefer the longer
one personally.
> Expose version and resource description in CorruptIndexException and friends
> ----------------------------------------------------------------------------
>
> Key: LUCENE-6714
> URL: https://issues.apache.org/jira/browse/LUCENE-6714
> Project: Lucene - Core
> Issue Type: Improvement
> Affects Versions: 5.2.1
> Reporter: Simon Willnauer
> Priority: Minor
> Fix For: 5.3, Trunk
>
> Attachments: LUCENE-6714.patch
>
>
> It would be nice to access the minVersion, maxVersion in IndexTooNewException
> and IndexTooOldException as well as the resoruce description in
> CorruptIndexException programmatically. I'd love to use this to support
> better serialization on top of those exception as well as structured
> responses from the individual values.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
