[ https://issues.apache.org/jira/browse/SOLR-11879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16338665#comment-16338665 ]
Noble Paul commented on SOLR-11879: ----------------------------------- bq.It's bad practice to use exceptions as signaling... I assume there should be an easy way to avoid doing so here? yes. there should be a better way to avoid this by using a different method which is not expected to throw an Exception. > avoid creating a new Exception object for EOFException in FastinputStream > ------------------------------------------------------------------------- > > Key: SOLR-11879 > URL: https://issues.apache.org/jira/browse/SOLR-11879 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Environment: FastI > Reporter: Noble Paul > Assignee: Noble Paul > Priority: Trivial > Attachments: SOLR-11879.patch > > > FastInputStream creates and throws a new EOFException, every time an end of > stream is encountered. This is wasteful as we never use the stack trace > anywhere -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org