You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Alex Rodoni (JIRA)" <ji...@apache.org> on 2018/08/29 00:48:00 UTC
[jira] [Closed] (IMPALA-7500) Clarify workaround for IMPALA-635
[ https://issues.apache.org/jira/browse/IMPALA-7500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rodoni closed IMPALA-7500.
-------------------------------
Resolution: Fixed
Fix Version/s: Impala 3.1.0
> Clarify workaround for IMPALA-635
> ---------------------------------
>
> Key: IMPALA-7500
> URL: https://issues.apache.org/jira/browse/IMPALA-7500
> Project: IMPALA
> Issue Type: Bug
> Components: Docs
> Reporter: Tim Armstrong
> Assignee: Alex Rodoni
> Priority: Major
> Fix For: Impala 3.1.0
>
>
> The release note for IMPALA-635 needs a small tweak. The workaround isn't clear that the schema needs to be changed *before* an Avro file is written.
> If a file was written with the old schema then the schema is embedded in the file and Impala will still hit IMPALA-635 when reading the schema from the file.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org