Welcome!

Related Topics: @DXWorldExpo, Recurring Revenue, @CloudExpo, Apache, SDN Journal

@DXWorldExpo: Blog Post

MySQL and Oracle into Hadoop By @Continuent | @CloudExpo [#BigData]

Underlying all the decisions of what part of Hadoop will use the data is how the data is stored

Replicating from MySQL and Oracle into Hadoop

The notion of a database silo - that is, a single database that contains everything and operates in isolation - is a rapidly fading concept in most companies. Many use multiple databases to take advantage of the different range of functionality, from their transactional store, to caching and session stores using NoSQL and, more recently, the transfer of information into analytical stores such as Hadoop.

This raises a problem when it comes to moving the data about. There are many different solutions available if all you want to do is move some data between systems through import and export. These are clumsy solutions, they can be scripted, but more usually you want to provide a regular stream of changes into Hadoop so that you can process and analyze the data as quickly as possible. In this article, we'll examine the traditional dump and load solutions and look at a solution that enables real-time replication of data from MySQL and Oracle into Hadoop.

Hadoop Imports
Ignoring just for the moment where the data will come from, before we start doing any kind of import into Hadoop you need to think about how the data will be used and accessed on the Hadoop side. The temptation is to ignore the destination format and information, but this can lead to long-term problems in terms of understanding the data and processing it effectively.

Underlying all the decisions of what part of Hadoop will use the data is how the data is stored. Within Hadoop, data is written into the HDFS file system. HDFS stores data across your Hadoop cluster by first dividing up the file by the configured block size, and second by providing replicas of these blocks across the cluster. These replicas serve two purposes:

  • They enable faster and more easily distributed processing. With multiple copies, there are multiple nodes that can process the local copy of the data without having to copy it around the cluster at the time of processing.
  • They provide high availability, by allowing a single node in the cluster to fail without you losing access to the data it stores.

Ultimately this leads to the first key parameter for data loading into Hadoop - larger files are better. The larger the file, the more blocks it will be divided into, the more it will be distributed. Ergo, the faster it will be to process across the cluster as multiple nodes are able to work on each block individually.

When it comes to the actual file format, in most cases, Hadoop is designed to work with fairly basic textual data. Rather than the complicated binary formats that traditional databases use, Hadoop is just as happy to process CSV or JSON-based information.

One of the many benefits of Hadoop and the HDFS system is that the distributed nature makes it easy to parse and understand a variety of formats. In general, you are better off writing to a simpler format, such as CSV, that can then be parsed and used by multiple higher-level interfaces, like Hive or Impala. This sounds counter-intuitive, but native binary representations when processed in a distributed fashion often complicate the process of ingesting the data.

So with that in mind, we can generate some simple data to be loaded into Hadoop from our traditional database environment by generating a simple CSV file.

Simple Export
There are many different ways in which you can generate CSV files in both Oracle and MySQL. In both solutions you can normally do a dump of the information from a table, or from the output of a query, into a CSV file.

For example, with MySQL you can use the SELECT INTO SQL statement:

mysql> SELECT title, subtitle, servings, description into OUTFILE  'data.csv' FIELDS TERMINATED BY ',' FROM recipes t;

Within Oracle, use the SPOOL method within sqlplus, or manually combine the columns together. Alternatively, there are numerous solutions and tools for reading SQL data and generating CSV.

Once you've generated the file, the easiest way to get the data into HDFS is to copy the information from the generated file into HDFS using the hadoop command-line tool.

For example:

$ hadoop fs -copyFromLocal data.csv /user/

The problem with this approach is what do you do the next time you want to export the data? Do you export the whole batch, or just the changed records? And how do you identify the changed information, and more importantly merge that back once it's in HDFS. More importantly, all you have is the raw data; to use it, for example, within Hive and perform queries on the information, requires manually generating the DDL. Let's try a different tool, Sqoop.

Using Sqoop
Sqoop is a standard part of Hadoop and uses JDBC to access remote databases of a variety of types and then transfers the information across into Hadoop. The way it does this is actually not vastly different from the manual export process provided above; it runs the equivalent of a 'SELECT * FROM TABLE' and then writes the generated information into HDFS for you.

There are some differences. For one, Sqoop will do this in parallel for you. For example, if you have 20 nodes in your Hadoop cluster, Sqoop will fire up 20 processes that first identify and split up the extraction, and then give each node the range of records to be extracted. When moving millions of rows of data, it is obviously more efficient to be doing this in parallel, providing your server is capable of handling the load.

Using Sqoop is simple, you supply the JDBC connectivity information while logged in to your Hadoop cluster, and effectively suck the data across:

$ sqoop import-all-tables --connect jdbc:mysql://192.168.0.240/cheffy
\-username=cheffy

This process will create a file within HDFS with the extracted data:

$ hadoop fs -ls access_log
Found 6 items
-rw-r--r--   3 cloudera cloudera          0 2013-08-15 09:37 access_log/_SUCCESS
drwxr-xr-x   - cloudera cloudera          0 2013-08-15 09:37 access_log/_logs
-rw-r--r--   3 cloudera cloudera   36313694 2013-08-15 09:37 access_log/part-m-00000
-rw-r--r--   3 cloudera cloudera   36442312 2013-08-15 09:37 access_log/part-m-00001
-rw-r--r--   3 cloudera cloudera   36797470 2013-08-15 09:37 access_log/part-m-00002
-rw-r--r--   3 cloudera cloudera   36321038 2013-08-15 09:37 access_log/part-m-00003

Sqoop itself is quite flexible, for example you can read data from a variety of sources, and write that out to files in various formats, including generating DDL for use within Hive.

Sqoop also supports incremental loads; this is achieved by either using a known auto-incrementing ID that can be used as the change identifier, or by changing your DDL to provide a date time or other column to help identify the last export and new data. For example, using an auto-increment:

$ sqoop import --connect jdbc:mysql://192.168.0.240/hadoop --username root \
--table chicago --check-column id --incremental append --last-value=2168224

The problem with Sqoop is that not everybody wants to change their DDL or auto-increment data. Meanwhile, the problem with both manual and Sqoop based exports is that performing a query, even a limiting one, has the effect of removing data from your memory cache, which may ultimately affect the performance of the application running on the source database. This is not a situation you want.

Furthermore, automating the process, either with direct imports or Sqoop is not as straightforward as it seems either.

Real-Time Replication
A better solution is to replicate the information in real-time using a tool such as Tungsten Replicator. There are methods built into both MySQL and Oracle for effectively extracting the data:

  • MySQL provides the binary log, which contains a simple sequential list of all the changes to the database. These can be statement based or row based, or a mixture.
  • Oracle provides multiple tools, but Tungsten Replicator is designed to work the Change Data Capture (CDC) system to extract row-based information from the database changes.

By reading the row-based changes out of the source database, Tungsten Replicator can formulate this information into CSV. A simple diagram explains the basic process.

This effectively replaces both the manual and Sqoop-based processes with an automated, and constant, stream of data from the source database into Hadoop using HDFS. The exact sequence is:

  • Data is read from the source database, using the binary log or CDC information. This data is already in row format and each table should have a primary key.
  • The row-based changes are stored within the THL format, which consists of the raw ROW data and metadata, such as the column names, primary key and indexing information, and any reformatting required, such as changing the ENUM or SET data types into equivalent strings. THL also associates a unique transaction ID with each block of committed data.
  • The THL data is transferred over to the slave replicator, which is running within the Hadoop cluster.
  • The slave replicator generates a CSV file per table containing a configurable number of rows or within a specific time limit, providing a regular stream of data. The CSV data itself consists of an operation type (insert, or delete, with updates represented as a delete of the original data and an insert of the new data), the sequence number, the primary key information, and the raw row data itself. The reason for this format is how it is used on the other side.
  • The CSV is then copied into the HDFS file system.

This actually only gets the raw change information from the source database and out into HDFS.

This is an important distinction from the manual export and Sqoop processes; Tungsten Replicator effectively stores a CSV version of the change log information.

To turn that change data into we need to materialize the change data into a table that looks like the original table from where the data was generated. The materialization process is actually very simple; within Hadoop we can write a map-reduce script that does the following:

  • Orders all the changes by primary key and transaction ID
  • Ignores any row that is a delete
  • Generates a row for each row marked as an insert, picking the 'last' row (by transaction id) from the list of available rows


This is perhaps clearer in the diagram below, where the change log on the left is translated into the two rows of actual data on the right.

The materialization process needs to be run on every table, and because of the way it works with relation to the idempotency of the primary key information for each row, it can be used both to merge with the current dataset, with data that has previously been provisioned by a using the manual process or Sqoop, and previous executions of the tool on the data. Once the changes have been migrated, the actual change data can be removed.

Using the Change Data
Since you've moved the change data over, another option, rather than generating carbon copy tables, is to actually use the change data. You can, for example, process the information and look at the same transaction data over time or provide a sample of what your data looked like at a specific time. For example, in a sales environment, you might use this to examine the cost and relative sales for products over time when their prices changed.

Summary
There are many solutions available for moving data, and indeed getting data into Hadoop is altogether complicated, but there are benefits and pitfalls to the solutions available. Both manual and Sqoop-based solutions tend to be network and resource heavy, and designed to duplicate data from one side to the other.

The right solution needs to provide the ability to analyze the transactional data in a completely different fashion that may provide additional depth and breadth from your existing transactional data store.

 

Manual via CSV

Sqoop

Tungsten Replicator

Process

Manual/Scripted

Manual/Scripted

Fully automated

Incremental Loading

Possible with DDL changes

Requires DDL changes

Fully supported

Latency

Full-load

Intermittent

Real-time

Extraction Requirements

Full table scan

Full and partial table scans

Low-impact binlog scan

More Stories By MC Brown

MC Brown is director of product management at Continuent, a leading provider of database clustering and replication, enabling enterprises to run business-critical applications on cost-effective open source software. To learn more, contact Continuent at [email protected] or visit http://www.continuent.com.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


Latest Stories
Recently, REAN Cloud built a digital concierge for a North Carolina hospital that had observed that most patient call button questions were repetitive. In addition, the paper-based process used to measure patient health metrics was laborious, not in real-time and sometimes error-prone. In their session at 21st Cloud Expo, Sean Finnerty, Executive Director, Practice Lead, Health Care & Life Science at REAN Cloud, and Dr. S.P.T. Krishnan, Principal Architect at REAN Cloud, discussed how they built...
The dynamic nature of the cloud means that change is a constant when it comes to modern cloud-based infrastructure. Delivering modern applications to end users, therefore, is a constantly shifting challenge. Delivery automation helps IT Ops teams ensure that apps are providing an optimal end user experience over hybrid-cloud and multi-cloud environments, no matter what the current state of the infrastructure is. To employ a delivery automation strategy that reflects your business rules, making r...
As many know, the first generation of Cloud Management Platform (CMP) solutions were designed for managing virtual infrastructure (IaaS) and traditional applications. But that's no longer enough to satisfy evolving and complex business requirements. In his session at 21st Cloud Expo, Scott Davis, Embotics CTO, explored how next-generation CMPs ensure organizations can manage cloud-native and microservice-based application architectures, while also facilitating agile DevOps methodology. He expla...
The past few years have brought a sea change in the way applications are architected, developed, and consumed—increasing both the complexity of testing and the business impact of software failures. How can software testing professionals keep pace with modern application delivery, given the trends that impact both architectures (cloud, microservices, and APIs) and processes (DevOps, agile, and continuous delivery)? This is where continuous testing comes in. D
No hype cycles or predictions of a gazillion things here. IoT is here. You get it. You know your business and have great ideas for a business transformation strategy. What comes next? Time to make it happen. In his session at @ThingsExpo, Jay Mason, an Associate Partner of Analytics, IoT & Cybersecurity at M&S Consulting, presented a step-by-step plan to develop your technology implementation strategy. He also discussed the evaluation of communication standards and IoT messaging protocols, data...
Modern software design has fundamentally changed how we manage applications, causing many to turn to containers as the new virtual machine for resource management. As container adoption grows beyond stateless applications to stateful workloads, the need for persistent storage is foundational - something customers routinely cite as a top pain point. In his session at @DevOpsSummit at 21st Cloud Expo, Bill Borsari, Head of Systems Engineering at Datera, explored how organizations can reap the bene...
In a recent survey, Sumo Logic surveyed 1,500 customers who employ cloud services such as Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform (GCP). According to the survey, a quarter of the respondents have already deployed Docker containers and nearly as many (23 percent) are employing the AWS Lambda serverless computing framework. It’s clear: serverless is here to stay. The adoption does come with some needed changes, within both application development and operations. Tha...
"I focus on what we are calling CAST Highlight, which is our SaaS application portfolio analysis tool. It is an extremely lightweight tool that can integrate with pretty much any build process right now," explained Andrew Siegmund, Application Migration Specialist for CAST, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
Digital transformation is about embracing digital technologies into a company's culture to better connect with its customers, automate processes, create better tools, enter new markets, etc. Such a transformation requires continuous orchestration across teams and an environment based on open collaboration and daily experiments. In his session at 21st Cloud Expo, Alex Casalboni, Technical (Cloud) Evangelist at Cloud Academy, explored and discussed the most urgent unsolved challenges to achieve f...
With tough new regulations coming to Europe on data privacy in May 2018, Calligo will explain why in reality the effect is global and transforms how you consider critical data. EU GDPR fundamentally rewrites the rules for cloud, Big Data and IoT. In his session at 21st Cloud Expo, Adam Ryan, Vice President and General Manager EMEA at Calligo, examined the regulations and provided insight on how it affects technology, challenges the established rules and will usher in new levels of diligence arou...
To get the most out of their data, successful companies are not focusing on queries and data lakes, they are actively integrating analytics into their operations with a data-first application development approach. Real-time adjustments to improve revenues, reduce costs, or mitigate risk rely on applications that minimize latency on a variety of data sources. In his session at @BigDataExpo, Jack Norris, Senior Vice President, Data and Applications at MapR Technologies, reviewed best practices t...
In his general session at 21st Cloud Expo, Greg Dumas, Calligo’s Vice President and G.M. of US operations, discussed the new Global Data Protection Regulation and how Calligo can help business stay compliant in digitally globalized world. Greg Dumas is Calligo's Vice President and G.M. of US operations. Calligo is an established service provider that provides an innovative platform for trusted cloud solutions. Calligo’s customers are typically most concerned about GDPR compliance, application p...
Mobile device usage has increased exponentially during the past several years, as consumers rely on handhelds for everything from news and weather to banking and purchases. What can we expect in the next few years? The way in which we interact with our devices will fundamentally change, as businesses leverage Artificial Intelligence. We already see this taking shape as businesses leverage AI for cost savings and customer responsiveness. This trend will continue, as AI is used for more sophistica...
In his Opening Keynote at 21st Cloud Expo, John Considine, General Manager of IBM Cloud Infrastructure, led attendees through the exciting evolution of the cloud. He looked at this major disruption from the perspective of technology, business models, and what this means for enterprises of all sizes. John Considine is General Manager of Cloud Infrastructure Services at IBM. In that role he is responsible for leading IBM’s public cloud infrastructure including strategy, development, and offering m...
Smart cities have the potential to change our lives at so many levels for citizens: less pollution, reduced parking obstacles, better health, education and more energy savings. Real-time data streaming and the Internet of Things (IoT) possess the power to turn this vision into a reality. However, most organizations today are building their data infrastructure to focus solely on addressing immediate business needs vs. a platform capable of quickly adapting emerging technologies to address future ...