You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@avro.apache.org by "Jim Huang (Jira)" <ji...@apache.org> on 2020/02/12 19:24:00 UTC

[jira] [Updated] (AVRO-2739) schema evolution support for case-sensitive to case-insensitive schema change

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

Jim Huang updated AVRO-2739:
----------------------------
    Description: In a scenario where my upstream sources changed the case-sensitivity treatment in either key or value (string & enum types) of the schema.  Can this be handled by the current schema evolution API to normalize the data for schema changes that went from case-sensitive --> all UPPERCASE or lowercase?  Your opinion and views are appreciated even if this feature does not exist or should or could be created.    (was: In a scenario where my upstream sources changed the case-sensitivity treatment in either key or value (string type) of the schema.  Can this be handled by the current schema evolution API to normalize the data for schema changes that went from case-sensitive --> all UPPERCASE or lowercase?  Your opinion and views are appreciated even if this feature does not exist or should or could be created.  )

> schema evolution support for case-sensitive to case-insensitive schema change
> -----------------------------------------------------------------------------
>
>                 Key: AVRO-2739
>                 URL: https://issues.apache.org/jira/browse/AVRO-2739
>             Project: Apache Avro
>          Issue Type: Wish
>            Reporter: Jim Huang
>            Priority: Minor
>
> In a scenario where my upstream sources changed the case-sensitivity treatment in either key or value (string & enum types) of the schema.  Can this be handled by the current schema evolution API to normalize the data for schema changes that went from case-sensitive --> all UPPERCASE or lowercase?  Your opinion and views are appreciated even if this feature does not exist or should or could be created.  



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