You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When an avro schema (avsc file) contains any custom properties for any of its elements, the custom properties will appear in the custom properties section of the form. However, when the file is saved after any edits, these custom properties get stripped from the file.
For example, if we had a schema file containing a custom property that tags fields as containing personal identifying information ("pii" : "true"):
...
"fields" : [ {
"name" : "id",
"type" : "string"
}, {
"name" : "fname",
"type" : "string", "pii" : "true"
}, {
"name" : "lname",
"type" : "string", "pii" : "true"
}, {
...
Although the custom properties will appear in the schema editor, when you save the file after any changes the custom properties will no longer appear:
...
"fields" : [ {
"name" : "id",
"type" : "string"
}, {
"name" : "fname",
"type" : "string",
}, {
"name" : "lname",
"type" : "string",
}, {
...
The text was updated successfully, but these errors were encountered:
When an avro schema (avsc file) contains any custom properties for any of its elements, the custom properties will appear in the custom properties section of the form. However, when the file is saved after any edits, these custom properties get stripped from the file.
For example, if we had a schema file containing a custom property that tags fields as containing personal identifying information ("pii" : "true"):
...
"fields" : [ {
"name" : "id",
"type" : "string"
}, {
"name" : "fname",
"type" : "string",
"pii" : "true"
}, {
"name" : "lname",
"type" : "string",
"pii" : "true"
}, {
...
Although the custom properties will appear in the schema editor, when you save the file after any changes the custom properties will no longer appear:
...
"fields" : [ {
"name" : "id",
"type" : "string"
}, {
"name" : "fname",
"type" : "string",
}, {
"name" : "lname",
"type" : "string",
}, {
...
The text was updated successfully, but these errors were encountered: