Feature Engineering

Save feature definitions, source references, entity keys, and serving requirements as a contract for your data workflow.

Open Feature Engineering

Define a feature contract

  1. Create a feature table definition and select its source table or query reference.
  2. Set a stable entity key and, when needed, the event-time column.
  3. Add each feature’s name, data type, expression, and description.
  4. Record the intended serving mode, refresh cadence, and time-to-live.

Compute feature values separately

This workspace saves feature contracts and metadata. An ONLINE setting or refresh cadence does not provision an online feature store or schedule materialization by itself.

Use a configured pipeline or workload to compute, store, and refresh the values. Test joins, time boundaries, freshness, and downstream reads in that implementation.

API endpoints

Use your Genorbex deployment’s origin followed by the path below. Replace IDs with resources accessible to your account. Authentication and permissions are checked by each endpoint.

GET /api/orbexdb/ai-ml/assets

Lists assets; use kind=FEATURE_TABLE as a query parameter for feature definitions.

Authentication: Genorbex account token and service/resource access; API-key support follows the endpoint’s authentication guard.

Need help with your setup? Visit the Help Center or contact Genorbex.