Academia.eduAcademia.edu

Figure 4 – uploaded by Computer Science & Information Technology (CS & IT) Computer Science Conference Proceedings (CSCP)

See full PDFdownloadDownload figure
Figure 4: Architecture 4.1. Architecture 4.1.1. Store

Figure 4 Architecture 4.1. Architecture 4.1.1. Store

Related Figures (9)

Figure 1: Class Node Structure In an object-oriented environment, application is modeled as classes with certain properties anc behavior. An object/instance of such a class, with which the user interacts, is defined as Clas: Node. For e.g. an online booking system will have objects of type Ticket, Place, Person etc. A blogging application will have objects of type Blog, Author, Topic etc. Graphite looks into the structure of a Class Node to formulate queries that a user might want to ask about objects of thi: class. Each class node has a unique name and is represented as a node in the underlying store which has an outward ‘name’ link pointing to a string. For e.g. class — ‘Person’ (see figure 1) is represented as shown below:
Figure 1: Class Node Structure In an object-oriented environment, application is modeled as classes with certain properties anc behavior. An object/instance of such a class, with which the user interacts, is defined as Clas: Node. For e.g. an online booking system will have objects of type Ticket, Place, Person etc. A blogging application will have objects of type Blog, Author, Topic etc. Graphite looks into the structure of a Class Node to formulate queries that a user might want to ask about objects of thi: class. Each class node has a unique name and is represented as a node in the underlying store which has an outward ‘name’ link pointing to a string. For e.g. class — ‘Person’ (see figure 1) is represented as shown below:
Figure 3: Object Node Structure An instance of a class node is defined as Object Node. Each object is represented by a node and has outward property links whose name is same as that of the property name. As shown in figure 3, a domain object named ‘ram’ has a property named ‘location’ whose value is ‘pune’.
Figure 3: Object Node Structure An instance of a class node is defined as Object Node. Each object is represented by a node and has outward property links whose name is same as that of the property name. As shown in figure 3, a domain object named ‘ram’ has a property named ‘location’ whose value is ‘pune’.
Figure 2: Property Node Structure For e.g. Person class (see figure 2) will have properties such as email, location etc.
Figure 2: Property Node Structure For e.g. Person class (see figure 2) will have properties such as email, location etc.
4.1.2. Indexer As seen in the Figure 5 ‘Book’ (#22) and ‘Author’ (#23) are class nodes and their properties ‘author’ (#24) and ‘fullname’ (#21) respectively are property nodes in Layer2. Both the class node and the property node are linked (bonded) by the ‘name’ link to the string node residing in Layerl. Class node is linked by ‘domain’ link to their respective property nodes, for e.g. ‘Book’ (#22) & ‘author’ (#24) are linked and ‘Author’ (#23) & ‘fullname’ (#21) are linked. Property node is linked by ‘range’ link to their respective type (class) node, for e.g. ‘author’ (#24) and ‘Author’ (#23) are linked. Object nodes ‘C++’ (#31) and ‘Stroustrup’ (#32) reside in Layer3. These object nodes are linked to nodes, in Layer! by name link, in Layer2 by type ink, in Layer3 by property links. All links except ‘name’ and ‘type’ are created in adherence with the links of class node (instance type) and property nodes in Layer2.
4.1.2. Indexer As seen in the Figure 5 ‘Book’ (#22) and ‘Author’ (#23) are class nodes and their properties ‘author’ (#24) and ‘fullname’ (#21) respectively are property nodes in Layer2. Both the class node and the property node are linked (bonded) by the ‘name’ link to the string node residing in Layerl. Class node is linked by ‘domain’ link to their respective property nodes, for e.g. ‘Book’ (#22) & ‘author’ (#24) are linked and ‘Author’ (#23) & ‘fullname’ (#21) are linked. Property node is linked by ‘range’ link to their respective type (class) node, for e.g. ‘author’ (#24) and ‘Author’ (#23) are linked. Object nodes ‘C++’ (#31) and ‘Stroustrup’ (#32) reside in Layer3. These object nodes are linked to nodes, in Layer! by name link, in Layer2 by type ink, in Layer3 by property links. All links except ‘name’ and ‘type’ are created in adherence with the links of class node (instance type) and property nodes in Layer2.
Figure 6: Diverging Query Result Structure Diverging Query: Following the name link, if the query advisor lands on Layer3, it produces a diverging query. This type of query is called diverging query because the graph structure that gets outputted after execution is of diverging nature as seen in figure 6. The output nodes for such queries are the nodes at level 1.
Figure 6: Diverging Query Result Structure Diverging Query: Following the name link, if the query advisor lands on Layer3, it produces a diverging query. This type of query is called diverging query because the graph structure that gets outputted after execution is of diverging nature as seen in figure 6. The output nodes for such queries are the nodes at level 1.
Figure 7: Converging Query Result Structure Converging Query: Following the name link, if the query advisor lands on Layer2, it produces a converging query. The graph structure that gets outputted is converging in nature as seen in figure 7 and hence the name. Nodes of level 0 are outputted for such queries.
Figure 7: Converging Query Result Structure Converging Query: Following the name link, if the query advisor lands on Layer2, it produces a converging query. The graph structure that gets outputted is converging in nature as seen in figure 7 and hence the name. Nodes of level 0 are outputted for such queries.
4.1.4. ObjectSearcher Object searcher is primarily responsible for searching nodes of Layer3 that satisfies a given query. It does so by executing the Machine Readable Query extracted from the corresponding Query Stack. Two lists are returned when a Machine Readable Query gets executed:
4.1.4. ObjectSearcher Object searcher is primarily responsible for searching nodes of Layer3 that satisfies a given query. It does so by executing the Machine Readable Query extracted from the corresponding Query Stack. Two lists are returned when a Machine Readable Query gets executed:
Computer Science & Information Technology (CS & IT)
Computer Science & Information Technology (CS & IT)
Related topics:
AlgorithmsObject Oriented ProgrammingGraph Search
580 California St., Suite 400
San Francisco, CA, 94104
© 2025 Academia. All rights reserved