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

[Yoann Rodière]

  Branch: refs/heads/5.8
  Home:   https://github.com/hibernate/hibernate-search
  Commit: fb82ea91f6a016bf89fbee14307f84175673c37e
      https://github.com/hibernate/hibernate-search/commit/fb82ea91f6a016bf89fbee14307f84175673c37e
  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: 8055fe889a9be08421331663d8821de101ac040b
      https://github.com/hibernate/hibernate-search/commit/8055fe889a9be08421331663d8821de101ac040b
  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: 82500f6a50f676ec34500e3b279a0655c2f0f50e
      https://github.com/hibernate/hibernate-search/commit/82500f6a50f676ec34500e3b279a0655c2f0f50e
  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: 24c878a558fe1844a7114ebb48895b24fb015817
      https://github.com/hibernate/hibernate-search/commit/24c878a558fe1844a7114ebb48895b24fb015817
  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/03e56b25c116...24c878a558fe