Home > Articles > Data

Like this article? We recommend

Like this article? We recommend

Advanced Cypher Queries

The examples in the preceding section are pretty simple traversals from one starting node to a set of results. In this section, let's create a more robust example with multiple starting nodes and complex conditions. For this example, we'll create a simple movie catalog that has the following types of nodes:

  • Movies: Movies include The Avengers, The Avengers: Age of Ultron, Iron Man, and The Wolverine.
  • Characters: Super heroes that appear in our movies include Iron Man, The Hulk, Captain America, Thor, and Wolverine.
  • Tag: Tags are genres that can be associated with a movie; they include Action, Super Heroes, Marvel, X-men, and New Release.

Figure 1 shows this graph.

Figure 1

Figure 1 Movie catalog graph.

Essentially we're keeping track of super hero movies, tags for those movies, and the characters that appear in them.

The following snippet creates these nodes and their relationships:

public enum Labels implements Label
{
    MOVIE,
    TAG,
    CHARACTER;
}

public enum RelationshipTypes implements RelationshipType
{
    HAS_TAG,
    PERFORMS_IN;
}

public static void main( String[] args )
{
    GraphDatabaseService graphDB = new GraphDatabaseFactory().newEmbeddedDatabase("data");

    // Setup a movie graph
    try( Transaction txn = graphDB.beginTx() )
    {
        // Create characters
        Node ironMan = graphDB.createNode( Labels.CHARACTER );
        ironMan.setProperty( "name", "Iron Man" );
        Node captainAmerica = graphDB.createNode( Labels.CHARACTER );
        captainAmerica.setProperty( "name", "Captain America" );
        Node hulk = graphDB.createNode( Labels.CHARACTER );
        hulk.setProperty( "name", "The Hulk" );
        Node thor = graphDB.createNode( Labels.CHARACTER );
        thor.setProperty( "name", "Thor" );
        Node wolverine = graphDB.createNode( Labels.CHARACTER );
        wolverine.setProperty( "name", "Wolverine" );

        // Create movie tags
        Node actionTag = graphDB.createNode( Labels.TAG );
        actionTag.setProperty( "name", "Action" );
        Node marvelTag = graphDB.createNode( Labels.TAG );
        marvelTag.setProperty( "name", "Marvel" );
        Node superHeroTag = graphDB.createNode( Labels.TAG );
        superHeroTag.setProperty( "name", "Super Hero" );
        Node xmenTag = graphDB.createNode( Labels.TAG );
        xmenTag.setProperty( "name", "X-Men" );
        Node newReleaseTag = graphDB.createNode( Labels.TAG );
        newReleaseTag.setProperty( "name", "New Release" );

        // Create movies
        Node avengers = graphDB.createNode( Labels.MOVIE );
        avengers.setProperty( "name", "The Avengers" );
        avengers.createRelationshipTo( marvelTag, RelationshipTypes.HAS_TAG );
        avengers.createRelationshipTo( actionTag, RelationshipTypes.HAS_TAG );
        avengers.createRelationshipTo( superHeroTag, RelationshipTypes.HAS_TAG );
        ironMan.createRelationshipTo( avengers, RelationshipTypes.PERFORMS_IN );
        captainAmerica.createRelationshipTo( avengers, RelationshipTypes.PERFORMS_IN );
        hulk.createRelationshipTo( avengers, RelationshipTypes.PERFORMS_IN );
        thor.createRelationshipTo( avengers, RelationshipTypes.PERFORMS_IN );

        Node avengers2 = graphDB.createNode( Labels.MOVIE );
        avengers2.setProperty( "name", "The Avengers: Age of Ultron" );
        avengers2.createRelationshipTo( marvelTag, RelationshipTypes.HAS_TAG );
        avengers2.createRelationshipTo( actionTag, RelationshipTypes.HAS_TAG );
        avengers2.createRelationshipTo( superHeroTag, RelationshipTypes.HAS_TAG );
        avengers2.createRelationshipTo( newReleaseTag, RelationshipTypes.HAS_TAG );
        ironMan.createRelationshipTo( avengers2, RelationshipTypes.PERFORMS_IN );
        captainAmerica.createRelationshipTo( avengers2, RelationshipTypes.PERFORMS_IN );
        //hulk.createRelationshipTo( avengers2, RelationshipTypes.PERFORMS_IN );
        thor.createRelationshipTo( avengers2, RelationshipTypes.PERFORMS_IN );

        Node ironManMovie = graphDB.createNode( Labels.MOVIE );
        ironManMovie.setProperty( "name", "Iron Man" );
        ironManMovie.createRelationshipTo( marvelTag, RelationshipTypes.HAS_TAG );
        ironManMovie.createRelationshipTo( actionTag, RelationshipTypes.HAS_TAG );
        ironManMovie.createRelationshipTo( superHeroTag, RelationshipTypes.HAS_TAG );
        ironMan.createRelationshipTo( ironManMovie, RelationshipTypes.PERFORMS_IN );

        Node theWolverine = graphDB.createNode( Labels.MOVIE );
        theWolverine.setProperty( "name", "The Wolverine" );
        theWolverine.createRelationshipTo( xmenTag, RelationshipTypes.HAS_TAG );
        theWolverine.createRelationshipTo( actionTag, RelationshipTypes.HAS_TAG );
        theWolverine.createRelationshipTo( superHeroTag, RelationshipTypes.HAS_TAG );
        wolverine.createRelationshipTo( theWolverine, RelationshipTypes.PERFORMS_IN );

        // Success!
        txn.success();
    }
}

Click here to download a zip file containing the source files for this article.

Let's start simple by finding all the movies:

match( movie :MOVIE ) return movie.name

The full code snippet follows:

System.out.println( "Movies" );
try( Transaction txn = graphDB.beginTx();
    Result results = graphDB.execute( "match( movie :MOVIE ) return movie.name" ) )
{
    while( results.hasNext() )
    {
        Map<String,Object> result = results.next();
        System.out.println( "\t" + result.get( "movie.name" ) );
    }
    txn.success();
}

We match all nodes with the MOVIE tag and return each node's name. The output is the following:

Movies
        The Avengers
        The Avengers: Age of Ultron
        Iron Man
        The Wolverine

Now let's find all Marvel movies. To do this, we need to find the Marvel tag node and traverse to all movies that maintain a HAS_TAG to the Marvel tag. This query looks like the following:

MATCH(marvelMovies:TAG {name:'Marvel'})<-[:HAS_TAG]-(movie)
RETURN movie.name

We find each node that has the TAG label and a name property value of “Marvel” and follow that tag's HAS_TAG inbound relationships to the movies with that tag. Figure 2 shows this logic.

Figure 2

Figure 2 Find Marvel movies.

The output from this query is the following:

Marvel Movies
        Iron Man
        The Avengers: Age of Ultron
        The Avengers

Now let's find all newly released Marvel movies. This query is a little more complex because we need to find the Marvel tag node and the New Release tag node, and then find all nodes that have a HAS_TAG relationship with both of them. Figure 3 shows this logic.

Figure 3

Figure 3 Finding new release Marvel movies.

The query looks like the following:

MATCH(newRelease:TAG {name:'New Release'}),
     (marvelMovies:TAG {name:'Marvel'})-[:HAS_TAG]-(movie)
WHERE (newRelease)-[:HAS_TAG]-(movie)
RETURN movie.name

We define two variables in our match clause: newRelease and marvelMovies. We follow the marvelMovies tag to all movies that have HAS_TAG relationships with marvelMovies, and then we add a WHERE condition that verifies a path from the newRelease variable (which matches the “New Release” tag) to that movie.

To take this example one step crazier, let's find all new release Marvel movies about super heroes. You can add more movies to your example to validate that the query works; for an easier test, just comment out the superHeroTag from The Avengers and then validate that it is excluded from the list. The following query shows how to match three tags:

MATCH(superHeroes:TAG {name:'Super Hero'}),
     (newRelease:TAG {name:'New Release'}),
     (marvelMovies:TAG {name:'Marvel'})-[:HAS_TAG]-(movie)
WHERE (newRelease)-[:HAS_TAG]-(movie) AND
     (superHeroes)-[:HAS_TAG]-(movie)
RETURN movie.name

We define three variables: superHeroes, newReleases, and marvelMovies, all pointing to their respective tag nodes. We started from the marvelMovies node and traversed across all HAS_TAG relationships, and then filtered the results with two WHERE clauses, joined together with the AND keyword. In other words, find all Marvel movies that have a path from the “New Releases” tag to that movie and a path from the “Super Hero” tag to that movie. As expected, this query outputs the following:

New Release Marvel Super Hero Movies
        The Avengers: Age of Ultron

That covers multiple starting tags, but let's bring in a character too. The following query finds all Marvel movies that have Thor as a character:

MATCH(marvelMovies:TAG {name:'Marvel'})-[:HAS_TAG]-(movie)-[:PERFORMS_IN]-(thor:CHARACTER {name:'Thor'})
RETURN movie.name

We start by finding the Marvel tag and following all of its HAS_TAG relationships to movies, but then we follow that selected movie to Thor by following the PERFORMS_IN relationship to the Thor node. This query outputs the following results:

Marvel Movies with Thor
        The Avengers: Age of Ultron
        The Avengers

Next, we can combine the two strategies to find all new release Marvel movies that have Thor:

MATCH(marvelMovies:TAG {name:'Marvel'}),(newRelease:TAG {name:'New Release'})-[:HAS_TAG]-(movie)-[:PERFORMS_IN]-(thor:CHARACTER {name:'Thor'})
WHERE (marvelMovies)-[:HAS_TAG]-(movie)
RETURN movie.name

We define a variable named marvelMovies that references the Marvel TAG, follow the HAS_TAG relationships from the New Release TAG to movies for which there is a path to the Thor node via the PERFORMS_IN relationship.

Likewise, we can find all new release Marvel movies featuring both Thor and The Hulk:

MATCH(marvelMovies:TAG {name:'Marvel'}),
     (newRelease:TAG {name:'New Release'})-[:HAS_TAG]-(movie)-[:PERFORMS_IN]-
          (thor:CHARACTER {name:'Thor'}),
          (hulk:CHARACTER {name:'The Hulk'})
WHERE (marvelMovies)-[:HAS_TAG]-(movie) AND (movie)-[:PERFORMS_IN]-(hulk)
RETURN movie.name

There are multiple ways to write queries; these are just meant to encourage you to think in terms of nodes and relationships. The query I've just described could be written as follows:

MATCH(thor:CHARACTER {name:'Thor'}),
     (hulk:CHARACTER {name:'The Hulk'}),
     (marvelMovies:TAG {name:'Marvel'}),
     (newRelease:TAG {name:'New Release'})-[:HAS_TAG]-(movie)
WHERE (marvelMovies)-[:HAS_TAG]-(movie)
  AND (movie)-[:PERFORMS_IN]-(hulk)
  AND (movie)-[:PERFORMS_IN]-(thor)
RETURN movie.name

In this case, we define all of our node references at the beginning, select a starting node (New Releases), find the movies that have that tag, and then define filter conditions to refine the results. I see this last query as being easier to read; but, as you can see, there are many alternative ways of writing Cypher queries.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020