[jira] [Resolved] (CALCITE-1458) ColumnValue not backwards compatibile after CALCITE-1040

["Josh Elser (JIRA)" <ji...@apache.org>]

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

Josh Elser resolved CALCITE-1458.
---------------------------------
    Resolution: Fixed

Resolved in https://git-wip-us.apache.org/repos/asf?p=calcite.git;a=commit;h=6010ce10faba4457ffdc0809bff981bebba5237b

> ColumnValue not backwards compatibile after CALCITE-1040
> --------------------------------------------------------
>
>                 Key: CALCITE-1458
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1458
>             Project: Calcite
>          Issue Type: Bug
>          Components: avatica
>    Affects Versions: 1.6.0, avatica-1.8.0, avatica-1.7.1, avatica-1.7.0
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Blocker
>             Fix For: avatica-1.9.0
>
>
> [~onpduo] was nice enough to help me debug an issue using the C# driver against Avatica 1.8.1. We could see that a record was being placed into the database, but the C# driver wasn't returning the value.
> After inspecting the server, I could see that the row was being returned by the server. Still the client claimed to not know about the value in the row.
> Turns out, this was a botched backwards-compatibility issue introduced by CALCITE-1040. When the array_value and scalar_value fields were introduced, the original value field stopped having the values set in it. This caused the C# driver, which was still using that (now deprecated) field to stop seeing any records.
> A simple fix to start adding the values for the row into that deprecated field seems to have fixed the issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)