I have a feeling the issue is the application has a embedded version of
elastic search. Is there a default path that elastic search will look for a
configuration? Or a java variable I can add that will force it to look in a
specific path?
On Thu, Dec 19, 2013 at 3:04 PM, Lee Hinman <matthew.hin...@gmail.com>wrote:
> On Wednesday, December 18, 2013 12:09:41 PM UTC-7, Joshua Corb wrote:
>>
>> We are running into an issue where we are getting mapping issues. We are
>> have tried on both Ubuntu and OSX. We are using java 1.7. Attached is our
>> node configuration, and below is the error we are getting.
>>
>> 11:12:47,856 WARN [org.elasticsearch.indices.cluster]
>> (elasticsearch[Nemesis][clusterService#updateTask][T#1]) [Nemesis]
>> [need] failed to add mapping [need], source [{"need":{"properties":{"
>> defaultTextValue":{"type":"string"},"description":{"type"
>> :"string"},"endDate":{"type":"string"},"id":{"type":"string"
>> },"imageURL":{"type":"string"},"location":{"type":"geo_
>> point"},"mainCategory":{"type":"string","store":true,"index_
>> analyzer":"keyword"},"postDate":{"type":"string"},"
>> subCategory":{"type":"string","store":true,"index_analyzer":
>> "keyword"},"tags":{"type":"string","store":true,"index_
>> analyzer":"keyword"},"title":{"type":"multi_field","fields":
>> {"title":{"type":"string"},"title.autocomplete":{"type":"
>> string","store":true,"index_analyzer":"autocomplete","search_analyzer":"
>> autocomplete_search","include_in_all":false},"title.
>> untouched":{"type":"string","index":"not_analyzed","omit_
>> norms":true,"index_options":"docs","include_in_all":false}}
>> },"user":{"type":"string","store":true,"index_analyzer":"
>> keyword"},"version":{"type":"long"}}}}]:
>> org.elasticsearch.index.mapper.MapperParsingException:
>> Analyzer [autocomplete] not found for field [title.autocomplete]
>> at org.elasticsearch.index.mapper.core.TypeParsers.
>> parseField(TypeParsers.java:107) [elasticsearch-0.90.7.jar:]
>> at org.elasticsearch.index.mapper.core.StringFieldMapper$
>> TypeParser.parse(StringFieldMapper.java:150) [elasticsearch-0.90.7.jar:]
>> at org.elasticsearch.index.mapper.multifield.
>> MultiFieldMapper$TypeParser.parse(MultiFieldMapper.java:130)
>> [elasticsearch-0.90.7.jar:]
>> at org.elasticsearch.index.mapper.object.ObjectMapper$
>> TypeParser.parseProperties(ObjectMapper.java:263)
>> [elasticsearch-0.90.7.jar:]
>> at org.elasticsearch.index.mapper.object.ObjectMapper$
>> TypeParser.parse(ObjectMapper.java:219) [elasticsearch-0.90.7.jar:]
>> at org.elasticsearch.index.mapper.DocumentMapperParser.
>> parse(DocumentMapperParser.java:176) [elasticsearch-0.90.7.jar:]
>> at
>> org.elasticsearch.index.mapper.MapperService.parse(MapperService.java:314)
>> [elasticsearch-0.90.7.jar:]
>> at
>> org.elasticsearch.index.mapper.MapperService.merge(MapperService.java:193)
>> [elasticsearch-0.90.7.jar:]
>> at org.elasticsearch.indices.cluster.IndicesClusterStateService.
>> processMapping(IndicesClusterStateService.java:417)
>> [elasticsearch-0.90.7.jar:]
>> at org.elasticsearch.indices.cluster.IndicesClusterStateService.
>> applyMappings(IndicesClusterStateService.java:381)
>> [elasticsearch-0.90.7.jar:]
>> at org.elasticsearch.indices.cluster.IndicesClusterStateService.
>> clusterChanged(IndicesClusterStateService.java:179)
>> [elasticsearch-0.90.7.jar:]
>> at org.elasticsearch.cluster.service.InternalClusterService$
>> UpdateTask.run(InternalClusterService.java:414)
>> [elasticsearch-0.90.7.jar:]
>> at org.elasticsearch.common.util.concurrent.
>> PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(
>> PrioritizedEsThreadPoolExecutor.java:135) [elasticsearch-0.90.7.jar:]
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>> [rt.jar:1.7.0_45]
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> [rt.jar:1.7.0_45]
>> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
>>
>>
> Hi Joshua,
>
> You have an issue in your elasticsearch.yml file, instead of:
>
>
> index.analysis.analyzer.autocomplete:
> type: custom
> tokenizer: whitespace
> filter: lowercase
>
>
> You need to put the filter into an array (because it's a list of filters
> to be applied), so it would look like so:
>
> index.analysis.analyzer.autocomplete:
> type: custom
> tokenizer: whitespace
> filter: [lowercase]
>
> Using your configuration and making this change to all the custom
> analyzers, I was able to create an index and analyze text with the
> "autocomplete" analyzer.
>
> ;; Lee Hinman
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "elasticsearch" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/elasticsearch/8oB1lM8sUHg/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> elasticsearch+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/elasticsearch/3713dcf7-0954-4996-bace-129bcefc2633%40googlegroups.com
> .
>
> For more options, visit https://groups.google.com/groups/opt_out.
>
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAG%2BZfhDPNHRaoFc%2BatT5BNRz7BSDbboeGW1h8zSYPpi_MrAFmQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
