Add support for array-based properties on nodes and edges.
Issue #9
open
No description provided.
Comments (3)
-
reporter -
reporter We won't initially support the idea of a set of values being distributed across different fields, but it should be easy to support converting a single multi-valued field to a property array. Consider a field
vegetables
with the following value"carrots, peas, beans"
This would ordinarlly be stored as a single string-property in the graph. To convert to an array property, the descriptor for this field in the schema could define a
split
conversion:{"name":"vegetables", "conversion":"split:," }
Here the argument to split
,
is the delimiter. -
reporter - changed status to open
Use a "split" converter.
- Log in to comment
CSV files don't have the concept of an array-field, but it is possible for a set of fields to be considered elements of an array. For example, a table of RGB colours, with the first column is the colour name, and the following 3 are the colours values in terms of red, green and blue. It should be possible to create an array from the colours and store it on a single array property in the graph.