GLOBAL_OPERATOR_EC_HISTORY
GLOBAL_OPERATOR_EC_HISTORY is used to query recorded information about operators of Extension Connector jobs that have been executed. The current feature is a lab feature. Contact Huawei technical support before using it.
Name |
Type |
Description |
---|---|---|
queryid |
bigint |
Internal query ID used for Extension Connector statement execution |
plan_node_id |
integer |
Plan node ID of the execution plan of an Extension Connector operator |
start_time |
timestamp with time zone |
Time when the Extension Connector operator starts to process the first data record |
duration |
bigint |
Total execution time of the Extension Connector operator (unit: ms) |
tuple_processed |
bigint |
Number of elements returned by the Extension Connector operator |
min_peak_memory |
integer |
Minimum peak memory used by the Extension Connector operator on all DNs (unit: MB) |
max_peak_memory |
integer |
Maximum peak memory used by the Extension Connector operator on all DNs (unit: MB) |
average_peak_memory |
integer |
Average peak memory used by the Extension Connector operator on all DNs (unit: MB) |
ec_status |
text |
Status of the Extension Connector job |
ec_execute_datanode |
text |
Name of the DN executing the Extension Connector job |
ec_dsn |
text |
DSN used by the Extension Connector job |
ec_username |
text |
Username used by the Extension Connector job to access a remote cluster. This parameter is null if the remote cluster type is SPARK. |
ec_query |
text |
Statement sent by the Extension Connector job to a remote cluster |
ec_libodbc_type |
text |
Type of the unixODBC driver used by the Extension Connector job |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot