Missing documentation on filtering rows on LOAD CSV when using CALL {} IN TRANSACTIONS about neo4j HOT 2 OPEN

The reason your initial approach did not work is due to restrictions on the importing WITH clause...the one at the start of the subquery, as the purpose of an importing WITH is only to define what is in-scope for the subquery, you cannot filter on it.

You can add a subsequent WITH immediately after for the purpose of filtering afterward:

LOAD CSV ...
CALL {
    WITH row   // importing WITH, can't filter with a WHERE
    
    WITH row  // regular WITH, we can filter this one
    WHERE ...
    MERGE...(etc.)
} IN TRANSACTIONS

from neo4j.

Thank you for clarifying!

Aside from the runtime error, I did not find any documentation on the restriction of these importing WITH clauses.

Also, this restriction seems to apply specifically to importing WITH clauses within CALL {} IN TRANSACTIONS: I ran the same query without transactions and it did not throw this error (it ran out of memory though).

Anyways, perhaps the restriction info and solution example could be added to the documentation here:
https://neo4j.com/docs/cypher-manual/current/clauses/load-csv/#load-csv-importing-large-amounts-of-data

Besides, I found references to the deprecated USING PERIODIC COMMIT here. I think these should be updated?
https://neo4j.com/developer/guide-import-csv/#_optimizing_load_csv_for_performance

from neo4j.