public class SplitFrameV3 extends SchemaV3<SplitFrame,SplitFrameV3>
SchemaV3.Meta
Schema.AutoParseable
Modifier and Type | Field and Description |
---|---|
KeyV3.FrameKeyV3 |
dataset |
KeyV3.FrameKeyV3[] |
destination_frames |
KeyV3.JobKeyV3 |
key |
double[] |
ratios |
Constructor and Description |
---|
SplitFrameV3() |
SplitFrameV3(SplitFrame impl) |
Modifier and Type | Method and Description |
---|---|
SplitFrame |
createImpl()
Create an appropriate implementation object and any child objects but does not fill them.
|
createAndFillImpl, extractVersionFromSchemaName, fillFromBody, fillFromImpl, fillFromImpl, fillFromImpl, fillFromParms, fillFromParms, fillImpl, fillImpl, getImplClass, getImplClass, getSchemaName, getSchemaType, getSchemaVersion, init_meta, markdown, markdown, newInstance, newInstance, setField, setSchemaType_doNotCall
asBytes, clone, copyOver, frozenType, read, readExternal, readJSON, reloadFromBytes, toJsonString, write, writeExternal
@API(help="Job Key") public KeyV3.JobKeyV3 key
@API(help="Dataset") public KeyV3.FrameKeyV3 dataset
@API(help="Split ratios - resulting number of split is ratios.length+1", json=true) public double[] ratios
@API(help="Destination keys for each output frame split.", direction=INOUT) public KeyV3.FrameKeyV3[] destination_frames
public SplitFrameV3()
public SplitFrameV3(SplitFrame impl)
public SplitFrame createImpl()
Schema
For objects without children this method does all the required work. For objects with children the subclass will need to override, e.g. by calling super.createImpl() and then calling createImpl() on its children.
Note that impl objects for schemas which override this method don't need to have a default constructor (e.g., a Keyed object constructor can still create and set the Key), but they must not fill any fields which can be filled later from the schema.
TODO: We could handle the common case of children with the same field names here by finding all of our fields that are themselves Schemas.
createImpl
in class Schema<SplitFrame,SplitFrameV3>