<p dir="auto">I am using the logstash 1.3.2 RPM found in this repository:<br>
<a href="http://packages.elasticsearch.org/logstash/1.3/centos" rel="nofollow">http://packages.elasticsearch.org/logstash/1.3/centos</a></p>
<p dir="auto">I have set CONF_DIR to /etc/logstash/conf.d/*<em>/</em>.conf.<br>
The asterisks seem to be messing with the regular expression used by pgrep to find the PID of the process that was started.</p>
<p dir="auto">The process starts fine, but then the process cannot be killed when using the stop command on the init script. When issuing a restart, there will be duplicate processes.<br>
Escaping the asterisks for pgrep allowed me to get the pid.<br>
Either the asterisks need to be escaped or a different value besides the full ARGS list should be used to find the PID.</p>
<p dir="auto">Also, in a somewhat related issue. It seems that in the init script for logstash, reads the ${DAEMON} variable in a few places, but it is never set. I think ${DAEMON} should probably be the ${JAVA} variable.</p>
<p dir="auto">HI,<br>
I am working with Elasticsearch 2.1.0.<br>
I have a requirement to specify the schema for my documents.<br>
So i used the ElasticSearch Mapping functionality like this:</p>
<p dir="auto">curl -XPUT '<a href="http://localhost:9200/customer/external/_mapping" rel="nofollow">http://localhost:9200/customer/external/_mapping</a>' -d ' { "external" : { "properties" : { "example" : { "properties" : { "custom_property" : { "type" : "byte" } } } } } } '</p>
<p dir="auto">It gets reflected in the schema mapping as well:</p>
<div class="highlight highlight-source-json notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="{
  &quot;customer&quot; : {
    &quot;mappings&quot; : {
      &quot;external&quot; : {
        &quot;properties&quot; : {
          &quot;first&quot; : {
            &quot;type&quot; : &quot;long&quot;
          },
          &quot;example&quot; : {
            &quot;properties&quot; : {
              &quot;custom_property&quot; : {
                &quot;type&quot; : &quot;byte&quot;
              },
              &quot;last&quot; : {
                &quot;type&quot; : &quot;long&quot;
              }
            }
          }
        }
      }
    }
  }
}"><pre class="notranslate">{
  <span class="pl-ent">"customer"</span> : {
    <span class="pl-ent">"mappings"</span> : {
      <span class="pl-ent">"external"</span> : {
        <span class="pl-ent">"properties"</span> : {
          <span class="pl-ent">"first"</span> : {
            <span class="pl-ent">"type"</span> : <span class="pl-s"><span class="pl-pds">"</span>long<span class="pl-pds">"</span></span>
          },
          <span class="pl-ent">"example"</span> : {
            <span class="pl-ent">"properties"</span> : {
              <span class="pl-ent">"custom_property"</span> : {
                <span class="pl-ent">"type"</span> : <span class="pl-s"><span class="pl-pds">"</span>byte<span class="pl-pds">"</span></span>
              },
              <span class="pl-ent">"last"</span> : {
                <span class="pl-ent">"type"</span> : <span class="pl-s"><span class="pl-pds">"</span>long<span class="pl-pds">"</span></span>
              }
            }
          }
        }
      }
    }
  }
}</pre></div>
<p dir="auto">I then added the value for this field like this:</p>
<p dir="auto">curl -XPUT 'localhost:9200/customer/external/1?pretty' -d '{"example": {"custom_property": 12345}}'</p>
<p dir="auto">And to my surprise it was saved successfully. Here is the output :</p>
<div class="highlight highlight-source-json notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="{
  &quot;_index&quot; : &quot;customer&quot;,
  &quot;_type&quot; : &quot;external&quot;,
  &quot;_id&quot; : &quot;1&quot;,
  &quot;_version&quot; : 3,
  &quot;found&quot; : true,
  &quot;_source&quot;:{&quot;example&quot;: {&quot;custom_property&quot;: 12345}}
}"><pre class="notranslate">{
  <span class="pl-ent">"_index"</span> : <span class="pl-s"><span class="pl-pds">"</span>customer<span class="pl-pds">"</span></span>,
  <span class="pl-ent">"_type"</span> : <span class="pl-s"><span class="pl-pds">"</span>external<span class="pl-pds">"</span></span>,
  <span class="pl-ent">"_id"</span> : <span class="pl-s"><span class="pl-pds">"</span>1<span class="pl-pds">"</span></span>,
  <span class="pl-ent">"_version"</span> : <span class="pl-c1">3</span>,
  <span class="pl-ent">"found"</span> : <span class="pl-c1">true</span>,
  <span class="pl-ent">"_source"</span>:{<span class="pl-ent">"example"</span>: {<span class="pl-ent">"custom_property"</span>: <span class="pl-c1">12345</span>}}
}</pre></div>
<p dir="auto">I did some more investigation and found that the value is treated as short and not as byte.</p>
<p dir="auto">There is a similar issue with float dataType as well. Can someone explain what may be causing this and how can this be rectified?</p>
<p dir="auto">Thanks,<br>
Anuj Kumar</p>