[
https://issues.apache.org/jira/browse/PHOENIX-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15592629#comment-15592629
]
James Taylor commented on PHOENIX-3392:
---------------------------------------
Do you think you'd have any spare cycles to take a look, [~maryannxue]? This is
the last failing test on the encodecolumns2 branch. [~samarthjain] will be able
to answer any detailed questions you may have.
> SortMergeJoinIT#testSubJoin[0] is failing with encodecolumns2 branch
> --------------------------------------------------------------------
>
> Key: PHOENIX-3392
> URL: https://issues.apache.org/jira/browse/PHOENIX-3392
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
>
> The SortMergeJoinIT#testSubJoin[0] is failing with encodecolumns2 branch. To
> repro, checkout the encodecolumns2 branch and run the SortMergeJoinIT tests.
> Here's the stack trace is here:
> https://builds.apache.org/job/Phoenix-encode-columns/16/testReport/org.apache.phoenix.end2end/SortMergeJoinIT/testSubJoin_0_/
> The basic idea of column encoding over mutable tables is that we take control
> of the column qualifier name, storing in PColumn the mapping of real column
> name to column qualifier name. We use serialized integers as the column
> qualifier names so that we can do positional lookups into the List<Cell> we
> get back from HBase APIs. There are a few "reserved" column qualifiers for
> things like our empty key value, etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
