Serving Metadata

The OData service generates two types of documents with metadata about the Denodo databases:

  1. The “Service Document”: lists all the entities offered by the data service. It is available at the root URI of the service, specifying the database name where we are going to get information: /denodo-odata.svc/<database name>.

    Below, there is an example where the accessible collections of the movies database are actor, address, city, country, film and film_actor.


      "@odata.context": "/denodo-odata.svc/movies/$metadata",
      "value": [
          "name": "actor",
          "url": "actor"
          "name": "address",
          "url": "address"
          "name": "city",
          "url": "city"
          "name": "country",
          "url": "country"
          "name": "film",
          "url": "film"
          "name": "film_actor",
          "url": "film_actor"
  2. The “Service Metadata Document” (also called Entity Data Model (EDM): XML representation of the data model exposed by the service. It is available at .../$metadata.

    For example:


    Example of an entity country that has a relationship with zero or more city elements:

       <EntityType Name="country">
              <PropertyRef Name="country_id"/>
          <Property Name="country_id" Type="Edm.Int16"
          <Property Name="country" Type="Edm.String"
          <Property Name="last_update" Type="Edm.DateTimeOffset"
          <NavigationProperty Name="cities"
              <ReferentialConstraint Property="country_id"

The service maps these OData structures to Virtual DataPort concepts like this:

Denodo OData Service Virtual DataPort
Entity Type View Definition
Entity Type > Property View Column
Entity Type > Navigation Property Association Role
Relationship Association Definition
Entity Set View Data
Imported Functions -