Chris I will install Elastic 1.7 and try again!! It should be on the wiki or the bugzilla issue that tracks the elasticsearch development. Thank a lot for the quick response! On Wed, Sep 28, 2016 at 5:43 PM, Chris Cormack <chrisc@catalyst.net.nz> wrote:
Hi Rodrigo
ElasticSearch in Koha currently only works with Elastic 1.7 We are working on upgrading it to working the latest version but there were some non backward compatible changes. That is what you are bumping into
Support in Koha is still experimental, but it once we upgrade it should be more solid.
You could try installing 1.7 and seeing how you go
Chris
Hi,
I have installed Elasticsearch after giving up on Zebra. I have follow
wiki: https://wiki.koha-community.org/wiki/Elasticsearch# Install_elasticsearch and installed latest Elasticsearch through the official repository.
My installed version is: curl -XGET 'localhost:9200' { "name" : "Her", "cluster_name" : "elasticsearch", "cluster_uuid" : "yuU4XtZwT1WtK1SH-3Xofw", "version" : { "number" : "2.4.1", "build_hash" : "c67dc32e24162035d18d6fe1e952c4cbcbe79d16", "build_timestamp" : "2016-09-27T18:57:55Z", "build_snapshot" : false, "lucene_version" : "5.5.2" }, "tagline" : "You Know, for Search" }
I have run the script perl misc/search_tools/rebuild_elastic_search.pl -v -d like the documentation says and I have this error: Failed to parse mapping [data]: analyzer on field [Local-number] must be set when search_analyzer is set
The log on the elasticsearch.log is
[2016-09-28 20:27:55,272][DEBUG][action.admin.indices.create] [Her] [koha_dev_biblios] failed to create MapperParsingException[Failed to parse mapping [data]: analyzer on field [Local-number] must be set when search_analyzer is set]; nested: MapperParsingException[analyzer on field [Local-number] must be set when search_analyzer is set]; at org.elasticsearch.index.mapper.MapperService.merge (MapperService.java:291) at org.elasticsearch.cluster.metadata.MetaDataCreateIndexService$1.execute (MetaDataCreateIndexService.java:317) at org.elasticsearch.cluster.ClusterStateUpdateTask.execute (ClusterStateUpdateTask.java:45) at org.elasticsearch.cluster.service.InternalClusterService. runTasksForExecutor (InternalClusterService.java:468) at org.elasticsearch.cluster.service.InternalClusterService$UpdateTask.run (InternalClusterService.java:772) at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecuto r$TieBreakingPrioritizedRunnable.runAndClean (PrioritizedEsThreadPoolExecutor.java:231) at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecuto r$TieBreakingPrioritizedRunnable.run (PrioritizedEsThreadPoolExecutor.java:194) at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: MapperParsingException[analyzer on field [Local-number] must be set when search_analyzer is set] at org.elasticsearch.index.mapper.core.TypeParsers.
(TypeParsers.java:234) at org.elasticsearch.index.mapper.core.TypeParsers.
(TypeParsers.java:250) at org.elasticsearch.index.mapper.core.StringFieldMapper$TypeParser.parse (StringFieldMapper.java:165) at org.elasticsearch.index.mapper.object.ObjectMapper$ TypeParser.parseProperties (ObjectMapper.java:309) at org.elasticsearch.index.mapper.object.ObjectMapper$TypeParser.
* Rodrigo Santellan (rsantellan@gmail.com) wrote: the the parseAnalyzersAndTermVectors parseTextField parseObjectOrDocumentTypeProperties
(ObjectMapper.java:222) at org.elasticsearch.index.mapper.object.RootObjectMapper$TypeParser.parse (RootObjectMapper.java:139) at org.elasticsearch.index.mapper.DocumentMapperParser.parse (DocumentMapperParser.java:118) at org.elasticsearch.index.mapper.DocumentMapperParser.parse (DocumentMapperParser.java:99) at org.elasticsearch.index.mapper.MapperService.parse (MapperService.java:549) at org.elasticsearch.index.mapper.MapperService.merge (MapperService.java:319) at org.elasticsearch.index.mapper.MapperService.merge (MapperService.java:289) ... 9 more
I'm again at a loss, I believe the problem is on the method: get_elasticsearch_mappings in Koha::ElasticSearch but I don't know how to follow it.!
Regards and thank for any help!!
Rodrigo
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
-- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand