title: How to resolve ELK Stack Mapping Conflict for apache access combined logs
body: <p>I am trying to learn ELK stack where i have staretd with indexing apache   access logs, i have Logstash 1.4.2,Elasticseach 1.5.1 and kiabna 4.0.2 for windows. Following are my configurtion files. for <strong>mapping at elasticsearch</strong> i have used </p>
  
  <pre><code>curl -XPOST localhost:9200/apache_access?ignore_conflicts=true -d '{  
      "settings" : {  
            "number_of_shards" : 1  
      },  
      "mappings" : {  
          "apache" : {  
  
  
  
   "properties" : {
  
  "timestamp" : {"type":"date", "format" : "DD/MMM/YYYY:HH:mm:ss" },             
  "bytes": {"type": "long"},   
  "response":{ "type":"long"},  
  "clientip":{ "type": "ip"},  
  "geoip" : { "type" : "geo_point"}  
  }  
          }  
      }  
  }' 
  </code></pre>
  
  <p>and my <strong>logstash-apache.conf</strong> is     </p>
  
  <pre><code>input   {  
    file {
      path =&gt; "D:\data\access_log1.log"  
      start_position =&gt; beginning  
      }
  }
  
  filter {
  
  
      grok {
        match =&gt; { "message" =&gt; "%{COMBINEDAPACHELOG}" }
      }
      geoip{
      source =&gt; "clientip"
      target =&gt; "geoip"
      }
  
    date {
      match =&gt; [ "timestamp" , "dd/MMM/yyyy:HH:mm:ss Z" ,"ISO8601"]
    }
  }
  
  output {  
    elasticsearch {  
              host =&gt; "localhost"  
              protocol =&gt; http  
              index =&gt; "apache_access"    
      }  
        stdout { codec =&gt; rubydebug }  
  }
  </code></pre>
  
  <p>what i am facing is , for the fields for which i have applied mapping in elasticsearch i.e bytes,response,clientip i am getting conflict. i understand what is happening, as it says these fields have string and long both as field type. but i dont understand why it is happening as i have  applied mapping. i would also like to resolve this issue. any help is appreciated.</p>