Please refer to
www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-core-types.html
--
Itamar Syn-Hershko
http://code972.com | @synhershko https://twitter.com/synhershko
Freelance Developer Consultant
Lucene.NET committer and PMC member
On Mon, Feb 9, 2015 at 12:24 PM,
yes, you are using string properties on a date mapping field
--
Itamar Syn-Hershko
http://code972.com | @synhershko https://twitter.com/synhershko
Freelance Developer Consultant
Lucene.NET committer and PMC member
On Mon, Feb 9, 2015 at 12:23 PM, Paul Kavanagh pkavan...@shopkeep.com
wrote:
I
I think you have something there. I have come up with this:
curl -XPUT localhost:9200/_template/template_1 -d '
{
template : logstash-*,
order : 0,
settings : {
number_of_shards : 15
},
mappings : {
dynamic_templates:[
{apiservice_logstash:{
You mean something like dynamic templates?
http://code972.com/blog/2015/02/81-elasticsearch-one-tip-a-day-using-dynamic-templates-to-avoid-rigorous-mappings
--
Itamar Syn-Hershko
http://code972.com | @synhershko https://twitter.com/synhershko
Freelance Developer Consultant
Lucene.NET committer
As we create a new index everyday, we're not concerned with retro-applying
the fix to existing indices. So it seems Templates are the way to go here.
On Friday, February 6, 2015 at 2:52:49 PM UTC, John Smith wrote:
A template wont help you here. I mean it's good to use and you should use
I think you have something there. I have come up with this:
curl -XPUT localhost:9200/_template/template_1 -d '
{
template : logstash-*,
order : 0,
settings : {
number_of_shards : 15
},
mappings : {
dynamic_templates:[
{apiservice_logstash:{
A template wont help you here. I mean it's good to use and you should use
them. But once the schema is defined you can't change it. This is no
different then any database.
Your best bet here is to do a bit of data cleansing/normalizing.
If you know that the field is date field and sometimes
