[
https://issues.apache.org/jira/browse/PHOENIX-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Fernando reopened PHOENIX-3421:
-----------------------------------
[~giacomotaylor] Unfortunately we discovered today that even with this fix we
have a significant backwards compatibility issue that will impact our
production code.
Our code that generates Phoenix SQL works with 4.8.0 client and server but with
the 4.8.0 client and 4.8.1 or 4.9 server jar our code that generates Phoenix
queries no longer works due to this issue. Can we have a fix that is backwards
compatible with the 4.8.0 client and our code line that runs with that. This
will prevent a breakage while have an older client and new server jar.
[[email protected]] Can you add some info about the specific method whose
returns values changes that is causing backwards compatibility to be broken?
> Column name lookups fail when on an indexed table
> -------------------------------------------------
>
> Key: PHOENIX-3421
> URL: https://issues.apache.org/jira/browse/PHOENIX-3421
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.8.0
> Reporter: Cody Marcel
> Assignee: James Taylor
> Fix For: 4.9.0
>
> Attachments: DebuggerWindow.png, PHOENIX-3421.patch
>
>
> Using an index the lookup for encoded values fails.
> This happens on tables when using an index.
> The conflict is essentially between the two methods below. The pkColsList
> create by getPkColsDataTypesForSql() returns column names without a ":", but
> the encodeValues() method does a lookup on PTable for the column and cannot
> find it.
> PhoenixRuntime.getPkColsDataTypesForSql(pkColsList, dataTypesList, queryPlan,
> connection, true);
> PhoenixRuntime.encodeValues(connection, queryPlanTableName, objects ,
> pkColsList);
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
