It would be best to choose only the few properties that are really needed "in the graph", and only load those. Generally speaking it is not best practice to replicate a relational data store table structure (with large column counts) inside Neo4j, first sketch out a new graph meta-model, then load it, this usually requires some ETL steps, and often data cleaning. One can sketch out the meta-model on paper with a pencil, or using the arrows tool, which provides a more polished diagram if needed for the documentation.
Note, I can however envision a need to dynamically handle the property list, perhaps the property list is short but always changing? I imagine there are several ways to do it, but off the top of my head one way would be to dynamically build the cypher statement in a string and then execute it using this APOC call
CALL apoc.cypher.run()
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…