[
https://issues.apache.org/jira/browse/PHOENIX-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16451450#comment-16451450
]
James Taylor commented on PHOENIX-4701:
---------------------------------------
[~an...@apache.org] - I've attached a wip2 patch that writes using Phoenix APIs
so that you can have a composite row key to allow querying, use salting, have
the table be column encoded, and potentially add secondary indexes. It needs a
bit more work, though, because the column values are set in various places for
the same query. I think we should log a single line per query - we can cover
the failed/exception case and the success case. I think having so many
individual Put RPCs won't scale well and even if it did, having a table with
only the query ID in the PK means every query would be a full table scan.
Would you have any cycles to take my patch further? Barring that, have we
documented this yet? Perhaps we can just call this beta and let users know that
the table structure will likely change in the future.
Your thoughts would be valuable too, [~elserj].
> Improve schema of SYSTEM.LOG table
> ----------------------------------
>
> Key: PHOENIX-4701
> URL: https://issues.apache.org/jira/browse/PHOENIX-4701
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: James Taylor
> Priority: Major
> Fix For: 4.14.0, 5.0.0
>
> Attachments: PHOENIX-4701_wip1.patch, PHOENIX-4701_wip2.patch
>
>
> If possible, the SYSTEM.LOG table would benefit greatly (3-5x perf gain)
> from being declared as immutable with a column encoding of 1 byte and a
> storage format of SINGLE_CELL_ARRAY_WITH_OFFSETS.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
