[ 
https://issues.apache.org/jira/browse/AVRO-3547?focusedWorklogId=785047&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-785047
 ]

ASF GitHub Bot logged work on AVRO-3547:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 27/Jun/22 11:42
            Start Date: 27/Jun/22 11:42
    Worklog Time Spent: 10m 
      Work Description: martin-g commented on code in PR #1736:
URL: https://github.com/apache/avro/pull/1736#discussion_r907195474


##########
lang/c++/impl/NodeImpl.cc:
##########
@@ -83,6 +83,17 @@ std::ostream &operator<<(std::ostream &os, indent x) {
     return os;
 }
 
+void printCustomFields(const CustomFields& customFields, int depth,
+                       std::ostream &os) {
+    std::map<std::string, json::Entity>::const_iterator iter =
+        customFields.fields().begin();
+    while (iter != customFields.fields().end()) {
+      os << ",\n" << indent(depth);

Review Comment:
   ```suggestion
         os << "," << endl  << indent(depth);
   ```





Issue Time Tracking
-------------------

    Worklog Id:     (was: 785047)
    Time Spent: 1h 20m  (was: 1h 10m)

> support custom attribute at field level
> ---------------------------------------
>
>                 Key: AVRO-3547
>                 URL: https://issues.apache.org/jira/browse/AVRO-3547
>             Project: Apache Avro
>          Issue Type: Improvement
>          Components: c++
>            Reporter: Nilesh Yadav
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Custom attributes are allowed at field level as per Avro specification : 
> [https://avro.apache.org/docs/current/spec.html#schemas|https://www.google.com/url?q=https://avro.apache.org/docs/current/spec.html%23schemas&sa=D&source=buganizer&usg=AOvVaw3JfXMgFX6Eq0Fd0TjDzgb1]
>  
> But Avro c++ implementation does not support custom attribute at field level.
> e.g. following schema cannot be parsed correctly due to presence of "sqlName" 
> attribute.
> {
>     'doc': 'weather warning',
>     'name': 'weather',
>     'type': 'record',
>     'fields': [
>     {
>         'name': 'station',
>         'type':'string',
>         'sqlName':'abc-@12'
>     },
>     {
>         'name': 'time',
>         'type':'long',
>         'sqlName': '用户名'
>     }]
> }
> Update implementation to support custom attribute at field level.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to