Please enable JavaScript to view this site.

Data Dictionary Data Model Data Dictionary Forums

Navigation: Catalog: DataDictionary > Schemas > Schema: Invantive > Tables

SYSTEMDATACONTAINERHTTPCACHECONTENTS: Data Dictionary System Data Container HTTP Cache Contents

Cached results of HTTP calls executed by providers.

Catalog: DataDictionary

Schema: Invantive

Alias: dct

Label: System Data Container HTTP Cache Contents

This is a read-only view. The Data Dictionary API may not support changing the data or the Invantive UniversalSQL driver for Data Dictionary does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the Data Dictionary API.

View Columns

The columns of the view SYSTEMDATACONTAINERHTTPCACHECONTENTS are shown below. Each column has an SQL data type.

Name

Data Type

Label

Required

Documentation

CACHE_FIRST_HIT_UTC

datetime

Cache First Hit

 

Date at which the cache entry was first hit (UTC).

CACHE_HITS_PER_HOUR

int32

Cache Hits per Hour

 

Number of times per hour the cache entry is used since creation.

CACHE_HITS

int32

Cache Hits

 

Number of times the cache entry was used after initial storage.

CACHE_KEY

string(4000)

Cache Key

☑

Unique key.

CACHE_LAST_HIT_UTC

datetime

Cache Last Hit

 

Date at which the cache entry was last hit (UTC).

CREATED_UTC

datetime

Created

 

Date at which the cache entry was created (UTC).

HTTP_METHOD

string(30)

HTTP Method

☑

HTTP method.

HTTP_REQUEST_BODY_GZIPPED_LENGTH

int64

HTTP Request Body Gzipped Length (Bytes)

 

Number of bytes in the gzipped text request body.

HTTP_REQUEST_BODY_GZIPPED

byte[]

HTTP Request Body (GZipped)

☐

HTTP request body as gzipped contents.

HTTP_REQUEST_BODY_LENGTH

int64

HTTP Request Body Length

 

Number of characters in the text request body.

HTTP_REQUEST_BODY

string(1000000)

HTTP Request Body

☐

HTTP request body.

HTTP_RESPONSE_BODY_BINARY

byte[]

HTTP Response Body (Binary)

☐

HTTP response body as binary contents.

HTTP_RESPONSE_BODY_BYTES_GZIPPED_LENGTH

int64

HTTP Response Body Gzipped Length (Bytes)

 

Number of bytes in the gzipped binary response body.

HTTP_RESPONSE_BODY_BYTES_LENGTH

int64

HTTP Response Body Length (Bytes)

 

Number of bytes in the binary response body bytes.

HTTP_RESPONSE_BODY_GZIPPED_LENGTH

int64

HTTP Response Body Gzipped Length (Bytes)

 

Number of bytes in the gzipped text response body.

HTTP_RESPONSE_BODY_GZIPPED

byte[]

HTTP Response Body (GZipped)

☑

HTTP response body as gzipped contents.

HTTP_RESPONSE_BODY_LENGTH

int64

HTTP Response Body Length

 

Number of characters in the text response body.

HTTP_RESPONSE_BODY

string(1000000)

HTTP Response Body

☑

HTTP response body.

HTTP_RESPONSE_HEADERS

string(16000)

HTTP Response Headers

☐

HTTP response headers.

MANAGED_THREAD_ID

int32

Managed Thread ID

☐

Managed thread ID.

PROVIDER_DATA_CONTAINER_ALIAS

string(4000)

Data Container Alias

☐

Data container alias.

PROVIDER_DATA_CONTAINER_ID

string(4000)

Data Container ID

☐

Data container ID.

PROVIDER_DESCRIPTION

string(16000)

Provider Description

☑

Provider description.

PROVIDER_INSTANCE_UID

guid

Provider Instance UID

☑

Unique ID of the provider instance.

PROVIDER_NAME

string(240)

Provider Name

☑

Name of the provider.

PROVIDER_SHORT_NAME

string(240)

Provider Short Name

☑

Provider short name.

REQUEST_ID

string(60)

Request ID

☐

Request ID.

REQUEST_URL

string(4000)

Request URL

☑

Request URL used to retrieve the answer.

TASK_ID

int32

Task ID

☐

Task ID.

 

18-10-2024 06:49 Version 24.0.345-PROD+4945

X

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

  • Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
  • Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
  • Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
  • Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
  • Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
  • Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
  • Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
  • Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.
  
Disclaimer