[
https://issues.apache.org/jira/browse/PHOENIX-2715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell reopened PHOENIX-2715:
-------------------------------------
Looks like a minor addendum is needed, at least for 0.98, some test failures
because SYSTEM.LOG is unexpected
{noformat}
[ERROR] SystemCatalogCreationOnConnectionIT.testMigrateSysCatCreateOthers:269
expected:<[SYSTEM:FUNCTION, SYSTEM:STATS, SYSTEM:MUTEX, SYSTEM:CATALOG,
SYSTEM.LOG, SYSTEM:SEQUENCE]> but was:<[SYSTEM:FUNCTION, SYSTEM:STATS,
SYSTEM:MUTEX, SYSTEM:LOG, SYSTEM:CATALOG, SYSTEM:SEQUENCE]>
[ERROR] SystemCatalogCreationOnConnectionIT.testMigrateToSystemNamespace:199
expected:<[SYSTEM:FUNCTION, SYSTEM:STATS, SYSTEM:MUTEX, SYSTEM:CATALOG,
SYSTEM.LOG, SYSTEM:SEQUENCE]> but was:<[SYSTEM:FUNCTION, SYSTEM:STATS,
SYSTEM:MUTEX, SYSTEM:LOG, SYSTEM:CATALOG, SYSTEM:SEQUENCE]>
[ERROR]
SystemCatalogCreationOnConnectionIT.testMigrateToSystemNamespaceAndUpgradeSysCat:288
expected:<[SYSTEM:FUNCTION, SYSTEM:STATS, SYSTEM:MUTEX, SYSTEM:CATALOG,
SYSTEM.LOG, SYSTEM:SEQUENCE]> but was:<[SYSTEM:FUNCTION, SYSTEM:STATS,
SYSTEM:MUTEX, SYSTEM:LOG, SYSTEM:CATALOG, SYSTEM:SEQUENCE]>
[ERROR]
SystemCatalogCreationOnConnectionIT.testTablesExistInconsistentNSMappingFails:298->firstConnectionNSMappingServerEnabledClientEnabled:557
expected:<[SYSTEM:FUNCTION, SYSTEM:STATS, SYSTEM:MUTEX, SYSTEM:CATALOG,
SYSTEM.LOG, SYSTEM:SEQUENCE]> but was:<[SYSTEM:FUNCTION, SYSTEM:STATS,
SYSTEM:MUTEX, SYSTEM:LOG, SYSTEM:CATALOG, SYSTEM:SEQUENCE]>
[ERROR]
SystemCatalogCreationOnConnectionIT.testUpgradeAttempted:210->firstConnectionNSMappingServerEnabledClientEnabled:557
expected:<[SYSTEM:FUNCTION, SYSTEM:STATS, SYSTEM:MUTEX, SYSTEM:CATALOG,
SYSTEM.LOG, SYSTEM:SEQUENCE]> but was:<[SYSTEM:FUNCTION, SYSTEM:STATS,
SYSTEM:MUTEX, SYSTEM:LOG, SYSTEM:CATALOG, SYSTEM:SEQUENCE]>
[ERROR]
SystemCatalogCreationOnConnectionIT.testUpgradeNotAllowed:231->firstConnectionNSMappingServerEnabledClientEnabled:557
expected:<[SYSTEM:FUNCTION, SYSTEM:STATS, SYSTEM:MUTEX, SYSTEM:CATALOG,
SYSTEM.LOG, SYSTEM:SEQUENCE]> but was:<[SYSTEM:FUNCTION, SYSTEM:STATS,
SYSTEM:MUTEX, SYSTEM:LOG, SYSTEM:CATALOG, SYSTEM:SEQUENCE]>
{noformat}
> Query Log
> ---------
>
> Key: PHOENIX-2715
> URL: https://issues.apache.org/jira/browse/PHOENIX-2715
> Project: Phoenix
> Issue Type: New Feature
> Reporter: Nick Dimiduk
> Assignee: Ankit Singhal
> Priority: Major
> Fix For: 4.14.0, 5.0.0
>
> Attachments: PHOENIX-2715.patch, PHOENIX-2715_master.patch,
> PHOENIX-2715_master_V1.patch, PHOENIX-2715_master_V2.patch
>
>
> One useful feature of other database systems is the query log. It allows the
> DBA to review the queries run, who's run them, time taken, &c. This serves
> both as an audit and also as a source of "ground truth" for performance
> optimization. For instance, which columns should be indexed. It may also
> serve as the foundation for automated performance recommendations/actions.
> What queries are being run is the first piece. Have this data tied into
> tracing results and perhaps client-side metrics (PHOENIX-1819) becomes very
> useful.
> This might take the form of clients writing data to a new system table, but
> other implementation suggestions are welcome.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
