If someone define a constraint but do not explicitly enable or disable it, Oracle enables it by default.
Any SQL INSERT, UPDATE or DELETE command applied to a table with constraints enabled has the possibility of failing. This is not true in case a constraint is disabled so Neo4j-etl, should, in my opinion be able to represent this situation while importing. If a table with a foreign key (which is enabled) is treated as a Join and imported as a node with a relationship, neo4j-etl should not import a table with a disabled foreign-key and inform any end-user of the event.
If someone define a constraint but do not explicitly enable or disable it, Oracle enables it by default. Any SQL INSERT, UPDATE or DELETE command applied to a table with constraints enabled has the possibility of failing. This is not true in case a constraint is disabled so Neo4j-etl, should, in my opinion be able to represent this situation while importing. If a table with a foreign key (which is enabled) is treated as a Join and imported as a node with a relationship, neo4j-etl should not import a table with a disabled foreign-key and inform any end-user of the event.