title: After upgrading to Neo4j 3.2 all my HTTP Transactional API queries fail
body: <p>Is 3.2 an API-Breaking Release?
  No. Minor releases are a place to deprecate features and functionality, which includes public APIs. However, we will not remove deprecated functionality until a major release.</p>
  
  <p>Upgrading my DB from 3.1.5 to 3.2 is successful, but almost every HTTP API query from my app to Neo4j fails. </p>
  
  <p>E.g.:  </p>
  
  <blockquote>
    <p>2017-06-11 12:01:20.808+0000 ERROR Failed to generate JSON output. Can
    not start an object, expecting field name mmneo_1       |
    org.codehaus.jackson.JsonGenerationException: Can not start an object,
    expecting field name</p>
  </blockquote>
  
  <p>And on a successful query, the result returned is not the result of the query, but a warning from the planner:</p>
  
  <pre><code>&amp;{200 OK 200 HTTP/1.1 1 1 map[Access-Control-Allow-Origin:[*] Retry-Count:[0] Server:[Jetty(9.2.9.v20150224)] Date:[Sun, 11 Jun 2017 12:01:20 GMT] Content-Type:[application/json]] {{"results":[{"columns":["newSession"],"data":[]}],"notifications":[{"code":"Neo.ClientNotification.Statement.PlannerUnavailableWarning","severity":"WARNING","title":"The RULE planner is not available in the current CYPHER version, the query has been run by an older CYPHER version.","description":"CREATE UNIQUE is unsupported for current CYPHER version, the query has been execute by an older CYPHER version","position":{"offset":100,"line":4,"column":1}}],"errors":[]}} -1 [] true false map[] 0xc420234300 &lt;nil&gt;} {"results":[{"columns":["newSession"],"data":[]}],"notifications":[{"code":"Neo.ClientNotification.Statement.PlannerUnavailableWarning","severity":"WARNING","title":"The RULE planner is not available in the current CYPHER version, the query has been run by an older CYPHER version.","description":"CREATE UNIQUE is unsupported for current CYPHER version, the query has been execute by an older CYPHER version","position":{"offset":100,"line":4,"column":1}}],"errors":[]}
  </code></pre>
  
  <p>IMO, the release notes, and <em>especially</em> the upgrade notes are sad and basically a circular reference.</p>
  
  <p>I am sure it is something stupid, but honestly, I expected it to just work. How silly of me?</p>