1.1.1

scan_type node_details
WHERE : ((F.FLIGHT_ID = FA.FLIGHT_ID) and true)
3 rows selected
You can see that the table scan is now replaced by a more efficient INDEXSCAN task in the join. Although
the query on the original, unindexed table completed very quickly, note that the index scan took less than a
millisecond to complete, whereas the original table scan required over 9 milliseconds. This performance
improvement is magnified as the number of rows increases, so always ensure that indexes are used when
possible for long-running queries.
Query Plan Codes
SQLFire may add the following codes to a generated query plan. All times reported in the plan are in milliseconds.
The following codes apply to the query coordinator (the SQLFire member that distributes a query to other data
store members and processes the results).
DescriptionQuery Plan Code
The total time spent processing the query on the data store members.DISTRIBUTION-END
The time spent grouping rows on the query coordinator. This code
is displayed only if the query contains an GROUP BY clause and
the query was processed over multiple table partitions.
GROUPED-ITERATION
The time spent resorting rows on the query coordinator. This code
is displayed only if the query contains an ORDER BY clause and
the query was processed over multiple table partitions.
ORDERED-ITERATION
The time spent evaluating outer joins after receiving rows from other
members.
OUTER-JOIN-ITERATION
QUERY-SCATTER is the top-level code that organizes all tasks
associated with sending queries from the query coordinator and
QUERY-SCATTER
receiving and processing results on the coordinator. The execute time
reported for QUERY-SCATTER is the total, aggregate time of all
the subordinate tasks. QUERY-SCATTER lists the SQLFire members
to which the query was distributed; it does not list the query
coordinator member.
The network time required to send the query, as well as the target
member. This is an "OUT" operation from the perspective of the
QUERY-SEND
query coordinator. A separate QUERY-SEND code is displayed for
each data store that receives the query.
An atomic "get" operation in the GemFire component.REGION-GET
An atomic "getall" operation in the GemFire component.REGION-GETALL
An atomic "put" operation in the GemFire component.REGION-PUT
An atomic "putall" operation in the GemFire component.REGION-PUTALL
The network time required to receive the results from data stores
back to the query coordinator. This is an "IN" operation from the
RESULT-RECEIVE
perspective of the query coordinator. A separate RESULT-RECEIVE
code is displayed for each data store that processes the query.
Shows the total time spent batching up results from the target
member. This is an "IN" operation from the perspective of the query
RESULT-HOLDER
coordinator. RESULT-HOLDER displays the number of rows
returned from the specified data store member. A separate
RESULT-HOLDER code is displayed for each data store that
processes the query.
vFabric SQLFire User's Guide276
Managing and Monitoring vFabric SQLFire