<https://lh3.googleusercontent.com/-jQSHJFR_qBg/V5jbPYty6oI/AAAAAAAAKqM/shQ66kpRQhsRaZ-vUM-UTQnVFfjH80gUwCLcB/s1600/o_db.png>
<https://lh3.googleusercontent.com/-VRJUvRqTp04/V5jaNpZTiMI/AAAAAAAAKqA/3JcukeHprLEW9Cl8ZPn8PSm6WiRZQJ1pQCLcB/s1600/o_db.png> <https://lh3.googleusercontent.com/-cl_XceZsb0U/V5jaBTAIlYI/AAAAAAAAKp8/pUcAcpMsWrMrp0x90cKOIqMTkt3N727NgCLcB/s1600/o_db.png> <https://lh3.googleusercontent.com/-cl_XceZsb0U/V5jaBTAIlYI/AAAAAAAAKp8/pUcAcpMsWrMrp0x90cKOIqMTkt3N727NgCLcB/s1600/o_db.png> Hi, just downloaded 2.2.5 community edition and tried to query the database with match. this is my database-structure (as posted in DEV.gz) - - E - scanner_result - sector_classification - - V - - Contract - Currency - Future - Option - Stock - ContractDetail - - Sector - Category - Industry - Subcategory With 2.2.5 the Match-query > MATCH {class: Industry, as: Industries} <-- {} <-- { as: Subcategories } > RETURN Industries, Subcategories > executes using the REST Interface as well as the Java-Api (with JRuby). Surprisingly, a slight modification MATCH {class: Industry, as: Industries} <-- {} <-- {} <-- { as: asset } > RETURN Industries, asset returns a Timeout-Error on the REST-Interface but gives a result using the java-api. The result-set is about 550 datasets. It took several minutes to perform the query. Now I am asking myself, where to start the optimizing-process. There are indexes sector (uniq, fields name, k) and contract (uniq, con_id). There is no Index any Edge-Class. A "view" to the Database – the query aims to fetch all Stocks related to an Industry: <https://lh3.googleusercontent.com/-jQSHJFR_qBg/V5jbPYty6oI/AAAAAAAAKqM/shQ66kpRQhsRaZ-vUM-UTQnVFfjH80gUwCLcB/s1600/o_db.png> Any Suggestions? -- --- 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.
