Github user osma commented on the issue:
https://github.com/apache/jena/pull/246
Thanks for the contribution!
I think this will take a while to digest. I'm currently on a business trip
to California and don't have time to look at this very closely, but I will do
so when I have the chance.
I've wanted to have something like this in jena-text some time ago, when
there was no support for any other analyzers than StandardAnalyzer. However,
instead of implementing a generic configuration system like this, I ended up
adding support for just the easiest analyzers (e.g. SimpleAnalyzer) plus a
couple I had a special need for. Others have so far done the same (e.g.
MultilingualAnalyzer by Alexis Miara).
It's very good to have tests and documentation included in the PR. I'm
still a bit worried about the usability aspect of this whole new configuration
language. The jena-text documentation is already difficult to understand, and
I've had to explain how to configure it many times to people who are new to it.
Adding a new layer that allows specifying any combination of analyzers with
specific parameters is very powerful, but it also adds a whole new meta-layer
over an already complex configuration system.
@xristy Could you elaborate a bit on why you ended up doing this (including
what is the original problem you were solving), and whether you considered any
alternative approaches?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
