Fork me on GitHub
#off-topic
<
2016-06-07
>
jqmtor12:06:45

@nxqd: looking at the code you posted, the problem is not related to the library. the message you are receiving is from Elasticsearch itself.

jqmtor12:06:04

the reason for the error is that you defined the :developer/name with the default analyzer - it should be the standard analyzer if you didn’t change it - and then you are trying to update the analyzer for that field in the update mapping action. Elasticsearch does not support changing the analyzer for one field after you create it.

jqmtor12:06:31

probably this came too late, but I hope it is still useful.

jimmy12:06:35

@quimrstorres: thanks for helping. I have realized and fixed it yesterday 😛 I wonder if there is any lib to make elasticsearch mapping from datomic ( for simple case like "nested" type )

jqmtor13:06:58

what do you mean? you would like something that generated an elasticsearch mapping from a datomic schema?

jimmy13:06:51

@quimrstorres: yes. I haven't covered all the case yet but it would be nice if we have a lib to generate "nested" type for :ref type in datomic schema. Something like that

jqmtor13:06:49

yes, I don’t know such a tool, but I see some possible limitations to it. you could definitely create a basic mapping from a Datomic schema, but I think that would not work for more complex use cases. If you are using both Datomic and Elasticsearch, then I suppose you are not using Datomic full text search capabilities, meaning that your schema probably does not have all the relevant information about the fields that are used for searching on Elasticsearch.

jqmtor13:06:53

of course you could generate the best mapping possible and then enrich it with the search-specific information for your use cases, but it would still have limited use, I think.

jqmtor14:06:11

@nxqd: anyway, at least you have clojure. transforming data structures is quite easy. 😛

jimmy14:06:11

@quimrstorres: yeah, I put this on my todo list. I will give it a try when I have free time 😄