graph-database

Description

context: https://discuss.nebula-graph.com.cn/t/topic/6991

In Chapter 5. Schema and Data Modeling first there is paragraph:

The default cardinality setting is SINGLE. Note, that property keys used on edges and properties have cardinality SINGLE. Attaching multiple values for a single key on an edge or property is not supported.

and then example:

mgmt = graph.openManagement()
follow = mgmt.makeEdgeLabel('follow').multiplicity(MULTI).make()

See #1029

Is your feature request related to a problem? Please describe.
CSV files produced in different locales have different default separators, a comma-separated file (",") is but one type of CSV.

In Sweden we usually use a semicolon (";") as separator and many CSV files use a tab as separator ("\t"). Importing CSVs requires reformatting them before import, and causes inoperability issues and f

Append class to all HashCodeBuilders in Gaffer for the below issue to minimise hash collisions.

@Test
    void name() {
        Foo foo = new Foo();
        Bar bar = new Bar();

        assertFalse(foo.equals(bar));
        assertNotEquals(foo.hashCode(), bar.hashCode()); //fails
    }

    class Bar {
        int a = 3;

        @Override
        public int hashCode() {

Feature description (Mandatory)

Please add the capability to specify the type of array instead of defaulting to string. i.e.
apoc.array.int()

How this feature can improve the project?

By default, it is created as a string. Some customers have asked for the ability to hint at the data type.

If you do object.association.distinct.other_association, the distinct goes away.

This is probably good for the simple implementation, but we could have a WITH DISTINCT automatically go in there on the second association

Once #157, it'd be great to add support for batch importing from a CSV file. CSV would act as a decent lowest-common-denominator format. In the future, other formats could be added as well (e.g. RDF XML) based off demand.