Google Big Query Nullable Attribute is Always "false" After OEMM Import
Last updated on DECEMBER 19, 2016
Applies to:Oracle Enterprise Metadata Management - Version 12.1.3 and later
Information in this document applies to any platform.
On OEMM 188.8.131.52, after a successful import from Google BigQuery using the Oracle Enterprise Metadata Management via Google BigQuery native bridge, the Nullable attribute is always "false", while with not required fields the Nullable attribute should be set to "true".
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms