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

LTE and standard indexes

Answer this question
Resolved
Yuri Simione2024-04-09

For a specific use case I need to LTE a property. I needed and created a standard index for the same property. Can LTE feauture e standard index cohesist? In this case, can you explain the benefit to have both features enabled for the same property? 

LTEindex

2 Answer(s)

  • 1 vote

    Index and LTE can co-exist.

    And they do have differences in terms of:
    1. they are query acceleartions at different levels;
    2. they are used in different circumstances.

    Index is more for meta-data oriented operations, such as nodes or edges (and property fields tied to them). Therefore you can see, index is for discrete (disconnected?) query accelerations.

    LTE is specifically designed to accelerate path/k-hop and certain graph algorithms that traverse conneted nodes and edges. In plain English, LTE is for path-like traversal accelerations.

    I hope this clarifies?

    Good_Architect 2024-04-10
    Add a comment...

    Discard
    Post
  • 0 vote

    Hi Yuri,

    Yes you can have a property both LTE-ed and indexed, because they will be used for different scenarios.
    Index accelerates the retrieval of metadata, i.e., the find().nodes() and find().edges() queries, where LTE is not applicable.
    For other queries (path, khop, etc.), index is preferentially used for filtering the start nodes, and LTE for filtering intermediate nodes/edges and destination nodes.

    Hope it helps!
    Pearl

    Pearl C 2024-04-10
    Add a comment...

    Discard
    Post

Your Answer

Post
Discard