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

[Yoann Rodière]

  Branch: refs/heads/5.6
  Home:   https://github.com/hibernate/hibernate-search
  Commit: 30f6cf3fc27a3820c8a83ecb4b8e021bd346bfaf
      https://github.com/hibernate/hibernate-search/commit/30f6cf3fc27a3820c8a83ecb4b8e021bd346bfaf
  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: b1006828d34918767df98097c45f676c3ec2582b
      https://github.com/hibernate/hibernate-search/commit/b1006828d34918767df98097c45f676c3ec2582b
  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: def0438f25fc13ca64ab1f2d9f2d2fc246794410
      https://github.com/hibernate/hibernate-search/commit/def0438f25fc13ca64ab1f2d9f2d2fc246794410
  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: d0bc1f1998c8fd43e7df23dd5036e59bac2a5e4f
      https://github.com/hibernate/hibernate-search/commit/d0bc1f1998c8fd43e7df23dd5036e59bac2a5e4f
  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/8e999821b409...d0bc1f1998c8