title: Aerospike - proper way to develop UDFs
body: <p><strong>UDF development background</strong><br>
  I was using Aerospike 3.5.12. Initially, I wrote UDFs remotely, then registered it to Aerospike via the Java client's UDF registration method. This method was a little cumbersome (it required re-registration for every change), but worked.</p>
  
  <p>Later, I found it more convenient to directly edit the file on the Aerospike server, at /aerospike_dir/usr/udf/lua/myUdf.lua. This worked conveniently. Changes made were permanent and remained even upon cluster restart (if I recall correctly).</p>
  
  <p>Recently, I upgraded to 3.6.1. I found that changes made directly to /aerospike_dir/usr/udf/lua/myUdf.lua are recognized by Aerospike until the cluster is restarted. After restart, all changes are lost, and the file reverts to its original version.</p>
  
  <p><strong>Question</strong><br>
  Is this normal behavior? How can I disable this auto-reversion? Or, if I'm not developing UDFs correctly, how should I approach it?</p>