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 Graph V4

Standalone

Please complete this required field.

Please complete this required field.

The MAC address of the server you want to deploy.

Please complete this required field.

Please complete this required field.

Cancel
Apply
ID
Product
Status
Cores
Applied Validity Period(days)
Effective Date
Excpired Date
Mac Address
Apply Comment
Review Comment
Close
Profile
  • Full Name:
  • Phone:
  • Company:
  • Company Email:
  • Country:
  • Language:
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

Search

      BATCH

      Overview

      The BATCH clause partitions data into smaller batches, where each batch collects data into an array. These arrays are then processed sequentially by the following clause. The BATCH clause is helpful when dealing with large datasets that may overwhelm memory resources, potentially leading to system crashes. While this strategy can result in a slight performance sacrifice, it significantly reduces memory usage. This approach is particularly beneficial when passing a large number of start nodes into a path query, ensuring efficient and stable query execution.

      Syntax

      The BATCH clause should follow the definition of an alias, except when a LIMIT or SKIP clause intervenes:

      `<clause>` as `<alias>` `<LIMIT/SKIP clause?>` BATCH `<batch-size>`
      `<clause>`
      

      Where <batch-size> is the amount of data in each batch.

      Examples

      find().nodes({@post}) as nodes LIMIT 1000 BATCH 100
      khop().n(nodes as a).le()[2].n() as b 
      GROUP BY a 
      WITH avg(b.length) as len
      RETURN a._uuid, len ORDER BY len DESC LIMIT 10
      

      This UQL puts 1000 @post nodes into 10 batches, each containing 100 nodes. Nodes in each batch are automatically collected into an array and passed into the khop() query, which is executed for 10 times independently. Afterward, the final results of the khop() query are combined and used in the subsequent clauses.

      find().nodes({@user.age_level == 4}) as users
      BATCH 100
      n(users).e().n({@ad} as ads)
      GROUP BY ads.cate
      RETURN table(ads.cate, count(ads.cate))
      

      This UQL puts all @user nodes of the no.4 age group into batches, each containing 100 nodes. Nodes in each batch are automatically collected into an array and passed into the path template query, which is executed for multiple times independently. Afterward, the final results of the path template query are combined and used in the subsequent clauses.

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