title: coprocessor deployment : replacing jar without restarting hbase will take effect?
body: <p>Let's assume this case.</p>
  
  <p>I have a coprocessor declared in hbase-site.xml</p>
  
  <pre><code>&lt;property&gt;
  &lt;name&gt;hbase.coprocessor.region.classes&lt;/name&gt;
  &lt;value&gt;my.co.processor&lt;/value&gt;
  &lt;property&gt;
  </code></pre>
  
  <p>and in hbase-env.sh I declared coprocessor classpath like this</p>
  
  <pre><code>export HBASE_CLASSPATH="${HBASE_HOME}/lib/coprocessor.jar"
  </code></pre>
  
  <ol>
  <li><p>If I find a bug in that coprocessor later, can I just replace that jar file in all region servers without restarting entire hbase?</p></li>
  <li><p>If I want to add another coprocessor, then I think I have to restart entire Hbase, am I correct?
  I know I can declare in hbase shell for every single table, but I think that's not an option to think about if I have many tables to apply new coprocessor.</p></li>
  </ol>