Solr参数(DisMax Event Facet)

2019-03-27 01:03|来源: 网路

一.DisMax

1.tie:query and init param for tiebreaker value
2.qf:query and init param for query fields
3.pf:query and init param for phrase boost fields
4.pf2:query and init param for bigram phrase boost fields
5.pf3:query and init param for trigram phrase boost fields
6.mm:query and init param for MinShouldMatch specification
7.ps:query and init param for Phrase Slop value in phrase boost query (in pf fields)
8.ps2:default phrase slop for bigram phrases (pf2)
9.ps3:default phrase slop for bigram phrases (pf3)
10.qs:query and init param for phrase Slop value in phrases explicitly included in the user's query string ( in qf fields)
11.bq:query and init param for boosting query
12.bf:query and init param for boosting functions
13.q.alt:Alternate query (expressed in Solr QuerySyntax) to use if main query (q) is empty
14.gen:query and init param for field list

二.Event

1.event
2.newSearcher
3.firstSearcher

三.Facet

1.facet:Should facet counts be calculated?
2.facet.method:What method should be used to do the faceting
3.enum:Value for FACET_METHOD param to indicate that Solr should enumerate over terms in a field to calculate the facet counts
4.fc:Value for FACET_METHOD param to indicate that Solr should enumerate over documents and count up terms by consulting an uninverted representation of the field values (such as the FieldCache used for sorting)
5.fcs:Value for FACET_METHOD param, like FACET_METHOD_fc but counts per-segment
6.facet.query:Any lucene formated queries the user would like to use for Facet Constraint Counts (multi-value)
7.facet.field:Any field whose terms the user wants to enumerate over for Facet Constraint Counts (multi-value)
8.facet.offset:The offset into the list of facets.Can be overridden on a per field basis
9.facet.limit:Numeric option indicating the maximum number of facet field counts be included in the response for each field - in descending order of count.Can be overridden on a per field basis
10.facet.mincount:Numeric option indicating the minimum number of hits before a facet should be included in the response.  Can be overridden on a per field basis
11.facet.zeros:Boolean option indicating whether facet field counts of "0" should be included in the response.  Can be overridden on a per field basis
12.facet.missing:Boolean option indicating whether the response should include a facet field count for all records which have no value for the facet field. Can be overridden on a per field basis
13.facet.pivot:Comma separated list of fields to pivot.example: author,type  (for types by author / types within author)
14.facet.mincount:Minimum number of docs that need to match to be included in the sublist default value is 1
15.facet.sort:String option: "count" causes facets to be sorted by the count, "index" results in index order
16.count
17.true
18.index
19.false
20.facet.prefix:Only return constraints of a facet field with the given prefix
21.facet.enum.cache.minDf:When faceting by enumerating the terms in a field,only use the filterCache for terms with a df >= to this parameter
22.facet.date:Any field whose terms the user wants to enumerate over for Facet Contraint Counts (multi-value)
23.facet.date.start: Date string indicating the starting point for a date facet range.Can be overriden on a per field basis
24.facet.date.end: Date string indicating the endinging point for a date facet range.Can be overriden on a per field basis
25.facet.date.gap: Date Math string indicating the interval of sub-ranges for a date facet range.Can be overriden on a per field basis
26.facet.date.hardend:Boolean indicating how counts should be computed if the range between 'start' and 'end' is not evenly divisible by 'gap'.  If this value is true, then all counts of ranges involving the 'end' point will use the exact endpoint specified -- this includes the 'between' and 'after' counts as well as the last range computed using the 'gap'.  If the value is false, then 'gap' is used to compute the effective endpoint closest to the 'end' param which results in the range between 'start' and 'end' being evenly divisible by 'gap'.The default is false.Can be overriden on a per field basis
27.facet.date.other:String indicating what "other" ranges should be computed for a date facet range (multi-value).Can be overriden on a per field basis.BEFORE AFTER BETWEEN ALL NONE
28.facet.date.include:Multivalued string indicating what rules should be applied to determine when the the ranges generated for date faceting should be inclusive or exclusive of their end points.The default value if none are specified is: [lower,upper,edge] (NOTE: This is different then FACET_RANGE_INCLUDE).Can be overriden on a per field basis
29.facet.range:Any numerical field whose terms the user wants to enumerate over Facet Contraint Counts for selected ranges
30.facet.range.start:Number indicating the starting point for a numerical range facet.Can be overriden on a per field basis
31.facet.range.end:Number indicating the ending point for a numerical range facet.Can be overriden on a per field basis
32.facet.range.gap:Number indicating the interval of sub-ranges for a numerical facet range.Can be overriden on a per field basis
33.facet.range.hardend:Boolean indicating how counts should be computed if the range between 'start' and 'end' is not evenly divisible by 'gap'.  If this value is true, then all counts of ranges involving the 'end' point will use the exact endpoint specified -- this includes the 'between' and 'after' counts as well as the last range computed using the 'gap'.  If the value is false, then 'gap' is used to compute the effective endpoint closest to the 'end' param which results in the range between 'start' and 'end' being evenly divisible by 'gap'.The default is false.Can be overriden on a per field basis
34.facet.range.other:String indicating what "other" ranges should be computed for a numerical range facet (multi-value).Can be overriden on a per field basis.BEFORE AFTER BETWEEN ALL NONE
35.facet.range.include:Multivalued string indicating what rules should be applied to determine when the the ranges generated for numeric faceting should be inclusive or exclusive of their end points.The default value if none are specified is: lower Can be overriden on a per field basis.ALL LOWER UPPER EDGE OUTER


转自:http://www.cnblogs.com/TerryLiang/archive/2012/08/30/2664487

相关问答

更多
  • 我无法通过Solr或插件配置找到这样做的方法,所以我开发了一种方法来有效地创建组构面计数,同时仍然使用CollapsingQParserPlugin。 我这样做是通过复制我将要面对的字段并确保整个组的所有方面值都在每个文档中,如下所示: "docs": [ { "id": "1", "workId": "abc", "type": "book", "facetType": [ "book", "ebook" ] }, { " ...
  • 我的申请中遇到了类似的问题。 该问题的解决方案是方面本地参数。 即如果我正在面对来自Solr techproducts示例的数据,以找出可用或不可用于库存的产品数量,我需要运行如下查询: http://localhost:8983/solr/techproducts/select?q=*%3A*&wt=json&indent=true&facet=true&facet.field=inStock 我会得到以下结果,包括来自inStock字段的所有dictinct值: ... "facet_counts": ...
  • 您的问题是要按方面值进行过滤。 一个过滤器,它只限制结果列表,但不限制相应的构面字段。 您正在寻找的是标记过滤器查询 : q=my+main+query&fq={!tag=brandTag}brand%3A"Flipkart"&facet=true&facet.field={!ex=brandTag}brand Your question is about to filter by a facet-value. A filter which does only restrict the resultlis ...
  • 这是一个已知问题,并且存在一个问题。 请点击https://issues.apache.org/jira/browse/SOLR-6329 也似乎使用minCount = 0处理过多的文档不必要,并使用太多的内存,这可能会解释崩溃的节点。 检查这个jira https://issues.apache.org/jira/browse/SOLR-11711 This is a known issue and there is a issue open for this. check here https://i ...
  • 您可以使用构面查询而不是构面范围来完成所要求的内容。 尝试这样的事情: facet.query=myDateField:[NOW-11MONTH/MONTH TO NOW-10MONTH/MONTH] facet.query=myDateField:[NOW-10MONTH/MONTH TO NOW-9MONTH/MONTH] facet.query=myDateField:[NOW-9MONTH/MONTH TO NOW-8MONTH/MONTH] ... 等等。 现在你可以完全控制任何一个方面, ...
  • 我自己找到了答案。 我应该使用More Like This处理程序,而不是使用搜索处理程序的MLT。 MLT处理程序“支持使用CommonQueryParameters进行分面,分页和过滤”(来自wiki)。 启用MLT功能的两种方法http://wiki.apache.org/solr/MoreLikeThis 更像是这个处理程序http://wiki.apache.org/solr/MoreLikeThisHandler#Examples Found the answer myself. I am su ...
  • 无法找到合适的解决方案,但猴子修补它像这样: Post.solr_search do facet(:comments_count) do row('No') { with(:comments_count).less_than 1 } row('Yes') { with(:comments_count).greater_than 0 } end case params[:comments_count] when 'No' with(:comments_coun ...
  • 我认为这不可能在solr结束。 但是你需要在客户端实现同样的目标。 当你得到json响应时,你可以通过添加'+'来修改它。 要么 您在UI前面显示构面计数的位置,您只需在显示计数之前添加“+”作为前缀。 I don't think so this possible at solr end. But you need to achieve the same thing at client side. When you get json response you modify the same by addin ...
  • 根据pysolr客户端测试中的facet示例,您需要将facet参数的值设置为“on”。 如下所示: solr = pysolr.Solr('http://localhost:8983/solr/', timeout=10)` params = { 'facet': 'on', 'facet.field': 'q_date', 'rows': '0', } results = solr.search('video', **params) According to the facet exa ...
  • 我认为你需要使用通用的setParam方法,因为它不是直接暴露的。 solrQuery.setParam(FacetParams.FACET_METHOD, FacetParams.FACET_METHOD_enum) I think you will need to use the generic setParam method since it is not exposed directly. solrQuery.setParam(FacetParams.FACET_METHOD, FacetPara ...