public class ExecutionPhaseEvent extends ExecutionEvent
A phase begins when Mondrian has tried to execute a statement and has determined that it needs cell values in order to give the complete, correct result. It generates one or more SQL statements to load those cells, and starts a new phase. Most MDX statements can be completed in 3 or fewer phases.
Modifier and Type | Field and Description |
---|---|
int |
hitCount |
int |
missCount |
int |
pendingCount |
int |
phase |
connectionId, executionId, serverId, statementId
Constructor and Description |
---|
ExecutionPhaseEvent(long timestamp,
int serverId,
int connectionId,
long statementId,
long executionId,
int phase,
int hitCount,
int missCount,
int pendingCount)
Creates an ExecutionPhaseEvent.
|
Modifier and Type | Method and Description |
---|---|
<T> T |
accept(Visitor<T> visitor)
Dispatches a call to the appropriate
visit method on
Visitor . |
String |
toString() |
public final int phase
public final int hitCount
public final int missCount
public final int pendingCount
public ExecutionPhaseEvent(long timestamp, int serverId, int connectionId, long statementId, long executionId, int phase, int hitCount, int missCount, int pendingCount)
timestamp
- TimestampserverId
- Server idconnectionId
- Connection idstatementId
- Statement idexecutionId
- Execution idphase
- PhasehitCount
- Cache hits this phasemissCount
- Cache misses this phasependingCount
- Cache entries hit but not ready this phaseCopyright © 2019 Hitachi Vantara. All rights reserved.