BigQuery: update signature for ML model access to label/feature columns. - #5732
Conversation
This is a breaking change to a @BetaApi within BigQuery. It swaps in a new veneer StandardSQLField type in place of the underlying discovery type for getting information about the feature and label columns from ML models, which was functionality introduced in: googleapis#5214
Codecov Report
@@ Coverage Diff @@
## master #5732 +/- ##
============================================
- Coverage 47.09% 46.71% -0.39%
+ Complexity 25063 23629 -1434
============================================
Files 2389 2389
Lines 259743 254614 -5129
Branches 29404 29257 -147
============================================
- Hits 122320 118934 -3386
+ Misses 128462 127626 -836
+ Partials 8961 8054 -907
Continue to review full report at Codecov.
|
The tests accessed the data transitively without declaring the intermediate types. The types changed but the getter names didn't. Ex: |
|
|
||
| @Override | ||
| Builder setLabelColumns(List<StandardSqlField> labelColumnList) { | ||
| Builder setLabelColumns(List<StandardSQLField> labelColumnList) { |
There was a problem hiding this comment.
Where is this annotated with @BetaApi? Just want to make sure we don't introduce a breaking change to something that wasn't labeled as such.
There was a problem hiding this comment.
The feature represents readonly properties provided by the BQ backend, so I marked it as BetaApi on the public getters in ModelInfo. The internal builder was not annotated this way.
There was a problem hiding this comment.
Ah, sorry didn't realize this wasn't a public method. SGTM.
This is a breaking change to a @BetaApi within BigQuery.
It swaps in a new veneer StandardSQLField type in place of the underlying
discovery type for getting information about the feature and label columns
from ML models, which was functionality introduced in:
#5214