graph-database

Description

It is recommended to change the built-in NBA data set to basketballPlayer.
Because a user might import an NBA data set and then use the sample command that only works in basketballPlayer.

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()

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() {

See #1029

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

The regex crate is currently employed in lib for some fairly trivial validation. This could be replaced fairly easily with some hand-written rust code.

Per discussion in #2743 this class is mis-named.

Also, rename LinkStreamValue to just plain LinkStream.