[ https://issues.apache.org/jira/browse/IMPALA-12426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Fehr updated IMPALA-12426: -------------------------------- Description: Implement a way of querying (via SQL) information about completed queries/ddls/dmls. Design details: 1. New Coordinator Startup Flags: * store_query_history -- string, value of "impala" stores the query history table as an Iceberg table, allows for future expansion to using Kudu as the table storage engine * query_history_table_name -- string, name of the table where query history will be stored, can be fully qualified with a database name (e.g. "mydb.my_table") or can be just the table name (e.g. "my_table") in which case the table will be stored in the "information" database, defaults to "information.query_history" * query_history_write_duration -- number, seconds to wait before inserting completed queries into the query history table, allows for batching inserts to avoid lots of small files, value of 0 indicates immediate insert with no batching, default 300 2. Not all queries will be written to this table. Use/set/get queries was:Implement a way of querying (via SQL) information about completed queries. > SQL Interface to Completed Queries > ---------------------------------- > > Key: IMPALA-12426 > URL: https://issues.apache.org/jira/browse/IMPALA-12426 > Project: IMPALA > Issue Type: Improvement > Components: Backend, be > Reporter: Jason Fehr > Assignee: Jason Fehr > Priority: Major > Labels: impala, workload-management > > Implement a way of querying (via SQL) information about completed > queries/ddls/dmls. > Design details: > 1. New Coordinator Startup Flags: > * store_query_history -- string, value of "impala" stores the query > history table as an Iceberg table, allows for future expansion to using Kudu > as the table storage engine > * query_history_table_name -- string, name of the table where query > history will be stored, can be fully qualified with a database name (e.g. > "mydb.my_table") or can be just the table name (e.g. "my_table") in which > case the table will be stored in the "information" database, defaults to > "information.query_history" > * query_history_write_duration -- number, seconds to wait before > inserting completed queries into the query history table, allows for batching > inserts to avoid lots of small files, value of 0 indicates immediate insert > with no batching, default 300 > 2. Not all queries will be written to this table. Use/set/get queries -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org