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

Yoann Rodière noreply at github.com
Wed May 15 04:06:33 EDT 2019


  Branch: refs/heads/HSEARCH-3537-5.7
  Home:   https://github.com/hibernate/hibernate-search
  Commit: 6aa6cdc0fce681f504a1222a1695a420c26843a9
      https://github.com/hibernate/hibernate-search/commit/6aa6cdc0fce681f504a1222a1695a420c26843a9
  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: a7537cd8b862d745eab7b58d3ca751ee7aafb208
      https://github.com/hibernate/hibernate-search/commit/a7537cd8b862d745eab7b58d3ca751ee7aafb208
  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: ab2fbe29ebab868f232c5a1076fb760a4e111ca8
      https://github.com/hibernate/hibernate-search/commit/ab2fbe29ebab868f232c5a1076fb760a4e111ca8
  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: 85bb1fbff081d26152ea16cf7150a846b4442bfd
      https://github.com/hibernate/hibernate-search/commit/85bb1fbff081d26152ea16cf7150a846b4442bfd
  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/6aa6cdc0fce6%5E...85bb1fbff081



More information about the hibernate-commits mailing list