How to manage Inferred Objects

Encountering Inferred Objects for certain Data Objects in Cloudera Octopai is a common issue that can occur when an object has not been extracted and uploaded to Cloudera Octopai, but appears in the lineage due to its association with a script.

When viewing the lineage in Cloudera Octopai, you might come across Data Objects that are displayed as Inferred Objects. This happens when Cloudera Octopai lacks sufficient information to determine the type of the Data Object, even though it is directly related to a Report or ETL. Cloudera Octopai fails to recognize the associated Database Name and Schema through their keys, resulting in the Inferred Objects classification.

Click the Information i button in the object radial button, and copy the object name from the Properties section.

Figure 1. Inferred Object Properties
Paste the object name in the Cloudera Octopai Discovery space.

Figure 2. Discovery space

You can identify that the Inferred Object is part of SSIS scripts but was not physically uploaded to Cloudera Octopai during the Metadata extraction process.
To resolve this issue, perform the following steps:
1. Verify the permissions on the Database associated with the object, based on the tool prerequisites.
2. Take note of the path of the Report or ETL shown in the Data Object Properties section and paste it to the Admin Console > Connection Parameters tab. The example is valid for ETL.
  Figure 3. Path in the Properties section
  
  Figure 4. Switch to Admin Console
  
  Figure 5. Admin Console
  
  Figure 6. Add the connection parameters
3. An Cloudera Octopai night job will handle the rest.
Edit bulk connection parameters.
1. Export the list to Excel.
2. Complete the Reports - Database and Schemaand ETL - Database missing data in the Excel file.
3. Upload the modified file to Cloudera Octopai.
4. An Cloudera Octopai night job will handle the rest.

If you still encounter Inferred Objects, contact Cloudera Support.