3.2是一個API-Breaking Release? 否。次要版本是棄用功能和功能的地方,其中包括公共API。但是,我們不會在主要版本之前刪除已棄用的功能。升級到Neo4j 3.2後,我所有的HTTP Transactional API查詢都失敗了
將我的數據庫從3.1.5升級到3.2是成功的,但幾乎所有從我的應用程序到Neo4j的HTTP API查詢都失敗。
例如爲:
2017年6月11日12:01:20.808 + 0000 ERROR無法生成JSON輸出。可以 不啓動對象,期望字段名稱mmneo_1 | org.codehaus.jackson.JsonGenerationException:無法啓動對象, 期待字段名
而且對成功的查詢,返回的結果是不是查詢的結果,但是從策劃者的警告:
&{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 <nil>} {"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":[]}
IMO,版本註釋,和尤其升級說明是悲傷和基本上圓形的參考。
我相信這是愚蠢的,但說實話,我希望它工作。我有多傻?
是的。但是我期待發布說明所建議的後備方案。如果我必須通過並改變我的疑問,或者預先考慮CYPHER 3.1,這是一個突破性的改變。假如Neo4j沒有使用語義版本控制,我可以對3.2進行突破性修改。我只是不想讓他們告訴我,沒有任何改變,但事實上,沒有改變,我的代碼會變爲地獄 – GoTomGo
你是否試過3.2.1?我相信在3.2.0中RULE規劃器有一些與回退有直接關係的錯誤。 – InverseFalcon