Permalink
Commits on Feb 20, 2017
  1. Add a missing @Override

    yrodiere committed with Sanne Feb 13, 2017
Commits on Feb 17, 2017
Commits on Feb 16, 2017
  1. HSEARCH-2590 Fix an over-allocation of memory when paging on Elastics…

    …earch
    
    getTotal() returns the total number of hits, not the number of returned
    hits.
    yrodiere committed Feb 16, 2017
Commits on Feb 15, 2017
Commits on Feb 14, 2017
  1. HSEARCH-2418 Always make analyzers from analyzer provider SPIs available

    ... through the SearchFactory, even when not used in the mapping.
    
    This mirror the behaviors of
    ConfigContext.initAnalyzerRegistries(IndexManagerHolder),
    which considers that even when @AnalyzerDefs are unused, Lucene
    analyzers should be created.
    
    Also, this behavior is a requirement to solve HSEARCH-2534.
    yrodiere committed Feb 7, 2017
  2. HSEARCH-2418 Introduce the ElasticsearchAnalysisDefinitionProvider SPI

    This allows to define analyzers independently from the mapping.
    yrodiere committed Feb 6, 2017
  3. HSEARCH-2418 Translate ES analyzer definition translation sooner, whe…

    …n building analyzer references
    
    ... so that we can have different analyzer definition sources, which
    would not require any translation (see next commits).
    yrodiere committed Feb 3, 2017
  4. HSEARCH-2418 Move analyzer definition translation code to a specific …

    …package
    
    This will make room for classes with a different purpose in the
    "settings.impl" package.
    yrodiere committed Feb 2, 2017
  5. HSEARCH-2418 Use NamedElasticsearchAnalyzerReference for the default …

    …and passthrough analyzers
    
    This makes perfect sense, because NamedElasticsearchAnalyzerReferences can
    actually hold undefined analyzers (i.e. analyzers for which only the
    name, but not the definition, is known).
    yrodiere committed Feb 3, 2017
  6. HSEARCH-2418 Make ElasticsearchAnalyzer responsible for registering a…

    …nalyzer definitions in the settings
    
    This will allow us to have some analyzers hold a reference to
    an ES-specific analyzer definition, so that we can have analyzers
    definition coming from another source than just @AnalyzerDef
    annotations.
    
    There are a few reasons to do that, the most important being that the
    @AnalyzerDef annotation does not really fit the ES model, where one
    tokenizer definition (for instance) can be referenced from multiple
    analyzer definitions.
    
    One side-effect of this change is the translation from Lucene class
    providing from @Analyzer annotations to the Elasticsearch name must now
    be done when initializing references, instead of when building the ES
    schema. This is inconsistent with the translation of @AnalyzerDef
    annotations, which occurs when building the ES schema, but we'll fix
    this inconsistency in the next commits.
    yrodiere committed Feb 2, 2017
  7. HSEARCH-2418 Remove a useless analyzer de-duplication mechanism in an…

    …alyzer strategies
    
    Rationale: we already make sure that we only have one reference for any
    given name, so we never have two references sharing the same name.
    Thus this mechanism is never used.
    yrodiere committed Feb 6, 2017
  8. HSEARCH-2418 Introduce the LuceneAnalyzerDefinitionProvider SPI

    This allows to define analyzers independently from the mapping.
    yrodiere committed Feb 3, 2017
  9. Fix incomplete javadoc

    yrodiere committed Feb 2, 2017
  10. HSEARCH-2577 Separate the namespaces for named Elasticsearch analyzer…

    …s and named Lucene analyzers
    yrodiere committed Jan 3, 2017
Commits on Feb 13, 2017
Commits on Feb 10, 2017
  1. HSEARCH-2453 Clarify some ES configuration options have to be prefixe…

    …d with "hibernate.search.default."
    yrodiere committed Feb 10, 2017
  2. HSEARCH-2453 Add dedicated configuration options for Elasticsearch au…

    …thentication
    
    Authentication was already possible, but a bit painful, since you had to
    include the username and password in the host URLs. Which meant
    repeating it over and over again when using multiple URLs, and also
    meant you had to URL-encode the username and password yourself.
    
    Tests are not included, because it's a pain to automate the setup of
    authentication on the ES instance used for tests. Also, I'm quite sure
    we can't do it with an embedded version of ES, and I don't even know if
    the licensing terms would allow it (the Shield plugin is subject to a
    commercial license).
    
    To test manually, see:
    https://www.elastic.co/blog/getting-started-with-elasticsearch-ssl-native-authentication
    yrodiere committed Feb 9, 2017
Commits on Feb 9, 2017
  1. HSEARCH-2561 Test overriding of query metadata (sortable fields) duri…

    …ng query execution
    yrodiere committed with Sanne Jan 31, 2017