Cisco Cisco Tidal Enterprise Scheduler 6.2 릴리즈 노트
New Features
© 2012 Cisco Systems, Inc. All rights reserved.
3
MapReduce
The MapReduce Adapter serves as the job client to automate the execution of MapReduce
jobs as part of an Enterprise Scheduler managed process.
jobs as part of an Enterprise Scheduler managed process.
HP OMU
The Cisco Tidal Enterprise Scheduler (TES) HP OMU Adapter provides support for HP
OMU integration.
OMU integration.
Hive
The Cisco Tidal Enterprise Scheduler (TES) Hive Adapter provides the automation of
HiveQL commands as part of the cross‐platform process organization between TES and
the TES Hadoop Cluster. The Adapter is designed using the same user interface approach
as other Enterprise Scheduler adapter jobs, seamlessly integrating Hadoop Hive data
management into existing operation processes.
HiveQL commands as part of the cross‐platform process organization between TES and
the TES Hadoop Cluster. The Adapter is designed using the same user interface approach
as other Enterprise Scheduler adapter jobs, seamlessly integrating Hadoop Hive data
management into existing operation processes.
The Hive Adapter allows you to access and manage data stored in the Hadoop
Distributed File System (HDFS™) using Hiveʹs query language, HiveQL. HiveQL syntax
is similar to SQL standard syntax.
Distributed File System (HDFS™) using Hiveʹs query language, HiveQL. HiveQL syntax
is similar to SQL standard syntax.
The Have Adapter, in conjunction with Enterprise Scheduler, can be used to define,
launch, control, and monitor HiveQL commands submitted to Hive via JDBC on a
scheduled basis. The Adapter integrates seamlessly in an enterprise scheduling
environment.
launch, control, and monitor HiveQL commands submitted to Hive via JDBC on a
scheduled basis. The Adapter integrates seamlessly in an enterprise scheduling
environment.
DataMover
Based on the incorporation of Big Data and Cloud applications into Cisco Tidal Enterprise
Scheduler (TES), Data Mover has been developed for data movement operations beyond
the traditional FTP type movement. Additional data movement operation types have been
included in the Agent, thus expanding the current FTP Service in the Agent into a Data
Mover service. The Agent is the logical component for this functionality due to the fact
that it has better ʹlocality of referenceʹ to the data being moved.
Scheduler (TES), Data Mover has been developed for data movement operations beyond
the traditional FTP type movement. Additional data movement operation types have been
included in the Agent, thus expanding the current FTP Service in the Agent into a Data
Mover service. The Agent is the logical component for this functionality due to the fact
that it has better ʹlocality of referenceʹ to the data being moved.
Data Mover allows for data movement operations to be carried out that move data from
customer local storage into and out of the Cloud Application space. Operations that move
or manipulate data or its structure in the Cloud are not intended for the Data Mover as
they do not have ʹlocality of referenceʹ characteristics.
customer local storage into and out of the Cloud Application space. Operations that move
or manipulate data or its structure in the Cloud are not intended for the Data Mover as
they do not have ʹlocality of referenceʹ characteristics.
Note TIDAL Masters that use the Kerberos authentication system must have their internal
clocks synchronized within a specified maximum amount of time (known as clock
skew). This requirement provides another Kerberos security check. If the clock skew
is exceeded between any of the participating hosts, client requests are rejected. The
maximum clock skew is configurable, but typically defaulted to five minutes. Refer
to Kerberos documentation for further details. Because maintaining synchronized
clocks between the KDCs and Kerberos clients (TIDAL Masters) is important, you
should use the Network Time Protocol (NTP) software or other similar time service
tools to synchronize them.
skew). This requirement provides another Kerberos security check. If the clock skew
is exceeded between any of the participating hosts, client requests are rejected. The
maximum clock skew is configurable, but typically defaulted to five minutes. Refer
to Kerberos documentation for further details. Because maintaining synchronized
clocks between the KDCs and Kerberos clients (TIDAL Masters) is important, you
should use the Network Time Protocol (NTP) software or other similar time service
tools to synchronize them.