phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xu Cang (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-5034) Log all critical statements in SYSTEM.LOG table.
Date Mon, 03 Dec 2018 22:21:00 GMT


Xu Cang commented on PHOENIX-5034:

thanks, [~karanmehta93] and [~elserj]

Uploaded .005 patch to use statement now.  Yeah, the purpose for this is to track DDL only.
(DROP table and ALTER table)

For DML, in my opinion, it's good to keep the current approach which only logs a small percentage
of them. (by default 1%)


> Log all critical statements in SYSTEM.LOG table.
> ------------------------------------------------
>                 Key: PHOENIX-5034
>                 URL:
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Xu Cang
>            Assignee: Xu Cang
>            Priority: Minor
>         Attachments: PHOENIX-5034-4.x-HBase-1.3.001.patch, PHOENIX-5034-4.x-HBase-1.3.002.patch,
PHOENIX-5034-4.x-HBase-1.3.003.patch, PHOENIX-5034-4.x-HBase-1.3.004.patch, PHOENIX-5034-4.x-HBase-1.3.005.patch
> In production, sometimes engineers see table got dropped unexpectedly. It's not easy
to SCAN raw table from HBase itself to understand what happened and when the table get dropped.
> Since we already have SYSTEM.LOG query log facility in Phoenix that sampling query statement
(log 1% statement by default). It's good to always log critical statements such as "DROP"
or "ALTER" statements.

This message was sent by Atlassian JIRA

View raw message