Skip to content

Conversation

@moshaad7
Copy link
Contributor

@moshaad7 moshaad7 commented Aug 12, 2024

  • Update Analyzer interface to

    • handle errors produced during analysis.
    • use "any" as return type of Analysis (generating values other than tokenStream, like embedding vectors)
  • Update the analyzers registry to allow runtime registration/removal

NOTE:
This will break backward compatibility for bleve users who register their own analyzer implementations.

@moshaad7 moshaad7 changed the title Introduce AnalyzerV2 and Ability to Register Analyzers at Runtime MB-56946: Introduce AnalyzerV2 and runtime analyzers registry Aug 12, 2024
@abhinavdangeti abhinavdangeti added this to the v2.5.0 milestone Sep 5, 2024
@moshaad7 moshaad7 changed the title MB-56946: Introduce AnalyzerV2 and runtime analyzers registry MB-56946: Handle analysis errors and make analyzer registry concurrent safe Sep 6, 2024
@moshaad7 moshaad7 changed the title MB-56946: Handle analysis errors and make analyzer registry concurrent safe MB-56946: update analyzer interface and registry Sep 6, 2024
+ Update Analyzer interface to
   + handle errors produced during analysis.
   + use "any" as return type of Analysis (generating values other than tokenStream, like embedding vectors)
+ Update the analyzers registry to allow runtime registration/removal

+ This is to let bleve users register/deregister analyzers at runtime and use it in their index mappings

NOTE:
This will break backward compatibility for bleve customers registering their own analyzer implementations.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants