I've been using elastic since about 2009 ... and I've always found myself
embedding elastic into our app - and configuring it programmatically.
I've always found programmatically configuring the mapping for an index to
be very clunky.
But perhaps I just havent paid close attention to the enhancements over the
years and I am now Doing It Wrong.
So, what is the best/cleanest way to configure mappings programmatically?
I've been using elastic since about 2009 ... and I've always found myself
embedding elastic into our app - and configuring it programmatically.
I've always found programmatically configuring the mapping for an index to
be very clunky.
But perhaps I just havent paid close attention to the enhancements over
the years and I am now Doing It Wrong.
So, what is the best/cleanest way to configure mappings programmatically?
I am primarily indexing structured data - so typically, there are many
fields.
In my experience mapping changes quite a bit over time - as requirements
evolve - or as you discover the mistakes you have made.
Your mapping necessarily refers to fields - as does your code. So, keeping
those two in sync over time sucks.
On Tue, May 26, 2015 at 10:07 PM, mooky <nick.mi...@gmail.com
<javascript:>> wrote:
I've been using elastic since about 2009 ... and I've always found myself
embedding elastic into our app - and configuring it programmatically.
I've always found programmatically configuring the mapping for an index
to be very clunky.
But perhaps I just havent paid close attention to the enhancements over
the years and I am now Doing It Wrong.
So, what is the best/cleanest way to configure mappings programmatically?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.