When using a TIBCO Data Virtualization (TDV) custom adapter to introspect the currently unsupported OSIsoft PI, a GUID column will be introspected as the "OTHER" type due to TDV's inability to recognize this column type from OSIsoft. This ambiguous column typing (OTHER) can prevent its participation in a TDV view or procedure later.

While this datasource remains unsupported at the time of writing, there is a way to make TDV interpret the GUID type as a varchar.

In your \conf\adapters\custom\<your custom adapter name>\<your custom adapter name>_values.xml file,
add this to the uncommented active block of xml:

<!--Adding an assigned varchar datatype for the GUID type -->
   <ns415:attribute>
      <common:name>/custom/jdbcds_datatype_guid</common:name>
      <common:type>STRING</common:type>
      <common:value>varchar</common:value>
      <common:configID>jdbcds.datatype.guid</common:configID>
   </ns415:attribute>


The use of a namespace 'ns415' is merely an arbitrary example here, you can name yours as appropriate to your file's contents. After saving the edit, restart the TDV service and re-introspect the PI data source or test by introspecting a new datasource with this adapter. Verify the column with a Native Type of GUID is now interpreted as a varchar Type in TDV.

 

This concerns a custom unsupported datasource.