Create Catalogs

To manage catalogs, add the data-client module as a dependency to your project.

Configure Catalogs

Catalog configurations include the properties listed in the table below. Mandatory properties are in bold.

Note: Catalog IDs

Catalog IDs are publicly visible since they are part of the catalog HRN. Do not include private or company confidential information when you specify a catalog ID. Catalog names are private by default, which means you can add your private or confidential information in this field.

Property Description
id IDs are part of the HERE Resource Name (HRN) for a catalog.
name A short-form name for the catalog.
summary A one sentence summary describing the catalog. This summary is visible when you browse a list of catalogs on the platform portal.
description A detailed description of the catalog and its content. This information appears on the 'Overview' tab when you open a catalog in the platform portal.
layers The layers in the catalog.
tags Some keywords that help when searching for the catalog in the platform portal.
notificationsEnabled If enabled, a notification topic for the catalog is created. This topic allows an application to receive a notification when the catalog is updated.
automaticVersionDeletion If set, enables automatic deletion of catalog versions to manage storage costs and enable lifecycle management of versioned layers.

Layer configurations include the properties listed in the table below.

Property Description
id IDs must be unique for all layers within a catalog.
name A short-form name for the layer.
summary A one sentence summary describing the layer. This summary is visible when you browse a list of layers on the platform portal.
description A detailed description of the layer and its contents. This information appears on the 'Overview' tab when you open a layer in the platform portal.
layerType The type of data provided by the layer: versioned, volatile or stream.
partitioning The name of the partitioning scheme for this layer: generic or heretile.
volumeType Properties that describe the volume where the data is physically stored: durable or volatile.
contentType The MIME type of the data stored in the layer.
contentEncoding Indicator if the data is compressed. Currently, gzip is supported.
coverage A set of admin area strings ( ISO 3166 two-letter codes for countries and regions optionally followed by up to three characters codes for subdivisions, such as 'DE', 'PL' or 'CN-HK') which define the geographic area that this layer covers.
tags A list of keywords that help to find the layer when searching in the platform portal.
billing tags A list of billing tags a free-form tag which is used for grouping billing records together. If supplied, it must be between 4 - 16 characters, contain only alphanumeric ASCII characters [A-Za-z0-9].
schema The HRN of the data schema for this layer.
digest The digest algorithm used by the data publisher to generate a checksum for each partition in the layer. Data consumers can use it to verify the integrity of the data they retrieve from the layer. Currently, MD5, SHA-1 and SHA-256 are supported.
crc The CRC algorithm used to calculate the checksum for the partitions in this layer. Currently, CRC-32C is supported.

Volatile layer configuration

Volatile layer type has following additional configuration fields.

Property Description
ttl The expiry time in milliseconds for data in this layer. Data is automatically removed after the specified time limit has elapsed. For volatile layers the TTL value must be between 60000 (1 minute) and 604800000 (7 days).
dataRedundancy The data redundancy for volatile layers. Possible enum values are single-instance or multi-instance. Single instance layers do not have data redundancy, whereas multi instance layers do.
storageCapacityMb The storage capacity of the layer specified in megabytes, with an increment step of 100 (eg. 100, 500, 600, 2000). For volatile layers, the storage capacity must be between 100 (100MB) and 21000 (21GB).

Index layer configuration

Index layer type has following additional configuration fields.

Property Description
indexDefinitions The collection of index key definitions to index published partitions.
ttl Time to Live of indexed data in index layer. If not specified it defaults to 7 days.

Each index key definition contains the following configuration fields:

Property Description
name The name of index key. Max name length is 64 characters. The name must begin with a Unicode letter. Subsequent characters can be letters, underscores (_), digits (0-9)
indexType The type of index key. Supported types: Int, Bool, String, TimeWindow, and HereTile.
duration Duration attribute of the TimeWindow type must be in the range 600000 (10 minutes) .. 86400000 (24h in millis)
zoomLevel zoomLevel attribute for HereTile type must be in 0 .. 14 range

Supported index key types:

Property Description
Int A signed integer, up to 64 bits.
Bool A Boolean value.
String A string of Unicode characters with the maximum length of 40.
TimeWindow Represents the time slice (NOT just point in time) and it denotes the finest time granularity at which the data will be indexed and later queried. Time type has an attribute duration which represents the time slice length and similarly to the here-tile is NOT mutable. Both here-time value and here-time duration attribute is expressed in milliseconds (time value is milliseconds since Epoch).
HereTile Represents the tile id in the HERE tile map tiling scheme. HereTile type has an attribute zoomLevel which represents the size of the tile and it's NOT mutable.

TimeWindow index key is required. Index layer can have at most single TimeWindow and a single HereTile index key. It means that Index layer can have exactly one TimeWindow index key and only one optional HereTile index key.

Below are the possible TTL values:

Enum Value TTL
SevenDays 7 days
FifteenDays 15 days
OneMonth 30 days
TwoMonths 60 days
ThreeMonths 90 days
FourMonths 120 days
SixMonths 180 days
OneYear 365 days
OneAndHalfYears 548 days
TwoYears 730 days
Unlimited unlimited

Stream layer configuration

Stream layer type has following additional configuration fields.

Property Description
dataInThroughputMbps Maximum throughput for incoming data expressed in megabytes per second. Throttling occurs when the inbound rate exceeds the maximum inbound throughput. The default is 4 MBps. The maximum is 32 MBps.
dataOutThroughputMbps Maximum throughput for outgoing data expressed in megabytes per second. Throttling occurs when the total outbound rate to all consumers exceeds the maximum outbound throughput. The default is 8 MBps. The maximum is 64 MBps.
parallelization The number of Kafka partitions for Stream Layer. The maximum is 32.
ttl The expiry time in milliseconds for data in this layer. Data is automatically removed after the specified time limit has elapsed. For stream layers, the TTL value must be between 600000 (10 minutes) and 259200000 (72 hours).

Note: General recommendation for stream layer properties

(dataInThroughputMbps and dataOutThroughputMbps and parallelization) is to provide all of them in the request.

To preserve backward compatibility there are few corner cases:

  1. User should provide either dataInThroughputMbps and dataOutThroughputMbps or parallelization. Missing field(s) should be calculated according to the following formula 1 parallelization = 1 dataInThroughputMbps / 2 dataOutThroughputMbps
  2. If dataInThroughputMbps and dataOutThroughputMbps are provided, then we calculate parallelization from dataInThroughputMbps rounded up (i.e. if dataInThroughputMbps is 0.5 Mbps we will have parallelization 1).
  3. If all 3 fields are provided, then we use them as is.
  4. If all stream properties are missing, then default values dataInThroughputMbps = 4, dataOutThroughputMbps = 8, parallelization = 4 will be set

Automatic Version Deletion Configuration

Warning: Data Loss

Deleting Catalog versions will delete partition metadata AND data associated with those versions, impacting all versioned layers in the catalog. The partition metadata and data will be irrecoverable. Any partition metadata and data from deleted versions that is still used in current, non-deleted versions will not be deleted so that non-deleted versions remain functional.

Supported automaticVersionDeletion types:

Property Description
numberOfVersionsToKeep If set and once the max number of versions is reached, every time a new version is created, the oldest version will be deleted.

Note

For instructions on how to disable automatic version deletion, see Disable an Automatic Version Deletion

Create Catalogs

To configure and create catalogs, add the following:

Scala
Java
val catalogId = "creating-catalog-test-" + someIdentifierSuffix
val catalogConfig =
  WritableCatalogConfiguration(
    id = catalogId,
    name = catalogId,
    summary = "This is a catalog summary.",
    description = "This is what the catalog is for.",
    tags = Set("tag1", "tag2", "tag3"),
    automaticVersionDeletion =
      Some(AutomaticVersionDeletion.builder.withNumberOfVersionsToKeep(10L).build),
    layers = Seq(
      WritableLayer(
        id = "layer-0",
        name = "INFO",
        summary = "This is a layer summary.",
        description = "This is a layer description.",
        layerType = VersionedLayerType,
        partitioning = GenericPartitioning,
        volume = Volumes.Durable,
        contentType = "application/x-protobuf",
        digest = Some(DigestAlgorithm.MD5),
        crc = Some(CrcAlgorithm.CRC32C)
      ),
      WritableLayer(
        id = "layer-1",
        name = "SCHEMAS",
        summary = "This is a layer summary.",
        description = "This is a layer description.",
        layerType = VersionedLayerType,
        partitioning = GenericPartitioning,
        volume = Volumes.Durable,
        contentType = "application/x-protobuf"
      ),
      WritableLayer(
        id = "layer-2",
        name = "VOLATILEDATA",
        summary = "This is a layer summary.",
        description = "This is a layer description.",
        layerType = VolatileLayerType(),
        partitioning = HereTilePartitioning(tileLevels = 1 :: Nil),
        volume = Volumes.Durable,
        contentType = "application/octet-stream",
        contentEncoding = Some(ContentEncoding.gzip),
        coverage = Some(Coverage(Set[String]("DE", "CN", "US")))
      ),
      WritableLayer(
        id = "layer-3",
        name = "INDEX",
        summary = "This is a layer summary.",
        description = "This is a layer description.",
        layerType = IndexLayerType(
          indexDefinitions = Seq(
            IndexDefinition("someIntKey", IndexType.Int),
            IndexDefinition("someStringKey", IndexType.String),
            IndexDefinition("someTimeWindowKey",
                            IndexType.TimeWindow,
                            duration = Some(3600000)),
            IndexDefinition("someHereTileKey", IndexType.HereTile, zoomLevel = Some(8))
          ),
          ttl = Ttl.OneMonth
        ),
        partitioning = NoPartitioning,
        volume = Volumes.Durable,
        contentType = "application/octet-stream",
        digest = Some(DigestAlgorithm.SHA256),
        crc = Some(CrcAlgorithm.CRC32C)
      )
    )
  )

val adminApi = DataClient().adminApi()
adminApi.createCatalog(catalogConfig).flatMap { hrn =>
  log.info(s"Created new catalog `$hrn`")
  processCreatedCatalog(hrn)
}
String catalogId = "creating-catalog-test-" + someIdentifierSuffix;
WritableCatalogConfiguration catalogConfig =
    new WritableCatalogConfiguration.Builder()
        .withId(catalogId)
        .withName(catalogId)
        .withSummary("This is a catalog summary.")
        .withDescription("This is what the catalog is for.")
        .withTags(new HashSet<>(Arrays.asList("tag1", "tag2", "tag3")))
        .withAutomaticVersionDeletion(
            AutomaticVersionDeletion.builder().withNumberOfVersionsToKeep(10L).build())
        .withLayers(
            Arrays.asList(
                new WritableLayer.Builder()
                    .withId("layer-0")
                    .withName("INFO")
                    .withSummary("This is a layer summary.")
                    .withDescription("This is a layer description.")
                    .withLayerType(LayerTypes.Versioned())
                    .withPartitioning(Partitioning.Generic())
                    .withVolume(Volumes.Durable())
                    .withContentType("application/x-protobuf")
                    .withDigest(DigestAlgorithm.SHA256())
                    .withCrc(CrcAlgorithm.CRC32C()),
                new WritableLayer.Builder()
                    .withId("layer-1")
                    .withName("SCHEMAS")
                    .withSummary("This is a layer summary.")
                    .withDescription("This is a layer description.")
                    .withLayerType(LayerTypes.Versioned())
                    .withPartitioning(Partitioning.Generic())
                    .withVolume(Volumes.Durable())
                    .withContentType("application/x-protobuf"),
                new WritableLayer.Builder()
                    .withId("layer-2")
                    .withName("INDEX")
                    .withSummary("This is a layer summary.")
                    .withDescription("This is a layer description.")
                    .withLayerType(
                        new IndexLayerType.Builder()
                            .addIndexDefinition(
                                new IndexDefinition.Builder()
                                    .withName("someIntKey")
                                    .withIndexType(IndexType.Int)
                                    .build())
                            .addIndexDefinition(
                                new IndexDefinition.Builder()
                                    .withName("someStringKey")
                                    .withIndexType(IndexType.String)
                                    .build())
                            .addIndexDefinition(
                                new IndexDefinition.Builder()
                                    .withName("someTimeWindowKey")
                                    .withIndexType(IndexType.TimeWindow)
                                    .withDuration(3600000L)
                                    .build())
                            .addIndexDefinition(
                                new IndexDefinition.Builder()
                                    .withName("someHereTileKey")
                                    .withIndexType(IndexType.HereTile)
                                    .withZoomLevel(8)
                                    .build())
                            .withTtl(Ttl.OneMonth)
                            .build())
                    .withPartitioning(Partitioning.NoPartition())
                    .withVolume(Volumes.Durable())
                    .withContentType("application/x-protobuf")))
        .build();

AdminApi adminApi = DataClient.get(myActorSystem).adminApi();
adminApi
    .createCatalog(catalogConfig)
    .thenApply(
        hrn -> {
          log.info("Created new catalog `" + hrn + "`");
          return processCreatedCatalog(hrn);
        });

Note

It may take several minutes for a new catalog to appear in the list of catalogs returned by the Data Client Library, CLI, REST API, and the list displayed on the HERE platform portal.

results matching ""

    No results matching ""