On 8/18/2018 11:03 PM, Zahra Aminolroaya wrote:
Thanks Shawn. For Solr mode I should include all dependencies in lib, so I
thought for Solr Cloud mode I should include the dependencies too.
Even for standalone mode, you don't want those dependency jars in the
lib folder. The same problems can happen no matter what mode Solr is
running in.
Caused by: java.lang.RuntimeException: schema fieldtype
text_general(org.apache.solr.schema.TextField) invalid
arguments:{runtimeLib=true}
This is a different error than the one in your second message. That one
says it can't find the 'norm.myNormalizerFilterFactory' class.
I have no idea what needs to go into configoverlay.json. I've never
actually used the config API. So I do not know whether your config
there is right or not.
The filter class that you're using strikes me as a little odd. You've
got norm.myNormalizerFilterFactory ... if the package line in the .java
file is just "norm" then that part would be OK. If it's something else,
then you need to use the entire package name. The class name
myNormalizerFilterFactory doesn't follow normal Java convention and
start with an uppercase letter. Is this the actual class name in the
.java file? If you share a full file listing from the jar (which is a
zipfile) then I can tell you what your class name should be.
The classes typically used in a schema do start with "solr." which might
seem like an incomplete package name is acceptablwe. Solr handles this
special prefix by checking a number of different packages for the class.
Thanks,
Shawn
