[ https://issues.apache.org/jira/browse/SOLR-6246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856300#comment-15856300 ]
jefferyyuan commented on SOLR-6246: ----------------------------------- This is great news. Thanks so much [~steve_rowe] for clarifying my questions. - I should do more search before asking here. My fault. I do read release notes for Solr 6.4.1 but not lucene 6.4.1 - which I should. Also I should have read the issue links this Jira depends on. > Core fails to reload when AnalyzingInfixSuggester is used as a Suggester > ------------------------------------------------------------------------ > > Key: SOLR-6246 > URL: https://issues.apache.org/jira/browse/SOLR-6246 > Project: Solr > Issue Type: Sub-task > Components: SearchComponents - other > Affects Versions: 4.8, 4.8.1, 4.9, 5.0, 5.1, 5.2, 5.3, 5.4 > Reporter: Varun Thacker > Assignee: Steve Rowe > Fix For: 6.5, master (7.0) > > Attachments: SOLR-6246.patch, SOLR-6246.patch, SOLR-6246-test.patch, > SOLR-6246-test.patch, SOLR-6246-test.patch, SOLR-6246-test.patch > > > LUCENE-5477 - added near-real-time suggest building to > AnalyzingInfixSuggester. One of the changes that went in was a writer is > persisted now to support real time updates via the add() and update() methods. > When we call Solr's reload command, a new instance of AnalyzingInfixSuggester > is created. When trying to create a new writer on the same Directory a lock > cannot be obtained and Solr fails to reload the core. > Also when AnalyzingInfixLookupFactory throws a RuntimeException we should > pass along the original message. > I am not sure what should be the approach to fix it. Should we have a > reloadHook where we close the writer? -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org