I was wondering if aliasing was supported for tokenizers and
filters ?
If not is there any plan to support it ?
The idea is that my automated annotation based tool automagically
creates analyzers, tokenizers and filter definitions.
If it encounters a definition that was previously sent to server it
tries to create an alias for it rather than redefining the exact same
analyzer.
That works fine for analyzers but it seems tokenizers and filters dont
have that feature.
Aliases, as you noted, are only supported for analyzers, not for tokenizers
or token filters...
On Wed, Oct 26, 2011 at 11:10 AM, Alexandre azlist1@gmail.com wrote:
I was wondering if aliasing was supported for tokenizers and
filters ?
If not is there any plan to support it ?
The idea is that my automated annotation based tool automagically
creates analyzers, tokenizers and filter definitions.
If it encounters a definition that was previously sent to server it
tries to create an alias for it rather than redefining the exact same
analyzer.
That works fine for analyzers but it seems tokenizers and filters dont
have that feature.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.