Record fields have been truncated

[wadael]

Hello

I migrated a graph from 3.1 community to 3.5 enterprise.
The graph is very rich, like too rich, I've seen redundancy of information.
And the volume is respectable with 3.4M nodes and 10M relations.

I have to remodel this

So, I called CALL db.schema.visualization() to get an overview
and I get this message "Record fields have been truncated" at the bottom of the card whether I display table/text/code views.
There is no graph view

Why is there a truncate ?
As per eye investigation looking at a few labels, there is a max of ten properties.
Or too many labels ?

I increased the browser settings (1000 initial nodes, 500 neighbours) for the same result.

Taking any idea. Thanks

[sameerG]

There are a lot of subtle differences between community edition and enterprise edition.
Please note all these differences.Also try upgrading to 4.1.(x)(except 4.1.0) Enterprise edition after remodeling and please see if CALL db.schema.visualization() to get an overview works.

[wadael]

I migrated to 4.1.1 anyway, as its the target.
Same issue.

So I ran the consistency-check.

inconsistencies-2020-07-17.14.45.42.report.txt (15.8 KB)

[hix]

I am having the same issue when using CALL db.schema.visualization(), using 4.1.0. I also tried increasing the nodes and neighbors without any luck.

[wadael]

As per a quick search in the browser repo, I find

GitHub

neo4j/neo4j-browser

Neo4j Browser is the general purpose user interface for working with Neo4j. Query, visualize, administrate and monitor the database. - neo4j/neo4j-browser

However, still no idea why the records get truncated
Truncated records is calculated in https://github.com/neo4j/neo4j-browser/blob/bb59893aff0fb777983b6cab75a31e490c3a750e/src/browser/mod... with

if (!maxFieldItems || !result) {
return false
}

So why are the records sent to browser truncated ?
I what cases does it happen ? (insiders super expert with hands in the code needed here)

[wadael]

Hum, same symptom (records truncated when calling viz) with this configuration :

using as source a 3.5 Community (with the data imported from a 3.3.1 Community dump), indexes and constraints dropped and recreated (btree native indexes). resampled.

Whole graph exported as cypher script (1.7GB)
Fed to cypher shell for use by 4.4.1 Community (was long).

[wadael]

And aggain; records truncated when calling db.schema.viz

this time I exported 3.3.1 Community content as cypher script for cypher-shell.
Ran it against a Community 4.1
No 3.5 in between

[wadael]

Ah. The 3.3 version I inherited was in fact using a 0.A.7 store
(which is pre-3.2)
I upgraded to 0.A.8 then 0.A.9 then SF4.0

All constraints and indexes recreated for good measure.

However, I still do not get the nodes view returned when I call for the overview.
(records truncated).