- The FAST Query Language (FQL) supports both post & prefix wildcards – unfortunately the standard search box in SharePoint will only work with prefix wildcards.
- You can use up to 3 whole word extractors – these are a very efficient way to enhance your search refiners.
- FAST automatically recognizes the “primary” language of a document but it does not really do “translation” of search results.
- The native content processing pipeline stages have been written in Python.
- People search in SharePoint Server 2010 is still powered by SharePoint and not by Fast Search Server 2010 for SharePoint – check out How to get SharePoint 2010 people search to work with FAST Search 2010
- Word document thumbnail preview and PowerPoint preview is not powered by FAST Search Server 2010 but by the Office Web Apis (see Two little known facts about the thumbnail and Powerpoint preview feature in FAST Search Server 2010 for more details)
- There are already a number of standard property extractors available in FAST – for companies, locations and person names. Companies and Locations are activated by default but not present in the search result page. The person names extractor is not activated by default and you will need to modify OptionalProcessing.xml to allow for person name extraction – see Using the default property extractors in FAST and how it works with the search refinements
- If you want to try out FAST and SharePoint without having to do a complete install yourself, you can use the 2010 Information Worker Demonstration and Evaluation Virtual Machine (RTM) image – which also includes FAST Search Server 2010 for SharePoint but … don’t forget to create a new certificate – see Having problems with FAST and the Microsoft Information Worker virtual image, try creating a new certificate.
Occasional rantings about Dynamics CRM/365, Power BI and Azure cloud. Taking the first small steps in machine learning, Python and algorithmic trading
No comments:
Post a Comment