Change Password

Please enter the password.
Please enter the password. Between 8-64 characters. Not identical to your email address. Contain at least 3 of: uppercase, lowercase, numbers, and special characters.
Please enter the password.
Submit

Change Nickname

Current Nickname:
Submit

Apply New License

License Detail

Please complete this required field.

  • Ultipa Blaze (v4)

Standalone

Please complete this required field.

Please complete this required field.

Please complete this required field.

Please complete this required field.

Leave it blank if an HDC service is not required.

Please complete this required field.

Leave it blank if an HDC service is not required.

Please complete this required field.

Please complete this required field.

Mac addresses of all servers, separated by line break or comma.

Please complete this required field.

Please complete this required field.

Cancel
Apply
ID
Product
Status
Cores
Maximum Shard Services
Maximum Total Cores for Shard Service
Maximum HDC Services
Maximum Total Cores for HDC Service
Applied Validity Period(days)
Effective Date
Expired Date
Mac Address
Reason for Application
Review Comment
Close
Profile
  • Full Name:
  • Phone:
  • Company:
  • Company Email:
Change Password
Apply

You have no license application record.

Apply
Certificate Issued at Valid until Serial No. File
Serial No. Valid until File

Not having one? Apply now! >>>

Product Created On ID Amount (USD) Invoice
Product Created On ID Amount (USD) Invoice

No Invoice

v5.0
Search
    English
    v5.0

      Execution Plan

      Overview

      When a GQL query is submitted to Ultipa, it first undergoes parsing to validate its syntax. Once parsed, the query is passed through an optimization phase where Ultipa evaluates potential execution strategies based on the current state of the database.

      Ultipa’s query optimizer selects the most efficient execution plan by considering factors like data distribution, indexing, and potential bottlenecks. This execution plan outlines the optimal sequence of operations, minimizing resource consumption and improving query performance.


      Lifecycle of a GQL query

      Explaining Execution Plans

      To view the execution plan of a GQL query without running it, use the EXPLAIN prefix. This generates a detailed view of the operator tree that outlines each step in the query’s process to retrieve the desired result.

      EXPLAIN
      MATCH (m:movie)-[]-(:country {name: "US"})
      RETURN m.genre AS genre, count(m) GROUP BY genre
      

      Return{expr:[genre,count(m)]  row_type:genre:ANY,count(m):ANY}
      ->    With{exprs:[genre,$value_7  as  count(m)],row_type:genre:STRING,count(m):UINT64}
              ->    Aggregate{key:[genre],agg:[sum(#agg_27_0)  as  $value_7],phase:GLOBAL_MERGE}
                      ->    Exchange(PartitionByNode){distribution:distribution_type:ANY,gap_type:SOURCE}
                              ->    Aggregate{key:[genre],agg:[count(m)  as  #agg_27_0],phase:PARTIAL}
                                      ->    With{exprs:[m,m.genre  as  genre],row_type:m:NODE{},genre:ANY}
                                              ->    With{exprs:[m_4  as  m],row_type:m:NODE{}}
                                                      ->    Filter{predicate:(&&,(&&,(PROPERTY_EXISTS,anno_6,name),(eq,anno_6.name,US)),(is_schema,anno_6,country,4,NODE)),row_type:m_4:NODE{},anno_5:EDGE{},anno_6:NODE{}}
                                                              ->    Extend(INTO)(start){(m_4)-[anno_5]-(anno_6)}::m_4:NODE{},anno_5:EDGE{},anno_6:NODE{}  on  $2[m_4]
                                                                      ->    ExchangeApply{CORRELATE,row_type:m_4:NODE{},anno_5:EDGE{},anno_6:NODE{},cors:m_4:ANY,cor_id:2}
                                                                              ->    NodeSearch{alias:m_4,row_type:m_4:NODE{},access_method:{condition:@movie,index_name:schema,query_type:SK_SCHEMA_SCAN}}
                                                                              ->    Exchange(PartitionByNode){cors:2,distribution:distribution_type:ANY,gap_type:SOURCE,cor_ids:[2]  }
                                                                                      ->    NodeSearch{alias:anno_6,predicate:(&&,(PROPERTY_EXISTS,anno_6,name),(eq,anno_6.name,US)),row_type:anno_6:NODE{},access_method:{condition:@country,index_name:schema,query_type:SK_SCHEMA_SCAN}}
      

      The EXPLAIN feature helps in analyzing the performance implications of a query by revealing the structure and sequence of operations. This preview is essential for optimizing queries, as it allows for adjustments to achieve greater efficiency before executing the full query.

      Please complete the following information to download this book
      *
      公司名称不能为空
      *
      公司邮箱必须填写
      *
      你的名字必须填写
      *
      你的电话必须填写
      Privacy Policy.
      Please agree to continue.