Commit a7e9ebd
authored
Remove output-only fields from JSON schema (#3878)
## Changes
Instead of marking output-only fields with `doNotSuggest` (see #3599),
completely exclude them from the schema.
This is done by:
- Marking fields as `OUTPUT_ONLY` in `FieldBehaviors` during annotation
- Adding removeOutputOnlyFields transformation to remove these fields
- Also removing them from required lists
This removes 77 output-only properties from the schema.
## Why
Output-only field must not show up in the generated code for Python
support.
## Tests
A few fields were removed from the Python code.1 parent 1f8ca6c commit a7e9ebd
File tree
6 files changed
+39
-457
lines changed- bundle
- internal/schema
- schema
- experimental/python/databricks/bundles/pipelines
- _models
6 files changed
+39
-457
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
139 | 139 | | |
140 | 140 | | |
141 | 141 | | |
142 | | - | |
| 142 | + | |
143 | 143 | | |
144 | 144 | | |
145 | 145 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
145 | 145 | | |
146 | 146 | | |
147 | 147 | | |
| 148 | + | |
| 149 | + | |
| 150 | + | |
| 151 | + | |
| 152 | + | |
| 153 | + | |
| 154 | + | |
| 155 | + | |
| 156 | + | |
| 157 | + | |
| 158 | + | |
| 159 | + | |
| 160 | + | |
| 161 | + | |
| 162 | + | |
| 163 | + | |
| 164 | + | |
| 165 | + | |
| 166 | + | |
| 167 | + | |
| 168 | + | |
| 169 | + | |
| 170 | + | |
| 171 | + | |
| 172 | + | |
| 173 | + | |
| 174 | + | |
| 175 | + | |
| 176 | + | |
| 177 | + | |
| 178 | + | |
| 179 | + | |
| 180 | + | |
| 181 | + | |
| 182 | + | |
| 183 | + | |
| 184 | + | |
148 | 185 | | |
149 | 186 | | |
150 | 187 | | |
| |||
189 | 226 | | |
190 | 227 | | |
191 | 228 | | |
| 229 | + | |
192 | 230 | | |
193 | 231 | | |
194 | 232 | | |
| |||
0 commit comments