[
https://issues.apache.org/jira/browse/TIKA-863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13404580#comment-13404580
]
Nick Burch commented on TIKA-863:
-
Should be fixed in r1355782. We now avoid creating a new
[
https://issues.apache.org/jira/browse/TIKA-863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13220812#comment-13220812
]
Andrzej Bialecki commented on TIKA-863:
Nick, is there a chance of this making 1.1
[
https://issues.apache.org/jira/browse/TIKA-863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13210205#comment-13210205
]
Nick Burch commented on TIKA-863:
-
I'm not sure if we should be setting it as
[
https://issues.apache.org/jira/browse/TIKA-863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13210221#comment-13210221
]
Andrzej Bialecki commented on TIKA-863:
I see your point, it makes sense - no
[
https://issues.apache.org/jira/browse/TIKA-863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13210236#comment-13210236
]
Nick Burch commented on TIKA-863:
-
I'm not sure what the best way is to provide an
[
https://issues.apache.org/jira/browse/TIKA-863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13210242#comment-13210242
]
Andrzej Bialecki commented on TIKA-863:
This would work in my case, too. Though the
[
https://issues.apache.org/jira/browse/TIKA-863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13210245#comment-13210245
]
Nick Burch commented on TIKA-863:
-
We could check for the TikaConfig on the ParseContext,
