Big Data Management : 2019 : February Skip navigation
2019

What are we announcing?

Informatica Big Data Release 10.2.2

 

Who would benefit from this release?

This release is for all customers and prospects who want to take advantage of the latest Big Data Management, Big Data Quality, Big Data Streaming, Enterprise Data Catalog, and Enterprise Data Lake capabilities.

 

What’s in this release?

This update provides the latest ecosystem support, security, connectivity, cloud, and performance while improving the end-to-end user experience.

 

Big Data Management (BDM)

 

Enterprise Class

  • Zero client configuration: Developers can now import the metadata from Hadoop clusters without configuring Kerberos Keytabs and configuration files on individual workstations by leveraging the Metadata Access Service. Metadata Access Service now supports OS Profiles (when enabled) and can be executed on multiple nodes as a GRID
  • Mass ingestion: Data analysts can now ingest relational data into HDFS and Hive for both initial and incremental loads. Mass Ingestion service can now fetch incremental data based on date columns or numeric columns, persist the last values fetched in the previous run and automatically use them in the subsequent runs.
  • SQOOP enhancements: SQOOP connector now supports high levels of concurrency and the ability to fetch incremental data
  • Bitbucket Support: Big Data Management administrators can now configure BitBucket (in addition to Perforce, SVN, and Git) as the external versioning repository
  • Go-Live assistance: Release managers can now incrementally deploy objects into applications instead of overwriting the entire applications
  • Robustness & Concurrency: Data Integration Service is now highly robust can process 6 times more concurrent requests than it did in previous releases. The startup time of the Data Integration Service is improved by 2x.
  • Resilience: The Data Integration Service can now automatically reparent to the jobs that continue to run on the Hadoop clusters - even after the Data Integration Service experiences a crash or unexpected restart
  • Queuing: Data Integration Service is now enhanced to queue the jobs submitted to it and persists the requests so that the requests do not have to be resubmitted in case the Data Integration Service experiences a crash or unexpected restart
  • REST Operations Hub: Operations teams can now perform REST queries that fetch the job status, row level statistics and other monitoring information for deployed mappings
  • Dynamic mappings: Dynamic mappings can now be used across various data types and various ecosystems including AWS and Azure 

Advanced Spark

  • Advanced Data Integration: Spark now supports high precision decimals and executes the Python transformation many times faster than previous releases
  • Dynamic mappings: Complex data types such as Arrays, Structs and Maps can now be used in dynamic mappings
  • Debugging made easy: With the introduction of automatic Spark-based data preview, developers can now debug advanced spark mappings that contain complex types and stateful functions as easily as they preview the native mappings
  • CLAIRE integration: Big Data Management now integrates with Intelligent Structure Discovery (that is part of Informatica Intelligent Cloud Services) to provide machine learning capabilities in parsing the complex file formats such as Weblogs

Cloud and Connectivity

  • Core connectivity:
    • SQOOP connector is optimized to run faster and is designed to eliminate staging wherever possible
    • HBase sources and targets can be used with dynamic mappings
    • Schema drift is now supported. Changes in the source systems can now be applied on to the Hive targets
    • Data can now be loaded to Hive in Native mode
  • Amazon ecosystem:
    • Developer productivity is increased with the ability to use S3 and Redshift sources and targets in dynamic mappings
    • S3 data objects now support wild card characters in the file names.
    • File names can be dynamically generated for S3 objects using the target based FileName port
    • Many additional properties in the Redshift data objects can now be parameterized.
  • Azure ecosystem:
    • Developer productivity is increased manifold with the ability to use ADLS and WASB sources and targets in dynamic mappings
    • Intelligent Structure Discovery is now supported with Azure ADLS and WASB
  • Azure Databricks: BDM now offers support for managed cluster computation on Azure Databricks
  • Containerization: Implementation teams can now build docker containers of BDM images and deploy them per their enterprise needs

 

Platform PAM Update

 

  • Operating System Update:
    • RHEL - 7.3 & 6.7 - Added
    • RHEL - 7.0 , 7.1 ,7.2 and 6.5 , 6.6 - Dropped
    • SUSE 12 SP2 - Added
    • SUSE 12 SP0 & SP1 -  Dropped
    • SUSE 11 SP4 - Added
    • SUSE 11 SP2 & SP3 - Dropped
  • Database support:
    • Azure SQL DB  - Added
  • Authentication Support:
    • Windows 2012 R2 & 2016 (LDAP and Kerberos) - Added
    • Azure Active Directory (LDAP only) - Added
  • Tomcat Support:
    • v 7.0.88 (No update)
  • JVM Support Update:
    • Azul OpenJDK 1.8.0_192 - Added
    • Oracle Java - Removed
    • Effective Informatica 10.2.2, Informatica platform supports Azul OpenJDK, instead of Oracle Java since Oracle has changed its Java licensing policy, ending public updates for Java 8 effective January 2019. Azul OpenJDK would come bundled with the product.
  • Model Repository - Versioned Controlled
    • BitBucket Server 5.16 Linux (hosting service for repositories) - Added
    • Perforce - 2017.2 - updated
    • Visual SVN - 3.9 - updated
    • Collabnet Subversion Edge - 5.2.2 - updated
  • Others
    • Microsoft Edge Browser (Win 10) 40.15 - updated
    • Internet Explorer -11.x - updated
    • Google Chrome- 68.0.x - updated
    • Safari - 11.1.2 ( MacOS 10.13 High Sierra) - updated
    • Adobe Flash Player  - 27.x - updated

Informatica Docker Utility

  • Use the Informatica Docker Utility to create a custom Docker Container images for Big Data Management and then run the Docker Container image to create an Informatica Domain. The Informatica Docker utility provides a quick and easy process to install the Informatica Domain in Docker Containers.

 

Big Data Streaming (BDS)

 

Enterprise Class Streaming Data Integration

  • CLAIRE integration: Big Data Streaming now integrates with Intelligent Structure Discovery (that is part of Informatica Intelligent Cloud Services) to provide machine learning capabilities in parsing the complex file formats and support dynamically evolving schemas
  • Resilience: Data Integration Service can now automatically reparent to the jobs that continue to run on the Hadoop clusters - even after DIS experiences a crash or unexpected restart
  • Queuing: The Data Integration Service is now enhanced to queue the jobs submitted to it and persist the requests so that the requests do not have to be resubmitted in cases the Data Integration Service experiences a crash or unexpected restart
  • Incremental Deployment: Release managers can now incrementally deploy objects into applications instead of overwriting the entire applications
  • Latest Spark Version support: Big Data Streaming now supports Spark 2.3.1
  • Java Transformation support on HType Data

 

Advanced Cloud Support

  • Amazon ecosystem:
    • Profile based authentication support for AWS Kinesis service
    • Cross Account authentication support for AWS Kinesis Streams service
    • Support for secure EMR cluster with Kerberos authentication
  • Azure ecosystem:
    • Support for deploying streaming mappings with an Azure EventHub source in Azure cloud with an HDInsight cluster

 

Enhanced Streaming Data Processing and Analytics

  • Spark Structured Streaming support
    • Big Data Streaming now supports processing based on event time
    • Big Data Streaming can now integrate “out of order” data and process it in the same order as it was generated at the source
  • Message Header support
    • Better streaming data processing based on message metadata
    • Supports header metadata-based analytics without parsing the complete message
  • Machine Learning and Advanced Analytics support
    • Supports execution of Python script in streaming mapping with improved performance
  • Latest Apache Kafka version support
    • Big Data Streaming now supports Kafka 2.0

 

Intelligent Structure Discovery

 

Intelligent Structure Discovery is now integrated with Big Data Management and Big Data Streaming on Spark to allow high performance parsing of various file types with data drift handling.

  • Performance enhancements
    • Improved runtime performance for some use cases (JSON and XML) by up to 10X compared to the previous release
  • Improved handling of Data Drift with an Unassigned Port
    • Data not identified by the model will be routed to the unassigned port and not dropped
  • Data Type propagation
    • Intelligent Structure Discovery automatically discovers the model field names data types. When importing the model to the platform these Identified fields are propagated to the transformation with the corresponding data type
  • Handling of “Special” Characters
    • Intelligent Structure Discovery Models that contain characters that do not comply with the platform naming convention are automatically replaced with a compliant character
  • Enhanced Parsing Engine
    • Improved handling of XML files (Attributes and namespaces).
    • Support Discovery and parsing of multiple sheet Excel files
  • Improved Design Time
    • The Intelligent Cloud Design is enhanced with a Find functionality and the ability to apply actions on multiple elements (for example rename)

 

Enterprise Data Lake (EDL)

 

Core Data Preparation

 

  • New Advanced Data Preparation functions: Users can utilizemore than 50 new advanced data preparation functions for Statistical, Text, Math, Date/Time manipulations. Window functions help with calculation on a data window such as Rolling Average, Rolling Sum, Lead/Lag, Fill, Sessionize etc. Cluster and Categorize function uses phonetic algorithms to cluster data and then help users easily standardize. Delete duplicate rows function helps removing exact duplicates from the data.
  • Apply Active Rules: Users can Apply external pre-built rules with Active Transformations to support DQ processing like Fuzzy Matching and Consolidation. Expert users can use Informatica Developer Tool to build complex rules including active transformation and then expose those to the data preparation users. This helps collaboration, standardization, extensibility and re-usability.
  • Data Preparation for Avro and Parquet files: Users can add Avro and Parquet files to a project in addition to Hive tables and other file formats such as delimited files and JSONL files. This eliminates the need for creating a Hive table on top of files. They can structure the hierarchical data in row-column form by extracting specific attributes from the hierarchy, and canexpanding (or exploding) arrays into rows in the worksheet.

 

Self-service and Collaboration

  • Functional and UX Improvements: Users can apply conditions during aggregation, reorder sheets as needed. Recipe panel clearly shows steps that failed during data and recipe refresh. The “Back-in-time” functionality is now more on-demand to improve user experience for Edit step, Copy/Paste step etc.
  • Improved CLAIRE based recommendations: Improved user productivity with additional CLAIRE based recommendations for alternate assets upstream and related by PK-FK. During join, users are prompted to review sampling criteria in case of low overlap of join keys. User also get new data prep suggestions based on data types that are handy shortcuts to frequently used functions.
  • Ability to add recipe comments: Users can add comments to various recipe steps, view comments by other users for better collaboration and auditing.
  • Save mappings for Recipes: Users have option to save mappings corresponding to recipes for a worksheet instead of executing full at-scale execution and creation of new output table. This way expert IT users can inspect the mapping and execute at the appropriate time and resource levels.

 

Enterprise Focus

  • Support for S3, ADLS/WASB and MapR-FS files: Users can prepare data files directly from various file systems such as AWS S3, Azure ADLS and WASB and also for MapR-FS in addition to HDFS.
  • Spark Execution: Spark is used as the default execution engine for better performance and it also allows data prep users apply executing rules built with mapplets using advanced transformations such as Python transforms .
  • Autoscaling on AWS EMR: Customers can start with minimal number of EMR nodes and then auto-scale based on rules for resource consumption to lower overall total cost of ownership for data lakes in AWS.
  • Integration with Informatica Dynamic Data Masking: Data protection and governance is improved using Informatica Dynamic Data Masking. Based on DDM policies, data will be masked at various touch points such as preview, prepare, publish and download etc.
  • Scalability improvements: Performance, scalability and longevity improvements have been made in various services to support enterprise scale deployments with large number of users.

 

Enterprise Data Catalog (EDC)

 

  • Collaboration: Data Analysts, Data Scientists and Line of Business users will now be able to find the most relevant, most trusted datasets for their analytic needs faster with Enterprise Data Catalog(EDC) v10.2.2. EDC 10.2.2 includes both top down and bottom up collaboration capabilities that bring to forefront the otherwise deeply siloed knowledge about trustworthiness and usefulness of datasets. This new capability will help data consumers save weeks, sometimes months of efforts in finding and using the right dataset.
    • Dataset Certifications: With EDC v10.2.2, Subject Matter Experts, Data Stewards and Data Owners will be able to certify datasets and data elements adding context information like data usage and constraints. Using EDC’s machine learning based semantic search, EDC will surface these certified datasets at the top of the search results to guide users to use these certified datasets among all other similarly named datasets in the organization.
    • Reviews and Ratings: Data consumers like Data Analysts and Data Scientists can now review and rate datasets. EDC pushes datasets that are rated highly to the top of the search results. There are new facets that are available to narrow down search results to highly rated datasets only.
    • Questions and Answers: Users will be able to use a new question/answer platform that allows subject matter experts to answer the most common questions of the data consumers. This will help data consumers to find experts, ask questions and see answers in the context of the dataset. For subject matter experts, this will mean less work and more reuse of information as they need not response to multiple emails and phone calls for the same queries on data.
  • Change Notifications: With change notifications, EDC will provide data consumers an easy way to stay on top of any metadata changes happening to their data assets. Users will be able to follow any datasets in the catalog and whenever scanners detect any changes to these datasets, both in-app and email notifications will be sent to the user. Additionally super users like database administrators, stewards and owners can follow entire databases and other metadata resources to get notified on any changes happening in the database.
  • Intelligent Business Glossary Associations: One of the most important and most tedious data governance tasks is to associate business glossary terms to physical data assets. In EDC v10.2.2 the glossary association process is a lot more easier. By using the CLAIRE based AI engine, the right business glossary terms are matched with the right physical assets at the data element level. This method uses the data domain discovery and data similarity capabilities to power automatic glossary associations with the goal of making the data stewards and business analysts responsible for this task about 2X more productive by providing these machine learning based assistants.
    • Business Glossary Assignment Report: EDC v10.2.2 includes a new business glossary assignment report at the resource level to help data stewards understand glossary association coverage for a resource in one place. Data Stewards will also be able to curate(accept/reject) all glossary recommendations from this new report as well.
  • Metadata and Profile Filters: Catalog and profile only selected metadata from databases, data warehouses and big data sources. Users will be able to provide both inclusion and exclusion criteria to filter datasets that are cataloged and profiled. The filter criteria can be a list of names or regular expressions that are matched against table/view names.
  • Remote Metadata Scanner: Catalog metadata from data sources that are behind a firewall or are remote with port restrictions. With EDC v10.2.2 a direct network connection from the Catalog to the data source is no longer required. Remote Metadata Scanner Utility can be downloaded and setup in a server close to the data source/in the same network and the extracted metadata can be uploaded to the catalog. Currently only metadata scan is supported for Oracle, SQL Server and Teradata.
  • New Scanners
    • Workday: Manage Workday metadata for governance, risk/compliance andself service analytics
    • Google BigQuery: Manage Google BigQuery metadata for governance, risk/compliance andself service analytics
  • Performance Improvements: EDC v10.2.2 includes a new graph schema that improves the performance of tasks like parameter assignment (63x faster), resource purge (5x faster) and re-index (2.5x faster). Additionally, there are all round scanner performance improvements in the areas of auto-connection assignments (340x faster), SAP Business Objects scanner (1.5x faster), Oracle scanner (2x faster) and IBM Cognos scanner (2x faster).

 

PAM for Informatica 10.2.2: https://network.informatica.com/docs/DOC-18072

 

Informatica 10.2.2 Release Notes

 

Introduction

Customers use Informatica Big Data Management (BDM) product to access metadata (using developer client tool) as well as data (through Data Integration Service) for Hadoop based sources (HDFS files, HBase, Hive, MapR-DB) as well as non-Hadoop sources. One of the major pain points with accessing Hadoop data sources is related to the non-trivial configuration effort that goes in configuring access to the Hadoop systems including the Kerberos configuration using kinit tool, keytab files etc. This document explains how Metadata Access Service simplifies the configuration effort and also enables more secure metadata access from Hadoop data sources.

Metadata access process without Metadata Access Service

The metadata access process before Metadata Access Service to import metadata from a Hadoop data source like HDFS files, HBase, Hive, MapR-DB included the following steps. Note that the below steps were needed to be performed on each developer client box installation that needed to be configured to access metadata from a Hadoop data source.

  1. Informatica developer needs to execute kinit command on the developer client box to get and cache the initial ticket-granting ticket from the KDC server. This requires providing appropriate keytab and krb5 configuration files to individual developers and asking them to execute the command manually before requesting metadata using the developer client. Since keytab files include sensitive information, distributing the same to each developer box appropriately and asking developers to execute these commands manually requires a lot of careful handling on the customer side.
  2. If the cluster is SSL enabled, developer needs to import the corresponding certificates in each developer client installation using keytool commands to import the certificates in the jre folder.
  3. Developer also needs to export the cluster configuration XML from Informatica Admin console and manually extract the zip file and place the same into the 'conf' folder under the appropriate Hadoop distribution folder on the developer client installation.
  4. Developer also needs to update the variable 'INFA_HADOOP_DIST_DIR' defined in 'developerCore.ini' file on each client box under the client installation if connecting to a Hadoop distribution other than the default Cloudera version.
  5. Finally, after performing the above steps (needed on each developer client box), developer can launch the import wizard for the data source in the developer client to import and save the metadata.

As apparent from the above steps, performing the above steps on each developer client box (customer may potentially have tens or even hundreds of developer client installations) is a big hassle. Metadata Access Service was introduced to ease the above configuration and also provide improved security architecture w.r.t metadata access for Hadoop data sources.

 

Metadata access using Metadata Access Service

Metadata Access Service is intended for enabling metadata access to Hadoop data sources(HDFS Files, HBase, Hive and, MapR-DB) from the developer client tool. This is a mandatory service that must be created before any metadata access from Hadoop sources listed can be performed via the developer tool. The service can be created using either Informatica admin console or through command line using infacmd tool.

Metadata Access Service needs to be configured only once by the Informatica Administrator (similar to how existing services like Data Integration Service used for data access by Informatica mappings). If there is a single metadata access service configured and enabled, it'd get picked up automatically by the developer client installations, else the default metadata access service can be selected once at the developer client level and the developer selection gets cached until changed. Metadata Access Service provides a lot of features and advantages compared to the accessing metadata directly from developer client tools.

  1. Metadata Access Service enables configuration of Kerberos specific attributes like keytab location, principal name at a single location.  There is no longer a need to run the kinit command on any developer client boxes since appropriate keytab file location and Service Principal Name can be provided in the MAS configuration in the Admin Console. This is also more secure as we no longer need to distribute and use sensitive information to developer boxes.
  2. Developer can configure multiple metadata access services either for load balancing purpose (to reduce the load on a single service process) or to connect a different Hadoop distribution type (Cloudera, Hortonworks, MapR etc) or a system with a different configuration (keytab, Service Principal Name) is desired. Hence, there is no need to perform steps like downloading cluster configuration files into localHadoop distribution folder on the developer client. Developer can select the appropriate Metadata Access Service name in the developer client as the default service for the current developer client session in case multiple services are configured (similar to how default DIS service is selected).
  3. Configuring access to SSL enabled clusters is also simplified as the SSL certificates for the clusters need to be imported (using keytool command) on a single node (where MAS is configured to run) and not on each developer client box.
  4. Developer can also enable the option to use 'logged in user as impersonation user' similar to DIS to enable current logged in user credentials in developer client box to be used while accessing any Hadoop resources.
  5. Support for centralized logging is enabled, hence, any metadata access related error message would also get captured and persisted in a centralized location (in addition to showing in a popup dialog box as earlier) just like other services like DIS and can be viewed (with features like filtering enabled) in Informatica Admin Console service log console in a similar manner. Without Metadata Access Service, the error messages were shown in a pop-up dialog only in developer tool but could not be retrieved later once the dialog box with an error message is closed by the developer.
  6. Metadata Access Service can be configured to interact with developer client tool over either http or more secure https protocol just like other Informatica services like DIS. Developer can configure the appropriate port (http/https) and keystore/truststore password/file locations (if https is enabled) as part of Metadata Access Service configuration through Admin Console or infacmd.
  7. Support for backup node is also enabled for high availability for Metadata Access Service. Hence, if the primary node where metadata access service runs goes down, the service should come back up on the backup node automatically.
  8. The local Hadoop distribution folders on the developer client boxes are now used during metadata access only if any metadata is accessed from the local file on the same box (where developer client box is installed) eg when a local avro or parquet file is used to import metadata without using a Hadoop File System connection object. Hence, the variable 'INFA_HADOOP_DIST_DIR' needs to be configured (or updated) only if metadata needs to be imported from a local file. In scenarios where a connection is used to import metadata, this variable is no longer required to be configured on the developer client side for metadata access. The size of Informatica Hadoop distribution folder on the developer client is also significantly reduced (by more than 1 GB) as most of the Hadoop distribution related jars/files are required to be deployed as part of only Informatica server-side installation.

Summary

'Metadata Access Service' provides a significant architectural improvement resulting in better security and easier configuration for Informatica Big Data Management client-side developer tool. This reduces the amount of time Informatica developers and administrator need to spend on configuring connectivity to Hadoop adapters like HDFS files, HBase, Hive and MapR-DB for importing metadata into the repository.

Author

Sandeep Kathuria, Senior Staff Engineer

What are we announcing?

Informatica 10.2.1 Service Pack 1

Who would benefit from this release?

This release is for all Big Data Management and Big Data Quality customers and prospects who want to take advantage of the fixes to the Core Platform, Connectivity and installing new Service Pack, or upgrading from previous versions.

What’s in this release?

Big Data Management

  • This update provides the latest Service Pack improving the user experience. All big data customers are recommended to apply this Service Pack

Enterprise Data Catalog

  • This update provides bug fixes for functional and performance improvements. All Enterprise Data Catalog customers on 10.2.1 are recommended to apply this Service Pack.

Enterprise Data Lake

  • This update provides bug fixes for functional and performance improvements.
  • It also includes support for Spark engine execution and Autoscaling in AWS EMR deployments. 

 

Informatica 10.2.1 Service Pack 1 Big Data Release Notes

 

PAM for Informatica 10.2.1