You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Aditya Toomula (Jira)" <ji...@apache.org> on 2020/03/01 16:29:00 UTC

[jira] [Resolved] (SAMZA-2415) Samza-Sql: Fix AvroRelConverter to only consider cached schema while populating SamzaSqlRelRecord for all the nested records.

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

Aditya Toomula resolved SAMZA-2415.
-----------------------------------
    Resolution: Fixed

> Samza-Sql: Fix AvroRelConverter to only consider cached schema while populating SamzaSqlRelRecord for all the nested records.
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SAMZA-2415
>                 URL: https://issues.apache.org/jira/browse/SAMZA-2415
>             Project: Samza
>          Issue Type: Bug
>            Reporter: Aditya Toomula
>            Assignee: Aditya Toomula
>            Priority: Major
>             Fix For: 1.4
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently, relRecord is populated with cached schema only at the top-level fields while the nested fields are populated with the schema of the incoming record. This ticket is to fix that inconsistency and always consider cached schema (schema that is fetched when the job starts).
> As a by-product of considering only cached schema, Sql job will keep running even though the input schema has evolved, let's say a new field is added. We will keep dropping the new field. As a separate effort, we need to consider adding metrics to flag whenever we detect that the input schema has evolved.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)