Read and Write Limitations

Read limitations

  • Metadata Insights does not interpret case-sensitive field names as different names. If two tables or column names use the same name but different cases, they are interpreted as duplicate names. If a model store contains such field names, the deployment of that model store fails.

    For example, fields like DeDup, Dedup, and DEdup are interpreted as duplicate names. The deployment of a model store containing such case-differentiated fields fails.

  • If a Data Source, physical model, logical model or model store has a dependency on a JDBC-specific data source, it cannot be imported or exported using the Administration Utility.

Write limitations

While writing to a database source using the Write to DB stage in Enterprise Designer, there are certain limitations.

  • Creation of tables while writing to a database source using a Metadata Insights connection is not supported. If you click Create Table while using a Metadata Insights connection, a runtime exception is displayed.
  • Metadata Insights does not support unified writes to multiple connections simultaneously. You can write to a single source at a time.
  • Dropping and recreating any table while writing to a database using a Metadata Insights connection is not supported.
  • Delete and truncate operations are not supported while writing to a database using Metadata Insights. Only insert and update operations are supported.
  • Metadata Insights performs a commit after completion of each batch insert. The Batch count to commit cannot be changed to any other value other than 1.
    In the Runtime tab of the Write to DB stage in Enterprise Designer, the Batch count to commit field can only have the value 1 for Metadata Insights.
    Note: A batch consists of 1000 records by default. You can configure the batch size according to your system, in the Runtime tab of the Write to DB stage in Enterprise Designer.
  • For batch inserts, the feature Commit at the end is not supported. This feature refers to performing a commit after all batches are complete. In Metadata Insights, a commit is performed at the end of each batch insert completion.