Don't know if you use-case permits it, but this seems like a great place to use a traverse (esp. with lightweight edges). E.g. we ingest lots of data records from our data sources, building a set of manual sort-of indexes on-the-fly by making edges between records that share field-values that are of use in our queries. This lets us use high-performance traverses to find all the records that have e.g. name = "Smith" or size = "large" at the expense of additional storage space for the link fields.
On Wednesday, January 7, 2015 10:28:28 AM UTC-7, ATL wrote: > > How to search based on RID, let's say we have 10 Million Documents in one > database in one class, I want to search and filter 1 Million Documents > based on RID, How should we pass the 1 M RID string to limit search in > entier 10 M records class... > > *Notice of Confidentiality* > > *This email message and its attachments (if any) are intended solely for > the use of the addressees hereof. In addition, this message and any > attachments may contain information that is confidential, privileged and > exempt from disclosure under applicable law. If you are not the intended > recipient of this message, you are prohibited from reading, disclosing, > reproducing, distributing, disseminating or otherwise using this > transmission. Delivery of this message to any person other than the > intended recipient is not intended to waive any right or privilege. If you > have received this message in error, please promptly notify the sender by > reply email and immediately delete this message from your system.* > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
