Community
Participate
Working Groups
I see two ways we can accomplish this, by running the whole algorithm in the database through SQL queries (like we do in Time based correlation today) or by querying only the attributes that are required for the correlation (much faster than loading objects completely).
Use the container proxies from EMF 2.2.
Please raise this to a P1 and add the details from the meeting with Geiner.
As mentioned above by making use of containment proxies, we will also improve the load page time (the current behavior trigger the load of all the objects under a Common Base Event object).
How would you run log analysis using XPath expressions using the mechanism that you have just described?
Theme: Scaling Up
We need to add support for SQL Queries instead. This provides a more generic architecture.
This feature will cover the following (in sync with the URL): - make use of EMF containment proxies to defer loading the containment children of an object until they are required. - implement the analysis algorithm using backen storage capabilities (SQL) and when this is not possible make use of the existing query infrastructure to retreive only the features (attributes) that are required in the analysis instead of full objects.
Fixed.
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this originator of this enhancement/defect has an inactive Bugzilla account and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.