Hot answers tagged fast-search
3
Please refer to the following blog post which described basics of sharepoint 2013 ranking models.
http://powersearching.wordpress.com/2013/03/29/how-sharepoint-2013-ranking-models-work/
Please let me know which model are you interested in, I will cover this in following posts.
2
You can use Refinements to find all the possible values for Managed Properties. Refinements will also include the counts for each Managed Property.
Look here for more details on how to configure:
http://msdn.microsoft.com/en-us/library/ff394639%28v=office.14%29.aspx
2
FAST cannot index user profiles. You need to configure enterprise search for this.
Make sure User Profile Synchronization is running and you have profiles imported
Give your search default content access account "Retrieve People Data for Search Crawlers" permission on User Profile Service Application
Configure a new Content Source "People" that points to ...
2
It seems that you have to add LastModifiedTimeStampField property to your Finder method. Take a look at this blog posts series from Todd Baginski, especially at this one -
The LastModifiedTimeStampField property on the finder method instance
is set for two reasons.
So search results will display the last time the data was updated
So the ...
2
This is NOT possible with Managed Property keyword queries. The only wildcard capability that Sharepoint Search Server 2010 supports is "Stemming". Stemming expects the characters to be matched by the characters at the start of a string in the index.
e.g. Item contains Title string "TestMe"
You're query can be : Title:"Tes" and that would pick up the ...
1
Fast Search (2010) will index javascript sites.
SharePoint Search (2013) will not index javascript.
References: http://social.msdn.microsoft.com/Forums/de-DE/sharepointsearch/thread/b2456e71-9308-43f8-8351-b013b5070cc5
http://blogs.technet.com/b/vedant/archive/2010/08/24/fast-search-server-2010-for-sharepoint-specific-indexing-connectors.aspx
1
As you have seen, the limit for the Query is actually 2048 characters. So any more than that will throw this exception.
http://stackoverflow.com/questions/8061330/how-to-overcome-fast-search-char-limitation-2048 is a possible duplicate of your question, but sadly it never recieved any attention.
Also this from Technet ...
1
Your best approach is to get titles on those weird formats into a separate managed property. Then you can do word searches on that property in FQL with less chance of the query bombing.
It's all about term expansion in the search engine core and how many terms would match and how big(slow) will the end query be.
The other approach is to create a full text ...
1
If you want to explore how rank is evaluated for a query check out http://powersearching.wordpress.com/2013/01/25/explain-rank-in-sharepoint-2013-search/ which explains how to access the ExplainRank.aspx page located in the 15 hive.
1
docacl is still persisted in 2010, but appropriate managed property has [SummaryType] set to Disabled. To see the value of this property you must set SummaryType to Static or Dynamic. I don't know how they encoded, usually single value looks like this:
winaecqaaaaaaaakfiaaaadf4pmsee5mubf43xwubpiamaaa
you can extract value of this property using ...
1
Yes! Each Search service application is either the Standard SharePoint Search or the Fast Connector/Query. Just separate them into their own service applications, and you should just configure the web applications to use two different sets of service connections, one including FAST and excluding sharepoint search, and the other using sharepoint search and ...
1
in my opinion, the crawled properties in both section should be the same.
You are not correct. FAST Query administration page has two section with access to managed properties and even link to Content Sources (under Crawling).
The reason for this is the fact that People Search does not go through FS4SP but instead uses the built-in SharePoint Search. ...
1
If you only need to search specific information from a single site collection throgh a special UI then you may be able to use SharePoint 2010 Site Search which translates the search into CAML queries.
Usually you'll setup the servers doing the crawl to request information from themselves so it'll "only" hurt that/these server(s) and SQL.
But every minute ...
1
With FAST Search you are going to have a separate set of servers dedicated to document processing, indexing and other components. The configuration options are very flexible so you'll need to come up with the proper architecture based on your specific requirements for content freshness, query throughput, index size and redundancy. Your SharePoint application ...
Only top voted, non community-wiki answers of a minimum length are eligible
