Changelog

Version

Change

Description

1.10.0

FIXED

Fixed batch source connectors so that they do not restart from the beginning after checkpoint restoration.

1.10.0

ADDED

Added support for route tracking in streaming mode, allowing the Anonymizer to use predefined routes and waypoints to track trip progress and detect
deviations. When enabled, route tracking emits route deviation events and supports configurable anonymization strategies.

1.10.0

ADDED

Added the is_input_partitioned source parameter to Kafka and Kinesis connectors. When set to true, it enables parallel consumption across partitions/shards while preserving order within each key group; the default remains false.

1.10.0

KNOWN ISSUE

Certain versions of the Java Development Kit (JDK) require the manifest file
to stay within a file size limit. When the file exceeds the limit, you get this error:

Unsupported size: xxx for JarEntry META-INF/MANIFEST.MF. Allowed max size: 8000000 bytes

To fix this issue, increase the maximum manifest file size by adjusting the
jdk.jar.maxSignatureFileSize property of the JAVA_TOOL_OPTIONS environment
variable (-D...). This is a mechanism used to pass startup options and arguments
to the Java Virtual Machine (JVM).

For example, use the following configuration to set the maximum file size to
approximately 22 MB:

JAVA_TOOL_OPTIONS=-Djdk.jar.maxSignatureFileSize=22000000

1.9.0

ADDED

Added support for insights generation, which allows users to generate insights from the anonymized data.

1.9.0

ADDED

Added Density-aware anonymization in stream anonymization mode.
Density-aware anonymization allows you to apply different anonymization algorithms based on the number of vehicles in a given area.

1.9.0

KNOWN ISSUE

Certain versions of the Java Development Kit (JDK) require the manifest file
to stay within a file size limit. When the file exceeds the limit, you get this error:

Unsupported size: xxx for JarEntry META-INF/MANIFEST.MF. Allowed max size: 8000000 bytes

JAVA_TOOL_OPTIONS=-Djdk.jar.maxSignatureFileSize=22000000

1.8.0

FIXED

Fixed the SINK_COMPRESSION_FORMAT initialization.
Previously, the SINK_COMPRESSION_FORMAT was always initialized by value from SOURCE_COMPRESSION_FORMAT.

1.8.0

ADDED

Introduced the kafka_props_file parameter in the Kafka connector URI.
This parameter defines the path to a kafka.properties file, enabling advanced Kafka consumer or producer configuration, authentication with
different security protocols and mechanisms, and support for connecting to multiple brokers.

To learn more, see the Kafka Connector Documentation.

1.8.0

ADDED

Added Junction-based gapping in batch anonymization mode.
Junction-based gapping, powered by the smart gapping "Short Horizon" slgorithm, prioritizes creating anonymization gaps at known junctions rather than at arbitrary locations. This results in more context-aware anonymization.

1.8.0

CHANGED

Migrated application runtime from Java 11 to Java 17 for improved performance, language features, and long-term support.

1.8.0

FIXED

Fixed an issue where dropped event metrics were incorrectly reported under probe point metrics. Introduced a new metric EVENT_DROPPED_REGULAR to
accurately report the total number of events dropped during the anonymization process.

1.8.0

CHANGED

Preprocessor is updated to version 1.2.0.
It is migrated to use ignite cache v3 which is incompatible
to previous versions of preprocessor. Once you upgrade the
preprocessor, kindly update your deployment setup to use
ignite cache v3.

1.8.0

ADDED

Added support for elastic scaling adaptive mode, which adjust the parallelism of a job based on available slots.

By scaling the taskManager replicas up or down, the job parallelism is automatically increased or decreased accordingly by the flink.

1.8.0

KNOWN ISSUE

Certain versions of the Java Development Kit (JDK) require the manifest file
to stay within a file size limit. When the file exceeds the limit, you get this error:

Unsupported size: xxx for JarEntry META-INF/MANIFEST.MF. Allowed max size: 8000000 bytes

JAVA_TOOL_OPTIONS=-Djdk.jar.maxSignatureFileSize=22000000

1.7.1

CHANGED

The configuration syntax for the overall region selection feature has been updated. Now, region selection can be used to include regions in data processing and to explicitly exclude regions from data processing.

Learn more about the features and how to configure them:
- Region selection inclusion
- Region selection exclusion
- Configuration

1.7.1

ADDED

Support for user-defined speed threshold in stay point detection algorithm.

The threshold speed for the stay point detection algorithm can now be configured using within an inclusive range of 0 to
130 kph. This allows finer control over detection sensitivity based on specific movement patterns.

Add below config to anonymization.conf to define the desired speed threshold.

anonymization {
  stayPoint.obfuscation {
    enabled: true
    speedThresholdKph: 10
  }
}

1.7.1

ADDED

Added the optional calculateSpeedIfZero anonymization parameter.

It enables/disables automatic speed calculation for probe points with zero or undefined speed. In this case,
the speed will be calculated based on the previous point location and timestamp.

The calculated speed (if enabled) is used to apply start-cut, end-cut, and stay-point obfuscation anonymization strategies.

1.7.1

ADDED

Added several optional configuration parameters for Kinesis connectors.

See the "Amazon Kinesis Data Streams" user guide section for details.

1.7.1

FIXED

When using an S3 source URI, the S3 path resolver previously included other directories with matching name prefixes (
e.g., input also matched input_dummy). It now strictly processes the specified directory.

1.7.1

ADDED

Added support for all value in attributes.extendedAttributes.keep configuration. When set to all, all extended
attributes are included in anonymization, and attributes.extendedAttributes.message and
attributes.extendedAttributes.point array settings are ignored. To learn more,
see configuration chapter.

1.7.1

ADDED

Added alerts detection and routing, which allows you to manage incoming messages containing critical events, such as airbag deployments, crashes, and other emergencies.

To learn more, see Alerts detection and routing.

1.7.1

CHANGED

HERE Anonymizer Self-Hosted is now upgraded to use Apache Flink 1.19.2. For detailed instructions on
installation, please see
the installation guide.

To learn more about the Apache Flink 1.19.2, see
the flink documentation.

1.7.1

ADDED

Added Probe event handling which allows you to decide what happens with probe events that match the defined criteria.

The options are:
- keep - Events that match the defined criteria are kept without anonymization.
- drop - Events that match the defined criteria are dropped.
- regular - Events that match the defined criteria are subject to anonymization configured for the instance.

To learn more, see Configuration of anonymization methods

1.7.1

ADDED

Generated the country borders for configuring all region-specific features like, region selection inclusion and exclusion etc.
Countries are organised by regions (APAC,EasternEurope,MEA,NorthCentralAmerica,Oceania,SouthAmerica,WesternEurope) and stored in GeoJSON format.

See the "Country borders GeoJSON" user guide section for details.

1.7.1

ADDED

Added logging of anonymized data.
To learn how to enable and configure this feature, see Configuration.

1.7.1

KNOWN ISSUE

Certain versions of the Java Development Kit (JDK) require the manifest file
to stay within a file size limit. When the file exceeds the limit, you get this error:

Unsupported size: xxx for JarEntry META-INF/MANIFEST.MF. Allowed max size: 8000000 bytes

JAVA_TOOL_OPTIONS=-Djdk.jar.maxSignatureFileSize=22000000

1.7.1

CHANGED

1.7.1

ADDED

anonymization {
  stayPoint.obfuscation {
    enabled: true
    speedThresholdKph: 10
  }
}

1.7.1

ADDED

1.7.1

ADDED

Added several optional configuration parameters for Kinesis connectors.

See the "Amazon Kinesis Data Streams" user guide section for details.

1.7.1

FIXED

1.7.1

ADDED

1.7.1

ADDED

1.7.1

CHANGED

1.7.1

ADDED

1.7.1

ADDED

1.7.1

ADDED

Added logging of anonymized data.
To learn how to enable and configure this feature, see Configuration.

1.7.1

KNOWN ISSUE

Certain versions of the Java Development Kit (JDK) require the manifest file
to stay within a file size limit. When the file exceeds the limit, you get this error:

Unsupported size: xxx for JarEntry META-INF/MANIFEST.MF. Allowed max size: 8000000 bytes

JAVA_TOOL_OPTIONS=-Djdk.jar.maxSignatureFileSize=22000000

1.7.0

CHANGED

1.7.0

ADDED

anonymization {
  stayPoint.obfuscation {
    enabled: true
    speedThresholdKph: 10
  }
}

1.7.0

ADDED

1.7.0

ADDED

Added several optional configuration parameters for Kinesis connectors.

See the "Amazon Kinesis Data Streams" user guide section for details.

1.7.0

FIXED

1.7.0

ADDED

1.7.0

ADDED

1.7.0

CHANGED

1.7.0

ADDED

1.7.0

ADDED

1.7.0

ADDED

Added logging of anonymized data.
To learn how to enable and configure this feature, see Configuration.

1.7.0

KNOWN ISSUE

Certain versions of the Java Development Kit (JDK) require the manifest file
to stay within a file size limit. When the file exceeds the limit, you get this error:

Unsupported size: xxx for JarEntry META-INF/MANIFEST.MF. Allowed max size: 8000000 bytes

JAVA_TOOL_OPTIONS=-Djdk.jar.maxSignatureFileSize=22000000

1.7.0

CHANGED

1.7.0

ADDED

anonymization {
  stayPoint.obfuscation {
    enabled: true
    speedThresholdKph: 10
  }
}

1.7.0

ADDED

1.7.0

ADDED

Added several optional configuration parameters for Kinesis connectors.

See the "Amazon Kinesis Data Streams" user guide section for details.

1.7.0

FIXED

1.7.0

ADDED

1.7.0

ADDED

1.7.0

CHANGED

1.7.0

ADDED

1.7.0

ADDED

1.7.0

ADDED

Added logging of anonymized data.
To learn how to enable and configure this feature, see Configuration.

1.7.0

KNOWN ISSUE

Certain versions of the Java Development Kit (JDK) require the manifest file
to stay within a file size limit. When the file exceeds the limit, you get this error:

Unsupported size: xxx for JarEntry META-INF/MANIFEST.MF. Allowed max size: 8000000 bytes

JAVA_TOOL_OPTIONS=-Djdk.jar.maxSignatureFileSize=22000000

1.6.2

ADDED

Added location blacklisting feature.

Points falling in blacklisted region are excluded/dropped from the data.

Blacklisted region can be mentioned in exclude parameter of the region selection in anonymization.conf.

Example

anonymization {
  region.selection {
    enabled: true
    "include" {
      regionUris: [
        s3://my-bucket/files/region-inclusion-region-1.json?region=eu-west-1,
        s3://my-bucket/files/region-inclusion-region-2.json?region=eu-west-1,
        s3://my-bucket/files/region-inclusion-region-3.json?region=eu-west-1
      ]
    outerPointStrategy: <drop/keep>
    exclude {
      regionUris: [
        s3://my-bucket/files/blacklist-region-1.json?region=eu-west-1,
        s3://my-bucket/files/blacklist-region-2.json?region=eu-west-1,
        s3://my-bucket/files/blacklist-region-3.json?region=eu-west-1
      ]
    }
  }
}

1.6.2

CHANGED

Region selection syntax for mentioning region selection inclusion has been updated.

Region selection inclusion region URIs regionUris and outerPointStrategy should be mentioned in include parameter of the region selection in anonymization.conf.

Old syntax

anonymization {
  region.selection {
    enabled: true
    regionUris: [
      s3://my-bucket/files/region-inclusion-region-1.json?region=eu-west-1,
      s3://my-bucket/files/region-inclusion-region-2.json?region=eu-west-1,
      s3://my-bucket/files/region-inclusion-region-3.json?region=eu-west-1
    ]
    outerPointStrategy: <drop/keep>
  }
}

New syntax

anonymization {
  region.selection {
    enabled: true
    "include" {
      regionUris: [
        s3://my-bucket/files/region-inclusion-region-1.json?region=eu-west-1,
        s3://my-bucket/files/region-inclusion-region-2.json?region=eu-west-1,
        s3://my-bucket/files/region-inclusion-region-3.json?region=eu-west-1
      ]
      outerPointStrategy: <drop/keep>
    exclude {
      regionUris: [
        s3://my-bucket/files/blacklist-region-1.json?region=eu-west-1,
        s3://my-bucket/files/blacklist-region-2.json?region=eu-west-1,
        s3://my-bucket/files/blacklist-region-3.json?region=eu-west-1
      ]
    }
  }
}

1.6.2

ADDED

anonymization {
  stayPoint.obfuscation {
    enabled: true
    speedThresholdKph: 10
  }
}

1.6.2

ADDED

1.6.2

ADDED

Added several optional configuration parameters for Kinesis connectors.

See the "Amazon Kinesis Data Streams" user guide section for details.

1.6.2

KNOWN ISSUE

Certain versions of the Java Development Kit (JDK) require the manifest file
to stay within a file size limit. When the file exceeds the limit, you get this error:

Unsupported size: xxx for JarEntry META-INF/MANIFEST.MF. Allowed max size: 8000000 bytes

JAVA_TOOL_OPTIONS=-Djdk.jar.maxSignatureFileSize=22000000

1.6.1

ADDED

Added POI (point of interest) proximity data removal feature.

POI proximity data removal allows you to define sensitive areas where trace points or events are deleted.

1.6.1

ADDED

Added algorithm to read and write compressed data in Gzip format.

Data messages can be compressed to the Gzip format or have no compression applied. You can adjust the compression settings for source and sink connectors independently.

Variables SOURCE_COMPRESSION_FORMAT and SINK_COMPRESSION_FORMAT define the expected compression format of output data. The available values are:

- GZIP - Compresses message data to Gzip format.
- NONE - Applies no compression.

1.6.1

CHANGED

Upgraded the RabbitMQ version which is used in deployment configurations to 4.1.0.

1.6.1

FIXED

Fixed the AWS S3 connector used for loading files for such features as
Origin-destination obfuscation, Whitelisting, Country selection,
POI (point of interest) proximity data removal.

Before the fix, only the first file in the AWS S3 bucket was always loaded.

1.6.1

ADDED

Added location whitelisting feature.

Points contained within whitelisted area are excluded from anonymization.
Whitelisted areas should be mentioned in areaUris parameter.

Add below config to anonymization.conf to enable whitelisting feature.

anonymization {
  whitelist {
    area {
      enabled: true
      areaUris: [
        s3://my-bucket/files/whitelist-area-1.json?region=eu-west-1,
        s3://my-bucket/files/whitelist-area-2.json?region=eu-west-1,
        s3://my-bucket/files/whitelist-area-3.json?region=eu-west-1
      ]
    }
  }
}

1.6.1

REMOVED

Removed app.conf application configuration.

The advanced configuration makes no sense anymore, as all the advanced parameters can be
configured by environment variables or by anonymization.conf.

1.6.1

KNOWN ISSUE

Certain versions of the Java Development Kit (JDK) require the manifest file
to stay within a file size limit. When the file exceeds the limit, you get this error:

Unsupported size: xxx for JarEntry META-INF/MANIFEST.MF. Allowed max size: 8000000 bytes

JAVA_TOOL_OPTIONS=-Djdk.jar.maxSignatureFileSize=22000000

1.6.1

ADDED

Added POI (point of interest) proximity data removal feature.

POI proximity data removal allows you to define sensitive areas where trace points or events are deleted.

1.6.1

ADDED

1.6.1

CHANGED

Upgraded the RabbitMQ version which is used in deployment configurations to 4.1.0.

1.6.1

FIXED

1.6.1

ADDED

anonymization {
  whitelist {
    area {
      enabled: true
      areaUris: [
        s3://my-bucket/files/whitelist-area-1.json?region=eu-west-1,
        s3://my-bucket/files/whitelist-area-2.json?region=eu-west-1,
        s3://my-bucket/files/whitelist-area-3.json?region=eu-west-1
      ]
    }
  }
}

1.6.1

REMOVED

Removed app.conf application configuration.

The advanced configuration makes no sense anymore, as all the advanced parameters can be
configured by environment variables or by anonymization.conf.

1.6.1

KNOWN ISSUE

Certain versions of the Java Development Kit (JDK) require the manifest file
to stay within a file size limit. When the file exceeds the limit, you get this error:

Unsupported size: xxx for JarEntry META-INF/MANIFEST.MF. Allowed max size: 8000000 bytes

JAVA_TOOL_OPTIONS=-Djdk.jar.maxSignatureFileSize=22000000

1.6.0

ADDED

Added POI (point of interest) proximity data removal feature.

POI proximity data removal allows you to define sensitive areas where trace points or events are deleted.

1.6.0

ADDED

1.6.0

CHANGED

Upgraded the RabbitMQ version which is used in deployment configurations to 4.1.0.

1.6.0

FIXED

1.6.0

ADDED

anonymization {
  whitelist {
    area {
      enabled: true
      areaUris: [
        s3://my-bucket/files/whitelist-area-1.json?region=eu-west-1,
        s3://my-bucket/files/whitelist-area-2.json?region=eu-west-1,
        s3://my-bucket/files/whitelist-area-3.json?region=eu-west-1
      ]
    }
  }
}

1.6.0

REMOVED

Removed app.conf application configuration.

The advanced configuration makes no sense anymore, as all the advanced parameters can be
configured by environment variables or by anonymization.conf.

1.6.0

KNOWN ISSUE

Certain versions of the Java Development Kit (JDK) require the manifest file
to stay within a file size limit. When the file exceeds the limit, you get this error:

Unsupported size: xxx for JarEntry META-INF/MANIFEST.MF. Allowed max size: 8000000 bytes

JAVA_TOOL_OPTIONS=-Djdk.jar.maxSignatureFileSize=22000000

1.6.0

ADDED

Added POI (point of interest) proximity data removal feature.

POI proximity data removal allows you to define sensitive areas where trace points or events are deleted.

1.6.0

ADDED

1.6.0

CHANGED

Upgraded the RabbitMQ version which is used in deployment configurations to 4.1.0.

1.6.0

FIXED

1.6.0

ADDED

anonymization {
  whitelist {
    area {
      enabled: true
      areaUris: [
        s3://my-bucket/files/whitelist-area-1.json?region=eu-west-1,
        s3://my-bucket/files/whitelist-area-2.json?region=eu-west-1,
        s3://my-bucket/files/whitelist-area-3.json?region=eu-west-1
      ]
    }
  }
}

1.6.0

REMOVED

Removed app.conf application configuration.

The advanced configuration makes no sense anymore, as all the advanced parameters can be
configured by environment variables or by anonymization.conf.

1.6.0

KNOWN ISSUE

Certain versions of the Java Development Kit (JDK) require the manifest file
to stay within a file size limit. When the file exceeds the limit, you get this error:

Unsupported size: xxx for JarEntry META-INF/MANIFEST.MF. Allowed max size: 8000000 bytes

JAVA_TOOL_OPTIONS=-Djdk.jar.maxSignatureFileSize=22000000

1.5.0

ADDED

Added origin destination obfuscation algorithm. Algorithm aims to obfuscate
origin and destination points in origin and destination region area
respectively.

Add below config to anonymization.conf to enable OD obfuscation.

anonymization {
  originDestination.obfuscation: {
    enabled: true
    areaUris: [
      "s3://my-bucket/my-od-areas.json?region=eu-west-1"
      "file://my-local-folder-on-task-manager/my-other-od-areas.json"
    ]
    ignoreRepeatingRegion: false
    timeWindowSeconds: 30
  }
}

1.5.0

REMOVED

Removed attribute type from anonymization config.

1.5.0

DOCUMENTATION

Full set of user guide documentation about Country selection,
Origin-destination obfuscation, Smart gapping, Start and end cutting,
Staypoint prediction.

1.5.0

CHANGED

Changed connector URI params case to snake case.

eg:- rabbit connector uri with params.

rabbit://guest:guest@host:5672/queue?key_file=<key_file_value>&crt_file=<crt_file_value>&ca_file=<ca_file_value>"

1.5.0

ADDED

Added feature to drop or keep points outside the region.
Regions should be mentioned in the regionUris param.

Add below config to anonymization.conf to enable region selection feature.

anonymization {
	region.selection: {
		enabled: true
		regionUris: [
			"s3://my-bucket?files=FRA_regions.geojson",
			"s3://my-bucket?files=DEU_regions.geojson",
			"s3://my-bucket?files=BEL_regions.geojson"
		]
		outerPointStrategy: [drop|keep]
	}
}

1.5.0

ADDED

Drop only exact late points instead of entire late chunk.

1.5.0

FIXED

Make kinesis connector compatible with AWS Role-based access control (RBAC) and
explicit credentials.

1.5.0

KNOWN ISSUE

Certain versions of the Java Development Kit (JDK) require the manifest file
to stay within a file size limit. When the file exceeds the limit, you get this error:

Unsupported size: xxx for JarEntry META-INF/MANIFEST.MF. Allowed max size: 8000000 bytes

JAVA_TOOL_OPTIONS=-Djdk.jar.maxSignatureFileSize=22000000

1.5.0

ADDED

Added sink connector for writing to Azure Blob Storage.

Use this connector to write all files to the persistent storage (Azure Blob) by mentioning the location of folder in the path of connector configuring URI.
To learn more, see https://www.here.com/docs/bundle/anonymizer-self-hosted-user-guide/page/connectors/azure-blob.html

1.5.0

ADDED

Added the Batch Processing implementation for HERE Anonymizer.

This includes reading pre-processed data from storage using connectors (AWS S3, Azure Blob) , clean and anonymize the historical data then writing the anonymized chunks to persistent storage.
More details for the same can be found at https://www.here.com/docs/bundle/anonymizer-self-hosted-user-guide/page/concepts/operational-modes.html#batch-mode

1.5.0

ADDED

Added support for prometheus and grafana to HERE Anonymizer.

This implements an optional addon to HERE Anonymizer and enables prometheus and grafana. Optional service can be achieved by profiles parameter added in the demo_start.sh.
Selection of profiles could be plain = current one or monitoring = new profile with prometheus and grafana.
To learn more, see https://www.here.com/docs/bundle/anonymizer-self-hosted-user-guide/page/metrics.html

1.5.0

ADDED

Added the runbook directory for HERE Anonymizer.

This runbook is a compilation of standardized documents, references and procedures to deal with common recurring operational tasks.

1.5.0

ADDED

Added Azure Blob source connector for batch processing.

This connector supports reading raw data for batch processing. It reads the whole list of files at once and generates end indication.
To learn more, see https://www.here.com/docs/bundle/anonymizer-self-hosted-user-guide/page/connectors/azure-blob.html

1.5.0

CHANGED

Changed URI format for the kinesis connectors to include arn as the query parameter and remove obsolete details.

To learn more, see https://www.here.com/docs/bundle/anonymizer-self-hosted-user-guide/page/connectors/kinesis.html

1.5.0

KNOWN ISSUE

Certain versions of the Java Development Kit (JDK) require the manifest file
to stay within a file size limit. When the file exceeds the limit, you get this error:

Unsupported size: xxx for JarEntry META-INF/MANIFEST.MF. Allowed max size: 8000000 bytes

JAVA_TOOL_OPTIONS=-Djdk.jar.maxSignatureFileSize=22000000

1.4.2

ADDED

1.4.2

ADDED

1.4.2

ADDED

1.4.2

ADDED

Added the runbook directory for HERE Anonymizer.

This runbook is a compilation of standardized documents, references and procedures to deal with common recurring operational tasks.

1.4.2

ADDED

1.4.2

KNOWN ISSUE

Certain versions of the Java Development Kit (JDK) require the manifest file
to stay within a file size limit. When the file exceeds the limit, you get this error:

Unsupported size: xxx for JarEntry META-INF/MANIFEST.MF. Allowed max size: 8000000 bytes

JAVA_TOOL_OPTIONS=-Djdk.jar.maxSignatureFileSize=22000000

1.4.1

ADDED

1.4.1

ADDED

1.4.1

ADDED

1.4.1

ADDED

Added the runbook directory for HERE Anonymizer.

This runbook is a compilation of standardized documents, references and procedures to deal with common recurring operational tasks.

1.4.1

ADDED

1.4.1

KNOWN ISSUE

Certain versions of the Java Development Kit (JDK) require the manifest file
to stay within a file size limit. When the file exceeds the limit, you get this error:

Unsupported size: xxx for JarEntry META-INF/MANIFEST.MF. Allowed max size: 8000000 bytes

JAVA_TOOL_OPTIONS=-Djdk.jar.maxSignatureFileSize=22000000

1.4.0

KNOWN ISSUE

Certain versions of the Java Development Kit (JDK) require the manifest file
to stay within a file size limit. When the file exceeds the limit, you get this error:

Unsupported size: xxx for JarEntry META-INF/MANIFEST.MF. Allowed max size: 8000000 bytes

JAVA_TOOL_OPTIONS=-Djdk.jar.maxSignatureFileSize=22000000

1.3.2

ADDED

Added the attributes section for Anonymization configuration file.
This section allows the management of what message/points attributes should be kept during anonymization.

1.3.2

ADDED

Added the Azure Blob Storage management data connector.
Use this data connector to enable the Management API to read the license and anonymization configuration from the Azure Blob storage at defined intervals.
To learn more, see Azure Blob Storage management data connector.

1.3.2

ADDED

Added the Amazon Simple Queue Service (SQS) data connector. The connector leverages the FIFO ("First In, First Out") queue type and can be fine-tuned
using several configuration parameters.To learn more, see the Amazon SQS data connector documentation.

1.3.2

ADDED

Added the Amazon Kinesis Data Streams data connector.

The connector expects the name of the data stream to be connected and can be fine-tuned
using several configuration parameters.

To learn more, see the Amazon Kinesis data streams connector documentation.

1.3.2

ADDED

Added the Azure Event Hubs data connector. The connector leverages the support for Kafka and AMQP protocols, and can be
fine-tuned using several configuration parameters. To learn more, see
the Azure Event Hubs data connector documentation.

1.3.2

KNOWN ISSUE

Certain versions of the Java Development Kit (JDK) require the manifest file
to stay within a file size limit. When the file exceeds the limit, you get this error:

Unsupported size: xxx for JarEntry META-INF/MANIFEST.MF. Allowed max size: 8000000 bytes

JAVA_TOOL_OPTIONS=-Djdk.jar.maxSignatureFileSize=22000000

1.3.1

ADDED

Added the attributes section for Anonymization configuration file.
This section allows the management of what message/points attributes should be kept during anonymization.

1.3.1

ADDED

1.3.1

ADDED

1.3.1

ADDED

1.3.1

ADDED

1.3.1

KNOWN ISSUE

Certain versions of the Java Development Kit (JDK) require the manifest file
to stay within a file size limit. When the file exceeds the limit, you get this error:

Unsupported size: xxx for JarEntry META-INF/MANIFEST.MF. Allowed max size: 8000000 bytes

JAVA_TOOL_OPTIONS=-Djdk.jar.maxSignatureFileSize=22000000

1.3.0

ADDED

Added the attributes section for Anonymization configuration file.
This section allows the management of what message/points attributes should be kept during anonymization.

1.3.0

ADDED

1.3.0

ADDED

1.3.0

ADDED

1.3.0

ADDED

1.3.0

KNOWN ISSUE

Certain versions of the Java Development Kit (JDK) require the manifest file
to stay within a file size limit. When the file exceeds the limit, you get this error:

Unsupported size: xxx for JarEntry META-INF/MANIFEST.MF. Allowed max size: 8000000 bytes

JAVA_TOOL_OPTIONS=-Djdk.jar.maxSignatureFileSize=22000000

1.2.1

ADDED

Added the attributes section for Anonymization configuration file.
This section allows the management of what message/points attributes should be kept during anonymization.

1.2.1

ADDED

1.2.1

ADDED

1.2.1

ADDED

1.2.1

ADDED

1.2.1

KNOWN ISSUE

Certain versions of the Java Development Kit (JDK) require the manifest file
to stay within a file size limit. When the file exceeds the limit, you get this error:

Unsupported size: xxx for JarEntry META-INF/MANIFEST.MF. Allowed max size: 8000000 bytes

JAVA_TOOL_OPTIONS=-Djdk.jar.maxSignatureFileSize=22000000

1.2.0

ADDED

Added the attributes section for Anonymization configuration file.
This section allows the management of what message/points attributes should be kept during anonymization.

1.2.0

ADDED

1.2.0

ADDED

1.2.0

ADDED

1.2.0

ADDED

1.2.0

KNOWN ISSUE

Certain versions of the Java Development Kit (JDK) require the manifest file
to stay within a file size limit. When the file exceeds the limit, you get this error:

Unsupported size: xxx for JarEntry META-INF/MANIFEST.MF. Allowed max size: 8000000 bytes

JAVA_TOOL_OPTIONS=-Djdk.jar.maxSignatureFileSize=22000000

1.1.0

ADDED

Added a
deployment scenario
for Azure Virtual Machines (VMs).

1.1.0

CHANGED

Updated vulnerable dependencies to these versions:

* jackson: 2.15.2
* protobuf-java: 3.16.3
* zookeeper: 3.7.1
* parquet-hadoop: 1.13.1
* parquet-avro: 1.13.1
* snakeyaml: 2.0
* guava: 32.1.1-jre
* snappy-java: 1.1.10.3

1.1.0

ADDED

Added the Apache Kafka data connector
for both source and sink connections.

1.1.0

ADDED

Added the custom data format support.
This allows you to implement your own data format (as a Jar file) and use it
as a source or sink data format.

1.1.0

ADDED

Added the S3 Management Connector
which is designed for use with the
anonymization management queue.

1.1.0

ADDED

Added a pre-processing step that removes any message with future timestamps due to
inaccuracies before the anonymization process. The HERE_cleaning_point_dropped_invalid_timestamp
Flink metrics counter tracks the quantity of probe points eliminated in this phase.

1.1.0

ADDED

Added start and stop scripts for being able to run the demo Jupyter notebook
on Microsoft Windows OS. Please use demo-start.ps1 and demo-stop.ps1
with PowerShell.

1.1.0

ADDED

Added management event statistics to record management api events
(license/config) attempt and failure metrics. These metrics are visible
in the metrics counters section of the Flink dashboard.

The following counter were added:

* HERE_anonymization_management_events_total
* HERE_anonymization_management_events_licence_update_attempts
* HERE_anonymization_management_events_licence_update_failed
* HERE_anonymization_management_events_config_update_attempts
* HERE_anonymization_management_events_config_update_failed

1.1.0

ADDED

Added new license types and throttling per license type.
We now support these license types:

* ENTERPRISE: no throttling
* PREMIUM: throttling
* STANDARD: more throttling
* NON_PROFIT: no throttling but for non-profit organizations only

1.1.0

CHANGED

Updated staypoint prediction machine learning model with new freshly trained
one (bug-fixed training, updated libraries used for training).

1.1.0

FIXED

Fixed the anonymization algorithm issues that caused unnecessary probes to
drop when the stay point obfuscation mode was enabled.

1.1.0

ADDED

Added scripts and configuration examples to deploy HERE Anonymizer Self-Hosted
on AWS EC2. This includes deployment of RabbitMQ node as well as Apache Flink
job and task managers on EC2 instances.

This EC2 deployment proposal is hosted in a secure network architecture called
bastion host architecture or jump host architecture. It ensures secure
authorization and accessibility using bastion host, security group rules and
random SSH port.

Also added a script to safely and orderly terminate and cleanup EC2 instances
and related resources.

For further details please see the user guide.

1.1.0

ADDED

Added support to use HERE probe json format in demo notebook as a data source
with a possibility to directly paste json content to new textbox control.

1.1.0

ADDED

Added basic Flink REST API support for the demo notebook with a possibility
to display a table with available values from Flink demo accumulators.

1.1.0

CHANGED

Reduced log output of Kafka source connector by moving detailed log messages to debug level.

Added a deployment template for running Kafka with Kubernetes (kafka-k8s-deployment.template.yml).
For further details see the deployment folder of the released zip file.

1.1.0

CHANGED

The HERE Anonymizer Self-Hosted was updated to run with Java 11. For installation
and configuration of JDK, please refer to the steps outlined in the user guide.

1.1.0

CHANGED

The HERE Anonymizer Self-Hosted was updated to use Apache Flink version 1.18.1,
which brings new features such as operator-level state TTL within Table API & SQL
and enhances remote storage capabilities for hybrid shuffle, improving performance,
security and adaptability. Please ensure that your images (Docker etc.) are
compatible with Flink 1.18, for example for Docker you might use image
apache/flink:1.18-scala_2.12-java11.

1.1.0

CHANGED

The HERE_NOTICE document has been updated to include specific legally mandated
notices that are not covered by the LICENSE text or through licensing details
within the included dependencies.

1.1.0

ADDED

Added GPX data format support for source and sink. Please refer
to GPX (the GPS Exchange Format)
for more details. To use GPX data format, please declare environment
variables SOURCE_FORMAT=GPX and/or SINK_FORMAT=GPX.

1.1.0

FIXED

Fixed Azure AKS deployment scenario documentation regarding creating
a service-principal step.

1.1.0

KNOWN ISSUE

Certain versions of the Java Development Kit (JDK) require the manifest file
to stay within a file size limit. When the file exceeds the limit, you get this error:

Unsupported size: xxx for JarEntry META-INF/MANIFEST.MF. Allowed max size: 8000000 bytes

JAVA_TOOL_OPTIONS=-Djdk.jar.maxSignatureFileSize=22000000