To accomplish our FY 2018 goals, we continued backend development that will allow your agency content to be served directly from our indexes. In November, our team began testing our new system. We also released several features related to this project:
Collections results will now come from our indexes. Previously, a site that saw main page search results from our indexes would still see Bing or Google results when using Collections. Now, if a site is using our indexes for its main search page, its Collections results will also come from our indexes.
The page-1 RSS module and search page alert will now appear for sites getting results from our indexes. Previously, these two features only worked on sites using Bing/Google.
i14y documents will be rejected if the document_id contains slashes or is more than 512 bytes.
On November 14th, we notified our users of a Bing service degradation. This caused inconsistent results across sites, including incomplete results or 503 errors, and prevented access to the Search Admin Center. The inconsistency began at 2:05pm ET and ended at 3:05pm ET.
We continued transitioning our repos to use Circle CI.
Phrase searches now work with content that is served from our indexes. A search for “cheese curds” will return results for the specific phrase “cheese curds” rather than the separate words “cheese” and “curds”.