Details
-
Type: Bug
-
Status: Resolved
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 0.15.0
-
Fix Version/s: 0.15.0
-
Component/s: None
-
Labels:None
Description
After CDK-496, it's possible to load a view using a URI that has constraints and to end up having incompatible types for the constraint values and the field values. Where this shows up today is that it will create a String for the constraint, but if the user loaded the view with type GenericData.Record.class, it will use Utf8 for the fields when reading from a data file.
We should round-trip the constraint value through the serializer based on the data model associated with the type that was passed in to keep the types consistent.
Attachments
Issue Links
- relates to
-
KITE-496 Datasets#load, create, and update should take in a Class<E> parameter so you can control the type of the entities you want
- Resolved