Full text index http POST gives "invalid header" and 500 error

[jonam]

We were not able to post larger size text to neo4j full text index in versions 1.8+ and 1.9.3. It looks like around 3900 characters or so, it starts breaking. Initially for 3871 and higher, there is a delay, and after a long pause, it comes back with invalid header message. For lengths of size 3900+ it returns back quickly with a status 500. Below 3870, it works just fine. We were able to reproduce it in a few lines of code.

https://github.com/jonam/Neo4JExample/blob/master/src/main/java/com/redbasin/neotest/Neo4JPostFullTextTest.java

We have put the error messages in the above source. The whole project is on github, and there is a pom.xml, which can be changed to use different versions of Neo4J.

Let me know if there is something we are doing wrong? As we have many entries that are larger than 3780 for the full text index.

For POST request, we are gettting back the response status code, but now processing the response otherwise. Not yet, at least.

thanks Manoj

[jonam]

Hello,

I got DM from @Neo4J that this is a known problem. Please let us know when this can be fixed, as this is blocking our progress. We depend on the full text index quite a bit. Thank you for your help!

Cheers, Manoj

[peterneubauer]

@jakewins could you please take a look? Seems to be a blocker for @jomam. Have you tried this with 2.0 too @jomam?

[jexp]

Already in investigation and prioritization as the issue-labels say.

[jonam]

@peterneubauer I tried changing the maven tags to:

org.neo4j neo4j 2.0.0-M05

and

org.neo4j neo4j-rest-graphdb 1.9.3 But looks like the code requires more changes, as it's not compiling. Perhaps the Neo4J API has changed, or the packages have moved. So this will take longer to verify, if the new version 2.0.0-M05 has fixed it. Also, the downloaded neo4J server is 2.0.0-M06. So the versions M05 and M06 do not match, not sure, if that would present additional problems. Did you guys try to compile above code with the new version and test it? Let me know.

[jexp]

There is a 2.0.0-M06 version of neo4j-rest-graphdb, I released it last week on m2.neo4j.org

[jexp]

The issue is not fixed yet, but under discussion.

[jonam]

Hi Michael,

Thanks for the neo4j-rest-graphdb version. I will check this out. And yes, thanks for making me aware that the issue is not fixed in this new version yet, so I won't test it again. I will just wait for an update on this discussion thread from you, on when this is fixed.

Manoj github: @jonam twitter: @jonam_biz

[rickardoberg]

Fixed here: https://github.com/neo4j/neo4j/commit/cd0cc83b6d0700f553dad127860c9ad543d1754a