[ https://issues.apache.org/jira/browse/KYLIN-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15587203#comment-15587203 ]
Dayue Gao commented on KYLIN-2105: ---------------------------------- commit https://github.com/apache/kylin/commit/db09f5f9cae5a3d3ff731221cbb1c026da4f4e41 to master. QueryID format "yyyyMMdd_HHmmss_project_xxxxxx" * "yyyyMMdd_HHmmss": query submit time * "project": which project the query is submitted to * "xxxxxx": six random generated base26 (a-z) characters Need a threadlocal context to pass QueryID to storage layer, use BackdoorToggles for now. Maybe we should rename BackdoorToggles to QueryContext? Add a field to coprocessor protobuf interface, which is backward compatible with 1.5.4. > add QueryId > ----------- > > Key: KYLIN-2105 > URL: https://issues.apache.org/jira/browse/KYLIN-2105 > Project: Kylin > Issue Type: Sub-task > Components: Query Engine, Storage - HBase > Affects Versions: v1.6.0 > Reporter: Dayue Gao > Assignee: Dayue Gao > Labels: patch > Fix For: v1.6.0 > > > * for each query, generate an unique id. > * the id could describe some context information about the query, like start > time, project name, etc. > * for query thread, we could use query id as the name of the thread. As long > as user logs thread's name, he can grep query log by query id afterwards. > * pass query id to coprocessor, so that query id gets logged both in query > server and region server. > * BadQueryDetector should also log query id -- This message was sent by Atlassian JIRA (v6.3.4#6332)