[ https://issues.apache.org/jira/browse/TIKA-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105609#comment-15105609 ]
ASF GitHub Bot commented on TIKA-1834: -------------------------------------- GitHub user smadha opened a pull request: https://github.com/apache/tika/pull/71 fix for TIKA-1834 contributed by msha...@usc.edu You can merge this pull request into a Git repository by running: $ git pull https://github.com/smadha/tika TIKA-1834 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/tika/pull/71.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #71 ---- commit 0154e3067c8a63ab176e4e2161515d2d7d45b8e7 Author: smadha <msha...@usc.edu> Date: 2016-01-18T18:08:18Z fix for TIKA-1834 contributed by msha...@usc.edu ---- > Fix for GeoTopic parser holding state while running Tika server > --------------------------------------------------------------- > > Key: TIKA-1834 > URL: https://issues.apache.org/jira/browse/TIKA-1834 > Project: Tika > Issue Type: Sub-task > Components: parser > Affects Versions: 1.12 > Environment: All > Reporter: Madhav Sharan > Fix For: 1.12 > > > While using TIKA-server we observed that GeoTopic parser started holding > state and returned all the location retrieved for any previous request. > This was happening as mutable object > org.apache.tika.parser.geo.topic.NameEntityExtractor was initialised once and > then was reused by all request. > As part of this fix org.apache.tika.parser.geo.topic.NameEntityExtractor is > recreated for every request. -- This message was sent by Atlassian JIRA (v6.3.4#6332)