Solr突出顯示返回空結果

Question

我有一個搜索系統，與Solr 4.9配合使用，具有開箱即用的配置和架構。

在Solr 6.2中，高亮表項將在結果中返回，但它們僅包含文檔ID - 沒有高亮文本。

起初我以為是因為“內容”不在默認（托管）架構中，但添加它並沒有任何區別。 在任何情況下，默認架構（作者，主題，標題......）中都有其他字段可以返回高亮文本，但我也沒有得到任何內容。

在默認配置中似乎啟用了突出顯示，我的查詢似乎沒問題（從Admin界面運行時它也不會返回任何HL文本，因此排除了我的代碼）：

q = mike＆rows = 10＆start = 0＆sort = score desc，last_modified desc＆wt = json＆fl = content_type，fsb_doctype，author，id，last_modified，subject，title，score，url＆hl = true＆hl.fragsize = 250＆hl.fl = content，author，subject，title＆hl。 simple.pre =％板3Cb％3E＆hl.simple.post =％3C％2FB％3E＆端面=真facet.field = fsb_doctype＆facet.field = fsb_origin＆facet.field = fsb_mission

我所做的唯一架構更改是添加了3個用於分面的自定義字段。

這是在Solr 4.9系統上返回的json樣本（只是突出顯示部分）：

"highlighting":{"/event_20060718.cfm":{"content":[" \n \n \n \n \n \n \n Code 582 - Events \n \n July 18, 2006 - Flight Software Branch <b>CMMI</b> <b>Appraisal</b> \n\n \nThe Flight Software Branch was successful in its latest <b>CMMI</b> <b>appraisal</b> - a SCAMPI Class A <b>Appraisal</b> of the Supplier Agreement Management (SAM"]},"/SDODocs/":{"content":[" \n \n \n \n \n \n \n SDO Flight Software \n \n \t \t SDO Flight Software Baselined Documents \n(Restricted access - contains only assets used in the <b>CMMI</b> <b>appraisal</b>. For access to up-to-date SDO FSW documents, see M W.) \n \t \t SDO Flight"]},"/LRO/":{"content":[" \n \n \n \n \n \n \n LRO Flight Software \n \n \t \t LRO Flight Software Baselined Documents \n(Restricted access - contains only assets used in the <b>CMMI</b> <b>appraisal</b>. For access to up-to-date LRO FSW documents, see Mike B.) \n \t \t LRO Flight"]},"TDL_582 Web&id=501":{"content":[" \n \n \n \n \n \n \n Action item from 582 Web group - group id 501 - closed item \n \n Michael \n Mike Tilley \n Update Events - <b>CMMI</b> <b>appraisal</b> results are official today! \n 09/18/14 - updated/created & deployed:\n\n/default.cfm\n\n/events.cfm"]},"TDL_582 Web&id=203":{"content":[" \n \n \n \n \n \n \n Action item from 582 Web group - group id 203 - closed item \n \n Michael \n Mike Tilley \n <b>CMMI</b> <b>Appraisal</b> results are \"official\" today - post an event. \n 10/11/11 - updated/created & moved to production (& Linux)..\n\n/default.cfm"]},"TDL_BSR FPI&id=1":{"content":[" \n \n \n \n \n \n \n Action item from BSR FPI group - group id 1 - closed item \n \n Michael \n Mike Tilley \n Action: send a BSR template, customized for FPI, to Victor. \n 12/15/10 - done (distracted by <b>CMMI</b> <b>Appraisal</b>!) \n "]},"/event_20080516.cfm":{"content":[" \n \n \n \n \n \n \n Code 582 - Events \n \n May 16, 2008 - Center <b>CMMI</b> <b>Appraisal</b> \n\n\n A <b>CMMI</b> SCAMPI Class A <b>Appraisal</b> for GSFC was completed successfully on Friday, May 16th. GSFC is now compliant with Agency policy regarding <b>CMMI</b> Maturity Level 2 for"]},"/event_20140918.cfm":{"content":[" \n \n \n \n \n \n \n Code 582 - Events \n \n September 18, 2014 - Center <b>CMMI</b> <b>Appraisal</b> \n\n\n A <b>CMMI</b> SCAMPI Class A <b>Appraisal</b> for GSFC was completed successfully on Monday, September 15th. GSFC continues to be compliant with Agency policy regarding <b>CMMI</b>"]},"TDL_582 Web&id=353":{"content":[" & we made the mistake of trying to use the same repository for the team, and for <b>CMMI</b> <b>appraisal</b> evidence. As a result, the team never used it, and it contains sensitive <b>appraisal</b> data. Closing this AI. \n "]},"TDL_582 Web&id=67":{"content":[" \n \n \n \n \n \n \n Action item from 582 Web group - group id 67 - closed item \n \n Michael \n Mike Tilley \n Had to find the SEI certification page for the GSFC <b>CMMI</b> <b>appraisal</b> - it wasn't easy. Should probably post a link to this on the website"]}

這里是6.1 json結果的示例（在此服務器上設置略有不同的文檔，但第一個結果在兩種情況下都相同：

"highlighting":{"/event_20060718.cfm":{},"/event_20080516.cfm":{},"/event_20140918.cfm":{},"/event_20111011.cfm":{},"/LRO/":{},"/SDODocs/":{},"/event_20060201.cfm":{},"TDL_582 Web&id=353":{},"TDL_582 Web&id=67":{},"TDL_BSR JWST&id=94":{}

所以我得到的是一個沒有高亮文本的文檔ID列表。

Answer 1

將代碼更改為類似的代碼應該有效：

select?q=I+WANT+PIZZA&wt=php&indent=true&fl=id,name&group=true&group.field=content&hl=on&hl.fl=*&hl.encoder=html&hl.fragmenter=regex&hl.regex.slop=100.0&hl.fl=text_*&hl.bs.type=WHOLE&hl.defaultSummary=true&hl.offsetSource=POSTINGS