Did you see the ontology checking article on
https://jbarrasa.com/2016/04/06/building-a-semantic-graph-in-neo4j/
There is also imho a constraints extension from GraphAware for that.
I think you should also be able to use apoc triggers to veto transactions
that violate your constraints.
Join our n
I think you have to restore the auth folder to the same content as
the other cluster members
On Mon, Oct 21, 2019 at 8:38 PM Srihari Prabhakar
wrote:
> Hi folks,
>
> I am getting the below error when logging in to one of the server in
> causal cluster.
>
> [root@neo-vm1~]# cypher-shell -uneo4j
Hi folks,
I am getting the below error when logging in to one of the server in causal
cluster.
[root@neo-vm1~]# cypher-shell -uneo4j -p## -a'##'
The client has provided incorrect authentication details too many times in
a row.
It is a 3 node cluster, connection to other 2 nodes is fin
I have a requirement of placing a set of constraints on nodes,
relationships and properties, and making these discoverable.
For instance, a constraint might be that a relationship X may exist between
nodes with labels A and B, , D and B, or B and C, but not between A and C
or A and D.
Or, a con
