[
https://issues.apache.org/jira/browse/SOLR-11701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16295437#comment-16295437
]
Erick Erickson commented on SOLR-11701:
---------------------------------------
Tim:
I don't see a problem here then, I was mostly worried that this was an
inexplicable problem that would pop out other places. We'll upgrade slf4j
sometime anyway, so it seems to me that just adding the annotation is an OK fix.
At most, some of the @Slow or @Nightly or @Weekly tests will error out and need
a similar annotation, but we're in the beginning of a new release cycle so
there's time for those to flush out.
Any kind of blanket "don't report the full stack trace" seems like a bad idea
since that's often so necessary to analysis.
If you find anything out that's germane, let me know otherwise I'll just
annotate and commit (probably this evening).
Thanks for tracking this down!
> Upgrade to Tika 1.17 when available
> -----------------------------------
>
> Key: SOLR-11701
> URL: https://issues.apache.org/jira/browse/SOLR-11701
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Tim Allison
> Assignee: Erick Erickson
> Attachments: SOLR-11701.patch
>
>
> Kicking off release process for Tika 1.17 in the next few days. Please let
> us know if you have any requests.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
