anchor.diff:  }'
   --------------------------------------------------
   
  -And, we can delete the doc if the tags contain blue, or ignore (noop):
  +And, we can even change the operation that is executed.  This example deletes
  +the doc if the `tags` field contain `blue`, otherwise it does nothing
  +(`noop`):
   
   [source,js]
   --------------------------------------------------
  
positive.code:         	"time":"2014-01-01 12:32"
          }
      },
      "upsert" : {
      }
  }'
  --------------------------------------------------
  The default `scripted_upsert` setting is `false` meaning the script is not executed for inserts.
  However, in scenarios like the one above we may be using a non-trivial script stored
  using the new "indexed scripts" feature. The script may be deriving properties
  like the duration of our web session based on observing multiple page view events so the
  client can supply a blank "upsert" document and allow the script to fill in most of the details
  using the events passed in the `params` element.
  
  
  Last, the upsert facility also supports `doc_as_upsert`. So that the
  provided document will be inserted if the document does not already
  exist. This will reduce the amount of data that needs to be sent to
  elasticsearch.
  
  [source,js]
  --------------------------------------------------
  
negative.code: }'
  --------------------------------------------------
  
  We can add a tag to the list of tags (note, if the tag exists, it
  will still add it, since its a list):
  
  [source,js]
  