GCP Pub Sub Adapter Restrictions

Note the following GCP Pub Sub Adapter restrictions.

  • The Protocol buffer message structure is not currently supported by the GCP Pub Sub Adapter.
  • The GCP Pub Sub Adapter's publish request has a limit of 10 MB (total size) or 1,000 messages.
  • The GCP Pub Sub Adapter allows you to pull up to 100 messages per request.
  • The GCP Pub Sub Adapter can pull or publish only one XML message per request.
  • When configuring a trigger connection with the Avro binary message format and your Avro schema contains fixed data types, the decoded value may differ from the published value. For instance, the character A is decoded to its Dec equivalent of 65. Similarly, the string AA is decoded to the array [65, 65]. See the ASCII Table.
  • The GCP Pub Sub Adapter displays 1000 topics for selection at a time on the Configuration page of the Adapter Endpoint Configuration Wizard.
  • If a subscription already exists for the consumption of messages from a GCP Pub Sub topic, you can't update or change a topic, subscription filter, and message ordering.
  • If a topic or subscription already exists for publishing, pulling, or acknowledging messages, you can change the topic or subscription in the mapper at runtime. However, the corresponding request and response mappers remain the same as configured on the Adapter Endpoint Configuration Wizard page.
  • The refresh token has the following restrictions:
    • Only 100 refresh tokens are allowed, per Google Account per OAuth 2.0 client ID.
    • There are other restrictions. See Refresh Token Expiration.

Note:

There are overall service limits for Oracle Integration. A service limit is the quota or allowance set on a resource. See Service Limits.