Create a new schema object

Create a new schema object specifying a schema like "A,B:int,C:double" for user defined type schema string must contain C# name of the type do not use this method with CLR name of type (Type.FullName) In all other cases create empty schema and add columns using ColumnInfo(string name, Type type)

Create a new schema object specifying a schema like {"A", "B:int" , "C:double"} for user defined type column string must contain C# name of the type do not use this method with CLR name of type (Type.FullName) In all other cases create empty schema and add columns using ColumnInfo(string name, Type type)

Add another column to the schema

Add more columns to the schema

Create a new schema object that mirrors the current one The resulting schema will have the same column names and column types, in the same order, but it does not claim that output rows with this schema are identical to some input row.

Clone a schema and set the Source of each column to the matching input column. Input rows have to be passed through (or copied) to output rows with this schema unchanged.

Returns true if there is a column named specified by name

Returns the string repesentation of this schema

Returns the string repesentation of this object

Get the position of the ColumnInfo with this name in this schema

Merge with other schema

Obsolete -- please use schema.CloneWithSource() instead. The user defined object will pass through input rows unchanged as output rows

Sets the table.

Returns string representation of this schema.

Add more columns to the schema if not present already.

Enumerable of Schema columns

Returns the number of columns

Access the ith ColumnInfo from a Schema

Deprecated: please use IndexOf(name) instead Get the position of the ColumnInfo with this name in this schema Eventually this will be changed to give the actual ColumnInfo instead

Rows in this RowSet are ordered by OrderingList (which is a sequence of (column,ASC/DESC) pairs) The semantics vary a bit across UDOs: For extractors and processors, each vertex output rows in OrderingList order, since there is a single invocation of the processor/extractor per vertex For reducers and combiners, the vertex calls the UDO multiple times, once per group of ON columns. Stream-based reducers/combiners sort the inputs on the ON columns. If those are pass-through, the output is sorted by the ON columns In addition to that sort, we attach the ordering list. Example: REDUCE A ON a, b USING SampleReducer Suppose that SampleReducer has "a" as a pass-through column and declares "c,a" as an OrderlingList Also, assume that the stream-based reducer sorts the input on "a,b". The output of the reducer, due the pass-through column, is sorted by "a". Additionally, it is sorted by "c" within each group (the last "a" in "c,a" is redundant) So the reducer would deliver sorting on "a,c"

All columns in PartitioningSet with the same value are located in the same vertex RowSet

Not Supported. The name of the table. This is only set by the system for the inputs to combiners, both for Produces() and Combine(). For all schemas other than the inputs to a Combiner, schema.Table is null, since in all other cases column names are already distinct.