[hibernate-commits] [hibernate/hibernate-search] 0fbbf2: HSEARCH-3537 Document the default value of maxFace...

Yoann Rodière noreply at github.com
Wed May 15 02:57:35 EDT 2019


  Branch: refs/heads/5.11
  Home:   https://github.com/hibernate/hibernate-search
  Commit: 0fbbf2172b0471aa90ef7b42787812ff9924809b
      https://github.com/hibernate/hibernate-search/commit/0fbbf2172b0471aa90ef7b42787812ff9924809b
  Author: Yoann Rodière <yoann at hibernate.org>
  Date:   2019-05-15 (Wed, 15 May 2019)

  Changed paths:
    M documentation/src/main/asciidoc/query.asciidoc
    M engine/src/main/java/org/hibernate/search/query/dsl/FacetParameterContext.java
    M engine/src/main/java/org/hibernate/search/query/engine/impl/QueryHits.java
    M engine/src/main/java/org/hibernate/search/query/facet/FacetingRequest.java

  Log Message:
  -----------
  HSEARCH-3537 Document the default value of maxFacetCount

This is far from ideal, because a default value of 100 seems rather
arbitrary, but it's been that way since 5.3.0.Beta1 and I don't see
myself changing it in a micro.


  Commit: 972ccfa74b06d3172af2abfed1e1cc4bfeaead38
      https://github.com/hibernate/hibernate-search/commit/972ccfa74b06d3172af2abfed1e1cc4bfeaead38
  Author: Yoann Rodière <yoann at hibernate.org>
  Date:   2019-05-15 (Wed, 15 May 2019)

  Changed paths:
    M elasticsearch/src/main/java/org/hibernate/search/elasticsearch/impl/ToElasticsearch.java

  Log Message:
  -----------
  HSEARCH-3537 Properly detect negative values when translating faceting requests to Elasticsearch

Not changing the behavior even though it's probably performing very
badly, because we'll release this in a micro.


  Commit: c804167c2f7c447debd5562aa56c323fe84ab70b
      https://github.com/hibernate/hibernate-search/commit/c804167c2f7c447debd5562aa56c323fe84ab70b
  Author: Yoann Rodière <yoann at hibernate.org>
  Date:   2019-05-15 (Wed, 15 May 2019)

  Changed paths:
    A engine/src/test/java/org/hibernate/search/test/bridge/DuplicateFieldTest.java

  Log Message:
  -----------
  HSEARCH-3562 Add a very basic test for detectiong of incompatible fields with the same name

The detection is rather primitive, as it only detects fields with the
same name but a different "index" setting, so I'll stop here and won't
look for bugs: I know there are a few, and it won't be relevant anymore
in Search 6.


  Commit: 607de0c510a1f4a9066ba5854cc088a86230e3b3
      https://github.com/hibernate/hibernate-search/commit/607de0c510a1f4a9066ba5854cc088a86230e3b3
  Author: Yoann Rodière <yoann at hibernate.org>
  Date:   2019-05-15 (Wed, 15 May 2019)

  Changed paths:
    M engine/src/main/java/org/hibernate/search/engine/metadata/impl/AnnotationMetadataProvider.java
    M engine/src/main/java/org/hibernate/search/engine/metadata/impl/DocumentFieldMetadata.java
    M engine/src/main/java/org/hibernate/search/engine/metadata/impl/TypeMetadata.java
    M engine/src/main/java/org/hibernate/search/engine/spi/DocumentBuilderIndexedEntity.java
    M engine/src/test/java/org/hibernate/search/test/bridge/DuplicateFieldTest.java
    M engine/src/test/java/org/hibernate/search/test/bridge/builtin/TikaBridgeTest.java

  Log Message:
  -----------
  HSEARCH-3562 Fix AssertionFailure when trying to report a duplicate field declared by a class bridge or class-level @Spatial


Compare: https://github.com/hibernate/hibernate-search/compare/c4aa67f6d7c3...607de0c510a1



More information about the hibernate-commits mailing list