# How to use elasticsearch as a graph query solution

**URL:** <https://discuss.elastic.co/t/how-to-use-elasticsearch-as-a-graph-query-solution/111924>\
**Category:** Elasticsearch\
**Created:** [December 15, 2017, 8:38am UTC](https://discuss.elastic.co/t/how-to-use-elasticsearch-as-a-graph-query-solution/111924 "2017-12-15T08:38:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bryan\_rasmussen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bryan_rasmussen/32/874_2.png) [@bryan\_rasmussen](https://discuss.elastic.co/u/bryan_rasmussen)\
**Post date:** [December 15, 2017, 8:38am UTC](https://discuss.elastic.co/t/how-to-use-elasticsearch-as-a-graph-query-solution/111924/1 "2017-12-15T08:38:26Z")

</div>

I would like to get examples of how I should structure this data, and queries of it:

Assuming I have a graph with Nodes  
NodeA, NodeB, NodeC  
PropA, PropB, PropC, PropD

The prop nodes are properties of the Node nodes, and they can override each other.

NodeA has the properties PropA, PropD (I show override properties later in list, so PropD on NodeA has overridden PropA)  
NodeB has the properties PropB, PropC, PropA  
NodeC has the properties PropD, PropC, PropA, PropB.

So I know how to structure graph queries in Neo4J to be able to figure out which property overrides most other properties and what nodes it is found on -  
so what I'm hoping is example of how you might solve this in elasticsearch in a performant manner?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 12, 2018, 8:38am UTC](https://discuss.elastic.co/t/how-to-use-elasticsearch-as-a-graph-query-solution/111924/2 "2018-01-12T08:38:49Z")

</div>

Closed on January 12, 2018, 8:38am UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.