Coreseek:indexer crashed mystery

Brother Ho Let me coreseek the index again this time, the company name should be indexed because of a small change in demand. In the profile of the Add face sql_field_string: String field.

This property is particularly useful because it is not only a filter feature, but also a full-text search, and you can return to the original text message.

Then write good files, index, build index when there is such a strange problem oops, indexer crashed! really when is inexplicable.

Someone has found this reason when you meet these three conditions at the same time

1. Include horizontal lines in the original document
2.charset_type=zh_cn.utf-8
3. Use your own thesaurus to define your own thesaurus with no problem with your own library

This problem will arise.

About the first one. I found my document and thesaurus myself and removed the line. The result is still an error.

As for the second one, I changed the encoding format to UTF8. However, there is obviously a problem with the indexing results.

About the third one. No problem.

Finally, I still use the third one, the thesaurus into the original word library.

In the end, whether it is another time to coreseek or reproduce the thesaurus, are the same problem, and the index is not a problem, but the back of the problem.

In my opinion, it should be a special character in the database document that caused the problem or the problem of building a dictionary.

As a result of the original dictionary, there was a error!! error!! This problem, but always can not find why error.

Perhaps the solution to the problem is this, but there is no good solution.

Copyright notice: This article blog original articles, blogs, without consent, may not be reproduced.

Coreseek:indexer crashed mystery