- A string: Uses the string as the context name with default values (description=None, is_versioned=False)
- An object: Uses the object’s name, description, and is_versioned properties
entries
.
If present, any matching key inside this dictionary will override the
inferred type of that particular entry. The explicit_types dictionary
can also specify if a field is mutable via a ‘mutable’ boolean flag
and if a field is unique via a ‘unique’ boolean flag:
Authorizations
Bearer authentication header of the form
Bearer <token>
, where <token>
is your auth token.Body
Name of the project the stored entries will be associated to.
Optional context path to update for the logs. Can use ’/’ for nested contexts (e.g. ‘training/batch1’). Can be a string (which will be interpreted with description=None and is_versioned=False) or a ContextCreateRequest object.
Dictionary containing one or more key:value pairs that will be logged into the platform. Can be either a single dictionary or a list of dictionaries for batch processing. When using lists for both params and entries, their lengths must match. Values must be JSON serializable. If a
explicit_types
dictionary is present, its values will override the inferred types of the entries. The explicit_types dictionary can also specify if a field is mutable via a ‘mutable’ boolean flag, or unique via a ‘unique’ boolean flag. For enum types, use the EnumType model with ‘values’ list and optional ‘restrict’ flag. Omit ‘values’ to create an open enum (auto-seeding). For contexts with nested unique IDs, parent ID values for the leftmost N-1 unique columns can be supplied as normal param keys. The rightmost column is always auto-incremented. For example, if unique columns are [‘user’, ‘session’, ‘step’], you can provide ‘user’ and ‘session’ values in params, and ‘step’ will be auto-generated.Dictionary containing one or more key:value pairs that will be logged into the platform. Can be either a single dictionary or a list of dictionaries for batch processing. When using lists for both params and entries, their lengths must match. Values must be JSON serializable. If a
explicit_types
dictionary is present, its values will override the inferred types of the entries. The explicit_types dictionary can also specify if a field is mutable via a ‘mutable’ boolean flag, or unique via a ‘unique’ boolean flag. For enum types, use the EnumType model with ‘values’ list and optional ‘restrict’ flag. Omit ‘values’ to create an open enum (auto-seeding). For contexts with nested unique IDs, parent ID values for the leftmost N-1 unique columns can be supplied as normal entry keys. The rightmost column is always auto-incremented. For example, if unique columns are [‘user’, ‘session’, ‘step’], you can provide ‘user’ and ‘session’ values in entries, and ‘step’ will be auto-generated.