Podcast
Questions and Answers
Who is allowed to select the Auto Lineage option for building lineage automatically?
Who is allowed to select the Auto Lineage option for building lineage automatically?
- Only the Connector Creator (correct)
- Any user with admin access
- Users with a standard user role
- Integration Admins
What is the purpose of the Codes Loaded field in the Auto Lineage process?
What is the purpose of the Codes Loaded field in the Auto Lineage process?
- To indicate the total number of source codes crawled (correct)
- To display the number of processed codes
- To provide the last updated count of codes
- To show the remaining tasks for lineage building
What must be done in the connector setup before building lineage automatically?
What must be done in the connector setup before building lineage automatically?
- Complete all prerequisite configurations and validate the setup (correct)
- Assign roles to all users involved
- Install additional software
- Only add the connector details
Which user role can configure the crawler settings for a validated connector?
Which user role can configure the crawler settings for a validated connector?
What information does the Last Job Status field provide?
What information does the Last Job Status field provide?
What does the Codes Unprocessed field indicate during the lineage-building process?
What does the Codes Unprocessed field indicate during the lineage-building process?
In building lineage, which option refers to the manual configuration as opposed to automatic?
In building lineage, which option refers to the manual configuration as opposed to automatic?
What does the Codes Processed field show during the lineage-building process?
What does the Codes Processed field show during the lineage-building process?
Which option allows users to build lineage only for codes that have been newly added or modified?
Which option allows users to build lineage only for codes that have been newly added or modified?
What is the maximum duration for the look back period when configuring query log settings?
What is the maximum duration for the look back period when configuring query log settings?
Which query type is NOT an option for inclusion in the query log settings?
Which query type is NOT an option for inclusion in the query log settings?
What particular information does the 'Schema Name' field provide to the user?
What particular information does the 'Schema Name' field provide to the user?
Which action would you take if you want to ignore the queries of a specific user from the logs?
Which action would you take if you want to ignore the queries of a specific user from the logs?
In terms of building auto lineage, what does the 'Export Source Code to File' option do?
In terms of building auto lineage, what does the 'Export Source Code to File' option do?
Which of the following is a function of the 'Build Lineage for All Codes' option?
Which of the following is a function of the 'Build Lineage for All Codes' option?
What does the 'Code Name' section help users to do after executing a job?
What does the 'Code Name' section help users to do after executing a job?
What does the status 'SUCCESS_LINEAGE_BUILD' indicate about a query's lineage?
What does the status 'SUCCESS_LINEAGE_BUILD' indicate about a query's lineage?
Which of the following statements accurately describes the 'Graphical View' of lineage in OvalEdge?
Which of the following statements accurately describes the 'Graphical View' of lineage in OvalEdge?
What is a characteristic of the status 'SUCCESS_LINEAGE_DOES_NOT_EXIST'?
What is a characteristic of the status 'SUCCESS_LINEAGE_DOES_NOT_EXIST'?
In which context is 'Tabular View' most beneficial for users?
In which context is 'Tabular View' most beneficial for users?
What is indicated by the status 'SUCCESS_WITH_TEMP'?
What is indicated by the status 'SUCCESS_WITH_TEMP'?
What is the main purpose of accessing lineage data in the Data Catalog?
What is the main purpose of accessing lineage data in the Data Catalog?
Which lineage status suggests that the data lineage parsing was successful but possibly includes temporary tables?
Which lineage status suggests that the data lineage parsing was successful but possibly includes temporary tables?
How can users enrich their understanding of lineage through the data provided in the Data Catalog?
How can users enrich their understanding of lineage through the data provided in the Data Catalog?
Study Notes
Auto Lineage Prerequisites
- Create a connection in Administration > Connectors by entering connector details and license options.
- Only the Connector Creator can select the Auto Lineage option to enable automatic lineage tracking of data origins and paths.
- Ensure all connection details are saved and validated for correct setup.
Crawler Settings
- Users can select validated connectors, access settings via the nine-dot menu, and choose crawlers as needed.
- Configuration options vary between different connector types like RDBMS and reporting connectors.
Building Lineage
- Lineage can be built using Auto Lineage or Manual Lineage methods.
Auto Lineage
- Provides a structured overview with key fields like:
- Connector Name: Identifies data source for lineage.
- Codes Loaded: Total source codes crawled.
- Codes Processed: Number of processed codes.
- Codes Unprocessed: Count of codes yet to be processed.
- Last Updated Count: New codes added since the last crawl.
- Last Job Status: Updates on job submissions for lineage.
- Last Run Date: Timestamp of the last lineage-building job.
Ways of Building Auto Lineage
- Select source codes and use corresponding options from the nine-dot menu:
- Build lineage for selected codes.
- Build lineage for new or changed codes.
- Build lineage for all codes.
- Fetch code log and build lineage.
Query Log Settings
- Configurable options include:
- Query: Displays retrieval queries from the schema.
- Look back Period: Fetch queries from the specified days, maximum seven.
- Include Query Type: Users can select query types such as Select, Insert, Update, Delete.
- Exclude Users: Option to exclude specified users from query logs.
- Schema: Select a specific schema for query log settings.
Viewing Source Codes
- Access detailed information on queries in the "Build Auto Lineage" page post execution, including:
- Schema Name: Structure and context of code.
- Code Name: Identifies the code.
- Lineage Status: Indicates progress of lineage creation with various status types.
Lineage Status Types
- Successful lineage builds are categorized as:
- SUCCESS_LINEAGE_BUILD: Complete and successful lineage recognized.
- SUCCESS_WITH_TEMP: Successful with temporary tables.
- SUCCESS_LINEAGE_DOES_NOT_EXIST: No lineage discovered.
- SUCCESS_LINEAGE_FIXED: Lineage fixed with real tables.
- SUCCESS_LINEAGE_PARTIALLY_BUILD: Lineage partially built.
Manual Lineage
- Users can build lineage manually with separate configurations and mappings.
Lineage Maintenance & Column Mapping
- Processes for maintaining lineage and adding column mappings are available.
Accessing Lineage in Data Catalog
- Lineage information is accessible at the object level within the Data Catalog.
- The lineage tab displays connections and data flow through source systems.
Graphical and Tabular View
- Graphical View: Visual representation of lineage with connections between data objects.
- Tabular View: Structured table format shows upstream and downstream lineage, which can be downloaded for in-depth analysis.
Studying That Suits You
Use AI to generate personalized quizzes and flashcards to suit your learning preferences.
Related Documents
Description
Test your knowledge on Auto Lineage and manual lineage methods for data tracking. This quiz covers the prerequisites, crawler settings, and key components of building lineage. Perfect for Connector Creators looking to reinforce their understanding of data lineage tracking!
