Using the data object retrieval APIs

Data Lake is a scalable, elastic object store for capturing raw data in its original and native format. Infor Data Lake provides interfaces for these tasks:

  • Retrieving a list of data objects stored in Data Lake.
  • Retrieving a single data object by data object ID.
  • Marking an object as corrupt.
  • Retrieving statistical information about the stored object.

Interface and consumption methods are exposed through the Data Lake API Service registered within the ION API suite for Infor Data Fabric. For more information on how to use ION APIs and how to interact with Swagger documentation for the API methods, see Infor ION API Administration Guide.

By default, content in Data Lake is stored, and streamed to clients, in a compressed state. For exceptionally large content retrievals, especially through the /dataobjects/byfilter API, this deflating content method ensures that performance of the gateway and requesting clients remains nominal.

Authorized API applications and RESTful API clients that are used for API testing can advertise supported content encoding to the server. To stream and persist data in a compressed format, the requesting party can configure their request with the request header:

  • Accept-Encoding: deflate

    Using the “identity” value in a request HTTP header, clients can stream their requested content with no encoding in place. This setting is typically configured using the request format:

  • Accept-Encoding: identity

    Not all clients support the “identity” value. See your API application or client’s documentation to determine whether these request HTTP header values are supported.

Note:  The Data Lake JDBC driver is available only for multitenant Cloud customers using Birst.