使用 FAST Search Server 和 SharePoint 2010 的多值托管属性
我的场景是安装了 FAST Search Server 的 SharePoint 2010 环境。我使用 SharePoint KeywordQuery 类和 FQL（快速查询语言）来针对 FAST 索引执行查询。
我的问题： 显然，快速搜索服务器“不支持返回的查询结果中的数据类型感知”（如所述这里）。这意味着，对于映射到多个已爬网属性（例如“作者”）的托管属性，引擎将仅返回包含所有值的单个字符串。 （在这种情况下，SharePoint 搜索将返回一个字符串数组。）
我需要能够区分不同的值，因此我尝试寻找该问题的可能解决方案。这是我到目前为止发现的内容：
- 实现 自定义属性提取器 并引入不同值的分隔符。
- 修改例如 FAST 配置文件（例如 C:\FASTSearch\index-profiles\deployment-ready-index-profile.xml）并为不同值引入分隔符。
- 使用 KeywordQuery 类 (ResultType.RefinementResults) 的精简器功能并尝试在精简器结果和搜索结果之间进行映射。
在我看来，1 和 2 都不值得推荐，因为它们会改变“标准”托管属性的行为，从而对整个系统（例如在 FAST 搜索中心站点上）产生影响。此外，MS 似乎禁止 2，因为配置文件将被任何快速更新替换。 3 似乎是一个非常昂贵的操作。
还有其他我错过的解决方案吗？任何建议都将受到高度赞赏...
My scenario is a SharePoint 2010 environment with installed FAST Search Server. I am using the SharePoint KeywordQuery class with FQL (Fast Query Language) to execute queries against the FAST index.
My problem:
Apparently Fast Search Server 'does not support data type awareness in the returned query results' (as stated here). This means that for managed properties that are mapped to multiple crawled properties (e.g. "Author") the engine will only return a single string containing all values. (SharePoint search would return an array of strings in that case.)
I need to be able to distinguish between the different values, therefore I have tried to find possible solutions for that problem. Here is what I found so far:
- Implement a Custom Property Extractor and introduce a separator for different values.
- Modify e.g. FAST configuration files (e.g. C:\FASTSearch\index-profiles\deployment-ready-index-profile.xml) and introduce a separator for different values.
- Use the refiner functionality of the KeywordQuery class (ResultType.RefinementResults) and try a mapping between the refiner results and the search results.
Both 1 and 2 are not recommendable in my opinion as they would change the behavior of 'standard' managed properties which would have impact on the overall system (e.g. on a FAST Search Center site). Moreover, 2 seems to be forbidden by MS as the config files would be replaced by any FAST update. 3 seems to be a highly expensive operation.
Are there any other solutions I have missed? Any advice is highly appreciated...
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论