[
https://issues.jboss.org/browse/ISPN-9433?page=com.atlassian.jira.plugin....
]
Adrian Nistor commented on ISPN-9433:
-------------------------------------
[~gustavonalle] Tthe @Analyzer (pseudo)annotation in protobuf can only take an analyzer
definition name and cannot be used to define an analyzer on the spot by composing
filters/tokenizers. Not sure if that's doable with hibernate-search's annotations,
but certainly not possible with protobuf. So I'm not sure what you mean by "..and
last but not least, analyzers can be defined at protobuf mapping level, by composing
filters/tokenizers". The definition can only be done in the
ProgrammaticSearchProvider while the *.proto file can only reference this definition by
its name.
Add test for external analyzers
-------------------------------
Key: ISPN-9433
URL:
https://issues.jboss.org/browse/ISPN-9433
Project: Infinispan
Issue Type: Task
Components: Remote Querying, Test Suite - Server
Reporter: Gustavo Fernandes
Assignee: Gustavo Fernandes
The test need to verify that it's possible to deploy full fledged analyzers through
the server's extensions mechanism, namely the ProgrammaticSearchProvider and the cache
manager's module extensions.
Also it should test that Lucene analyzers can be defined, and last but not least,
analyzers can be defined at protobuf mapping level, by composing filters/tokenizers
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)