You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the bulk loader with enforce schema we are expected to define a value for the missing columns can_move for cat or can_make_noise for moving item.
There are cases where in data we are trying to load doesn't make sense to use default values , i.e cases where we can't assert that if this is not provided then use False (or True) for that matter .
Question is is it possible to accept missing values and not write those properties in the graph if values for those columns (attributes) are not provided?
The text was updated successfully, but these errors were encountered:
Sorry for the late response! The enforce-schema option currently assumes no property is optional, but I agree that this is a worse design than allowing missing values.
If you'd like to open a PR to this effect, I'd happily merge it, otherwise I will add this to the project backlog!
This is more of a question with a use case when loading nodes
lets imagine we have two objects
let's say we can create a schema merging the properties of these objects that looks something like
When using the bulk loader with enforce schema we are expected to define a value for the missing columns
can_move
forcat
orcan_make_noise
formoving item
.There are cases where in data we are trying to load doesn't make sense to use default values , i.e cases where we can't assert that if this is not provided then use
False
(orTrue
) for that matter .Question is is it possible to accept missing values and not write those properties in the graph if values for those columns (attributes) are not provided?
The text was updated successfully, but these errors were encountered: