[ https://issues.apache.org/jira/browse/LUCENE-6084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14229840#comment-14229840 ]
Robert Muir commented on LUCENE-6084: ------------------------------------- +1 Can we look at Lucene50PostingsWriter flushing and corruptindexexception? I know for example, this one (possibly other codecs) try to do some minimal checks against their input (like docid >= 0), but then have a hard time throwing corruptindexexception. this can be a followup issue > Add reasonable IndexOutput.toString > ----------------------------------- > > Key: LUCENE-6084 > URL: https://issues.apache.org/jira/browse/LUCENE-6084 > Project: Lucene - Core > Issue Type: Improvement > Reporter: Michael McCandless > Assignee: Michael McCandless > Priority: Minor > Fix For: 5.0, Trunk > > Attachments: LUCENE-6084.patch > > > In LUCENE-3539 we fixed IndexInput.toString to always include the > resourceDescription. > I think we should do the same for IndexOutput? > I don't think Lucene currently uses/relies on IndexOutput.toString, but e.g. > at least Elasticsearch does, and likely others, so I think it can only help > if you can see which path is open by this IndexOutput. -- 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