Previously I make an configset with mmseg4j tokenizer and create a core on Solr
5.4.1 under Win7. It's successfully.
Today I repeat same steps under Solr 6.0.0. When I crate collection, it return
the error message:
*************************************
ERROR: Failed to create collection 'cloud_ugna' due to:
{10.18.1.81:7574_solr=org.apache.solr.client.solrj.impl.HttpSo
lrClient$RemoteSolrException:Error from server at http://10.18.1.81:7574/solr:
Error CREATEing SolrCore 'cloud_ugna_sh
ard1_replica1': Unable to create core [cloud_ugna_shard1_replica1] Caused by:
com.chenlb.mmseg4j.solr.MMSegTokenizerFact
ory,
10.18.1.81:8983_solr=org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException:Error
from server at ht
tp://10.18.1.81:8983/solr: Error CREATEing SolrCore
'cloud_ugna_shard1_replica2': Unable to create core [cloud_ugna_sh
ard1_replica2] Caused by: com.chenlb.mmseg4j.solr.MMSegTokenizerFactory}
*************************************
The steps are as follow:
1.Ddownload mmseg4j v2.3 from here: https://github.com/chenlb/mmseg4j-solr
2.Copy two lib jar, mmseg4j-core-1.10.0-tcdic.jar and mmseg4j-solr-2.3.0.jar
into server\solr\solr-webapp\webapp\WEB-INF\lib.
3.Copy the mmseh4j-related config part from my Solr 5.4.1's config (the mmseg4j
run on there successfully) into solrconfig.xml on Solr 6.0.0 side.
4.run with bin\solr create_collection -c cloud_ugna -d
d:\solr\myconfigset\cloud_ugna -z localhost:9983 -p 8983
the part added into solrconfig.xml is:
******************************
<requestHandler name="/mmseg4j"
class="com.chenlb.mmseg4j.solr.MMseg4jHandler" >
<lst name="defaults">
<str name="dicPath">mydic</str>
<str name="check">true</str>
<str name="reload">false</str>
<str name="mode">simple</str>
</lst>
</requestHandler>
****************************
What could be the cause? Is it the version compatible problem between Solr 6
and mmseg4j v2.3?
BTW, in Solr 6.0.0, the example solconfig.xml has no <schemaFactory> tag, I
just add following line on my own:
<schemaFactory class="ClassicIndexSchemaFactory"/>
since my config on 5.4.1 is using schema.xml.
Could the problem come from this modification?
