phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xu Cang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-5034) Log all critical statements in SYSTEM.LOG table.
Date Sat, 01 Dec 2018 07:43:00 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-5034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Xu Cang updated PHOENIX-5034:
-----------------------------
    Attachment: PHOENIX-5034-4.x-HBase-1.3.004.patch

> Log all critical statements in SYSTEM.LOG table.
> ------------------------------------------------
>
>                 Key: PHOENIX-5034
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5034
>             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
>
>
> 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
(v7.6.3#76005)

Mime
View raw message