Erica Wood

Potentially, we could add newlines rather than limiting the number of entries in the publications info dictionary. See: https://stackoverflow.com/questions/56511859/weird-input-data-no-newline-character-in-the-whole-buffer-4194304-not-supporte

The original error message was: original error: Tried to read a field larger than buffer size 4194304. A common cause of this is that a field has an unterminated quote...

Attached is a file containing the error along with the edge it failed on [neo4j_buffer_issue_2019.log](https://github.com/RTXteam/RTX/files/4794371/neo4j_buffer_issue_2019.log) (it is from 2019). To keep a record of where I'm looking for information: https://github.com/neo4j/neo4j/issues/11687...

I posted an issue report on Neo4j here: https://community.neo4j.com/t/mismatching-store-id-on-neo4j-admin-import/20504 This applies to this issue because I found a way to avoid the buffer overflow issue with --read-buffer-size, but it only...

We can't test on the latest KG2 build without rebuilding the TSV files. Would that be helpful? @saramsey, what are your thoughts, since the data is on your instance?

The new build did not fix this. (I rebuilt the TSV files without the workaround). Please see the attached log file for more information (it was too long to feature...

RTX KG2.2.2 is giving the following error: 

The node in question is this (for reference):  The node after this node is VERY long. It has a long description. (which I am 90% sure is "PathWhiz.Compound:1134" after...

I worked on regenerating the TSV files, such that it would print out the offending node ID and the offending field for nodes above the limit. Here's the output: 

> @ericawood you indicated that you have some code related to this issue, that we will want to preserve. Can you please put that code somehwere, like in a branch...