You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@falcon.apache.org by ve...@apache.org on 2013/06/11 18:59:54 UTC
svn commit: r1491876 [1/2] - in /incubator/falcon: site/ site/docs/
site/images/ site/slides/ site/wiki/ trunk/
trunk/src/site/resources/images/ trunk/src/site/resources/slides/
trunk/src/site/twiki/ trunk/src/site/twiki/docs/
Author: venkatesh
Date: Tue Jun 11 16:59:54 2013
New Revision: 1491876
URL: http://svn.apache.org/r1491876
Log:
FALCON-23 Changed to the wiki docs.
FALCON-4 Incorporated the new logo from InMobi.
Contributed by Srikanth Sundarrajan
Added:
incubator/falcon/trunk/CHANGES.txt
incubator/falcon/trunk/src/site/resources/images/falcon-logo.png (with props)
Modified:
incubator/falcon/site/docs/EntitySpecification.html
incubator/falcon/site/docs/FalconArchitecture.html
incubator/falcon/site/docs/FalconCLI.html
incubator/falcon/site/docs/GettingStarted.html
incubator/falcon/site/docs/InstallationSteps.html
incubator/falcon/site/docs/OnBoarding.html
incubator/falcon/site/images/falcon-logo.png
incubator/falcon/site/index-new.html
incubator/falcon/site/index.html
incubator/falcon/site/issue-tracking.html
incubator/falcon/site/license.html
incubator/falcon/site/mail-lists.html
incubator/falcon/site/project-info.html
incubator/falcon/site/slides/falcon-overview.html
incubator/falcon/site/slides/falcon-user-guide.html
incubator/falcon/site/source-repository.html
incubator/falcon/site/team-list.html
incubator/falcon/site/wiki/Acknowledgements.html
incubator/falcon/site/wiki/FALCON.html
incubator/falcon/site/wiki/HowToContribute.html
incubator/falcon/site/wiki/IRCChannel.html
incubator/falcon/site/wiki/News.html
incubator/falcon/site/wiki/PoweredBy.html
incubator/falcon/site/wiki/Roadmap.html
incubator/falcon/trunk/src/site/resources/slides/falcon-overview.html
incubator/falcon/trunk/src/site/resources/slides/falcon-user-guide.html
incubator/falcon/trunk/src/site/twiki/docs/FalconArchitecture.twiki
incubator/falcon/trunk/src/site/twiki/docs/FalconCLI.twiki
incubator/falcon/trunk/src/site/twiki/index.twiki
Modified: incubator/falcon/site/docs/EntitySpecification.html
URL: http://svn.apache.org/viewvc/incubator/falcon/site/docs/EntitySpecification.html?rev=1491876&r1=1491875&r2=1491876&view=diff
==============================================================================
--- incubator/falcon/site/docs/EntitySpecification.html (original)
+++ incubator/falcon/site/docs/EntitySpecification.html Tue Jun 11 16:59:54 2013
@@ -1,13 +1,13 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia at May 20, 2013
+ | Generated by Apache Maven Doxia at Jun 11, 2013
| Rendered using Apache Maven Fluido Skin 1.3.0
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20130520" />
+ <meta name="Date-Revision-yyyymmdd" content="20130611" />
<meta http-equiv="Content-Language" content="en" />
<title>Falcon - Contents</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.3.0.min.css" />
@@ -218,7 +218,7 @@
- <li id="publishDate" class="pull-right">Last Published: 2013-05-20</li>
+ <li id="publishDate" class="pull-right">Last Published: 2013-06-11</li>
</ul>
</div>
Modified: incubator/falcon/site/docs/FalconArchitecture.html
URL: http://svn.apache.org/viewvc/incubator/falcon/site/docs/FalconArchitecture.html?rev=1491876&r1=1491875&r2=1491876&view=diff
==============================================================================
--- incubator/falcon/site/docs/FalconArchitecture.html (original)
+++ incubator/falcon/site/docs/FalconArchitecture.html Tue Jun 11 16:59:54 2013
@@ -1,13 +1,13 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia at May 20, 2013
+ | Generated by Apache Maven Doxia at Jun 11, 2013
| Rendered using Apache Maven Fluido Skin 1.3.0
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20130520" />
+ <meta name="Date-Revision-yyyymmdd" content="20130611" />
<meta http-equiv="Content-Language" content="en" />
<title>Falcon - Contents</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.3.0.min.css" />
@@ -218,7 +218,7 @@
- <li id="publishDate" class="pull-right">Last Published: 2013-05-20</li>
+ <li id="publishDate" class="pull-right">Last Published: 2013-06-11</li>
</ul>
</div>
@@ -227,7 +227,7 @@
<div id="bodyColumn" >
- <div class="section"><h3>Contents<a name="Contents"></a></h3><p></p><ul><li><a href="#Architecture">Architecture</a></li><li><a href="#Control_flow">Control flow</a></li><li><a href="#Modes_Of_Deployment">Modes Of Deployment</a></li><li><a href="#Entity_Management_actions">Entity Management actions</a></li><li><a href="#Instance_Management_actions">Instance Management actions</a></li><li><a href="#Retention">Retention</a></li><li><a href="#Replication">Replication</a></li><li><a href="#Cross_entity_validations">Cross entity validations</a></li><li><a href="#Updating_process_and_feed_definition">Updating process and feed definition</a></li><li><a href="#Handling_late_input_data">Handling late input data</a></li><li><a href="#Idempotency">Idempotency</a></li><li><a href="#Alerting_and_Monitoring">Alerting and Monitoring</a></li><li><a href="#Falcon_EL_Expressions">Falcon EL Expressions</a></li></ul></div><div class="section"><h3>Architecture<a name="Architecture"><
/a></h3></div><div class="section"><h4>Introduction<a name="Introduction"></a></h4><p>Falcon is a feed and process management platform over hadoop. Falcon essentially transforms user's feed and process configurations into repeated actions through a standard workflow engine. Falcon by itself doesn't do any heavy lifting. All the functions and workflow state management requirements are delegated to the workflow scheduler. The only thing that Falcon maintains is the dependencies and relationship between these entities. This is adequate to provide integrated and seamless experience to the developers using the falcon platform.</p></div><div class="section"><h4>Falcon Architecture - Overview<a name="Falcon_Architecture_-_Overview"></a></h4><p><img src="../images/Architecture.png" alt="" /></p></div><div class="section"><h4>Scheduler<a name="Scheduler"></a></h4><p>Falcon system has picked Oozie as the default scheduler. However the system is open for integration with other schedule
rs. Lot of the data processing in hadoop requires scheduling to be based on both data availability as well as time. Oozie currently supports these capabilities off the shelf and hence the choice.</p></div><div class="section"><h4>Control flow<a name="Control_flow"></a></h4><p>Though the actual responsibility of the workflow is with the scheduler (Oozie), Falcon remains in the execution path, by subscribing to messages that each of the workflow may generate. When Falcon generates a workflow in Oozie, it does so, after instrumenting the workflow with additional steps which includes messaging via JMS. Falcon system itself subscribes to these control messages and can perform actions such as retries, handling late input arrival etc.</p></div><div class="section"><h5>Feed Schedule flow<a name="Feed_Schedule_flow"></a></h5><p><img src="../images/FeedSchedule.png" alt="" /></p></div><div class="section"><h5>Process Schedule flow<a name="Process_Schedule_flow"></a></h5><p><img src=".
./images/ProcessSchedule.png" alt="" /></p></div><div class="section"><h3>Modes Of Deployment<a name="Modes_Of_Deployment"></a></h3><p>There are two basic components of Falcon set up. Falcon Prism and Falcon Server. As the name suggests Falcon Prism splits the request it gets to the Falcon Servers.More details below:</p></div><div class="section"><h4>Stand Alone Mode: <a name="Stand_Alone_Mode:"></a></h4><p>Stand alone mode is useful when the hadoop jobs and revelant data processing invoves only one hadoop cluster. In this mode there is single Falcon server that contacts with oozie to schedule jobs on Hadoop. All the process / feed request like submit, schedule, suspend , kill are sent to this server only. For running in this mode oen should use the falcon whihc has been built for standalone mode , or build using standalone option if using source code.</p></div><div class="section"><h4>Distributed Mode: <a name="Distributed_Mode:"></a></h4><p>Distributed mode is the mode whi
ch you might me using most of the time. This is for orgs which have which have multiple instance of hadoop clusters, and multiple workflow schedulers to handle them. Here we have 2 components: Prism and Server. Both Prism and server have there own setup (runtime and startup properties) and there config localtions. In this mode Prism acts as a contact point for Falcon servers.Below is what all request can be sent tp prism and server in this mode:</p><p>Prism: submit, schedule, submitAndSchdeule, Suspend, Resume, Kill , instance management Server: schedule, suspend, resume, instance management</p><p>As observed above submit and kill are kept exclusively as Prism operations to keep all the config stores in sync and to support feture of idempotency. Request may also be sent from prism but directed to only one specific server, to use that once had to use option "-colo" from CLI or append the same in web request if using API.</p><p>When a cluster is submitted it is bu
default sent to all the servers configured in the prism. When is feed is SUBMIT / SCHEDULED request is only sent to he servers specified in the feed / process definitions. Servers are mentioned in the feed / process via CLUSTER tags in xml definition.</p></div><div class="section"><h5>Prism Setup<a name="Prism_Setup"></a></h5><p><img src="../images/PrismSetup.png" alt="" /></p></div><div class="section"><h4>Configuration Store<a name="Configuration_Store"></a></h4><p>Configuration store is file system based store that the Falcon system maintains where the entity definitions are stored. File System used for the configuration store can either be a local file system or a hdfs file system. It is recommended that to maintain this store outside of the system where Falcon is deployed. This is needed for handling issues relating to disk failures or other permanent failures of the system where Falcon is deployed. Configuration store also maintains an archive location where prior vers
ions of the configuration or deleted configurations are maintained. They are never accessed by the Falcon system and they merely serve to track historical changes to the entity definitions.</p></div><div class="section"><h4>Atomic Actions<a name="Atomic_Actions"></a></h4><p>Often times when Falcon performs entity management actions, it may need to do several individual actions. If one of the action were to fail, then the system could be in an inconsistent state. To avoid this, all individual operations performed are recorded into a transaction journal. This journal is then used to undo the overall user action. In some cases, it is not possible to undo the action. In such cases, Falcon attempts to keep the system in an consistent state.</p></div><div class="section"><h3>Entity Management actions<a name="Entity_Management_actions"></a></h3></div><div class="section"><h4>Submit:<a name="Submit:"></a></h4><p>Entity submit action allows a new cluster/feed/process to be setup with
in Falcon. Submitted entity is not scheduled, meaning it would simply be in the configuration store within Falcon. Besides validating against the schema for the corresponding entity being added, the Falcon system would also perform inter-field validations within the configuration file and validations across dependent entities.</p></div><div class="section"><h4>List:<a name="List:"></a></h4><p>List all the entities within the falcon config store for the entity type being requested. This will include both scheduled and submitted entity configurations.</p></div><div class="section"><h4>Dependency:<a name="Dependency:"></a></h4><p>Returns the dependencies of the requested entity. Dependency list include both forward and backward dependencies (depends on & is dependent on). For ex, a feed would show process that are dependent on the feed and the clusters that it depends on.'</p></div><div class="section"><h4>Schedule:<a name="Schedule:"></a></h4><p>Feeds or Processes that are
already submitted and present in the config store can be scheduled. Upon schedule, Falcon system wraps the required repeatable action as a bundle of oozie coordinators and executes them on the Oozie scheduler. (It is possible to extend Falcon to use an alternate workflow engine other than Oozie). Falcon overrides the workflow instance's external id in Oozie to reflect the process/feed and the nominal time. This external Id can then be used for instance management functions.</p></div><div class="section"><h4>Suspend:<a name="Suspend:"></a></h4><p>This action is applicable only on scheduled entity. This triggers suspend on the oozie bundle that was scheduled earlier through the schedule function. No further instances are executed on a suspended process/feed.</p></div><div class="section"><h4>Resume:<a name="Resume:"></a></h4><p>Puts a suspended process/feed back to active, which in turn resumes applicable oozie bundle.</p></div><div class="section"><h4>Status:<a name="Status:
"></a></h4><p>Gets the current status of the entity.</p></div><div class="section"><h4>Definition:<a name="Definition:"></a></h4><p>Gets the current entity definition as stored in the configuration store. Please note that user documentations in the entity will not be retained.</p></div><div class="section"><h4>Delete:<a name="Delete:"></a></h4><p>Delete operation on the entity removes any scheduled activity on the workflow engine, besides removing the entity from the falcon configuration store. Delete operation on an entity would only succeed if there are no dependent entities on the deleted entity.</p></div><div class="section"><h4>Update:<a name="Update:"></a></h4><p>Update operation allows an already submitted/scheduled entity to be updated. Cluster update is currently not allowed. Feed update can cause cascading update to all the processes already scheduled. The following set of actions are performed in Oozie to realize an update.</p><p></p><ul><li>Suspend the previously
scheduled Oozie coordinator. This is prevent any new action from being triggered.</li><li>Update the coordinator to set the end time to "now"</li><li>Resume the suspended coordiantors</li><li>Schedule as per the new process/feed definition with the start time as "now"</li></ul></div><div class="section"><h3>Instance Management actions<a name="Instance_Management_actions"></a></h3><p>Instance Manager gives user the option to control individual instances of the process based on their instance start time (start time of that instance). Start time needs to be given in standard TZ format. Example: 01 Jan 2012 01:00 => 2012-01-01T01:00Z</p><p>All the instance management operations (except running) allow single instance or list of instance within a Date range to be acted on. Make sure the dates are valid. i.e are within the start and end time of process itself.</p><p>For every query in instance management the process name is a compulsory parameter.</p><p>
Parameters -start and -end are used to mention the date range within which you want the instance to be operated upon.</p><p>-start: using only "-start" without "-end" will conduct the desired operation only on single instance given by date along with start.</p><p>-end: "-end" can only be used along with "-start" . It corresponds to the end date till which instance need to operated upon.</p><p></p><ul><li>1. <b>status</b>: -status option via CLI can be used to get the status of a single or multiple instances. If the instance is not yet materialized but is within the process validity range, WAITING is returned as the state.Along with the status of the instance log location is also returned.</li></ul><p></p><ul><li>2. <b>running</b>: -running returns all the running instance of the process. It does not take any start or end dates but simply return all the instances in state RUNNING at that given time.</li></ul><p></p><ul><li>3. <b
>rerun</b>: -rerun is the option that you will use most often from instance management. As the name suggest this option is used to rerun a particular instance or instances of the process. The rerun option reruns all parent workflow for the instance, which in turn rerun all the sub-workflows for it. This option is valid for any instance in terminal state, i.e. KILLED, SUCCEEDED, FAILED. User can also set properties in the request, which will give options what types of actions should be rerun like, only failed, run all etc. These properties are dependent on the workflow engine being used along with falcon.</li></ul><p></p><ul><li>4. <b>suspend</b>: -suspend is used to suspend a instance or instances for the given process. This option pauses the parent workflow at the state, which it was in at the time of execution of this command. This command is similar to SUSPEND process command in functionality only difference being, SUSPEND process suspends all the instance whereas suspen
d instance suspend only that instance or instances in the range.</li></ul><p></p><ul><li>5. <b>resume</b>: -resume option is used to resume any instance that is in suspended state. (Note: due to a bug in oozie �resume option in some cases may not actually resume the suspended instance/ instances)</li><li>6. <b>kill</b>: -kill option can be used to kill an instance or multiple instances</li></ul><p>In all the cases where your request is syntactically correct but logically not, the instance / instances are returned with the same status as earlier. Example: trying to resume a KILLED / SUCCEEDED instance will return the instance with KILLED / SUCCEEDED, without actually performing any operation. This is so because only an instance in SUSPENDED state can be resumed. Same thing is valid for rerun a SUSPENDED or RUNNING options etc.</p></div><div class="section"><h3>Retention<a name="Retention"></a></h3><p>In coherence with it's feed lifecycle management philos
ophy, Falcon allows the user to retain data in the system for a specific period of time for a scheduled feed. The user can specify the retention period in the respective feed/data xml in the following manner for each cluster the feed can belong to :</p><div class="source"><pre class="prettyprint">
+ <div class="section"><h3>Contents<a name="Contents"></a></h3><p></p><ul><li><a href="#Architecture">Architecture</a></li><li><a href="#Control_flow">Control flow</a></li><li><a href="#Modes_Of_Deployment">Modes Of Deployment</a></li><li><a href="#Entity_Management_actions">Entity Management actions</a></li><li><a href="#Instance_Management_actions">Instance Management actions</a></li><li><a href="#Retention">Retention</a></li><li><a href="#Replication">Replication</a></li><li><a href="#Cross_entity_validations">Cross entity validations</a></li><li><a href="#Updating_process_and_feed_definition">Updating process and feed definition</a></li><li><a href="#Handling_late_input_data">Handling late input data</a></li><li><a href="#Idempotency">Idempotency</a></li><li><a href="#Alerting_and_Monitoring">Alerting and Monitoring</a></li><li><a href="#Falcon_EL_Expressions">Falcon EL Expressions</a></li></ul></div><div class="section"><h3>Architecture<a name="Architecture"><
/a></h3></div><div class="section"><h4>Introduction<a name="Introduction"></a></h4><p>Falcon is a feed and process management platform over hadoop. Falcon essentially transforms user's feed and process configurations into repeated actions through a standard workflow engine (Apache Oozie). Falcon by itself doesn't do any heavy lifting. All the functions and workflow state management requirements are delegated to the workflow scheduler. The only thing that Falcon maintains is the dependencies and relationship between these entities. This is adequate to provide integrated and seamless experience to the developers using the falcon platform.</p></div><div class="section"><h4>Falcon Architecture - Overview<a name="Falcon_Architecture_-_Overview"></a></h4><p><img src="../images/Architecture.png" alt="" /></p></div><div class="section"><h4>Scheduler<a name="Scheduler"></a></h4><p>Falcon system has picked Apache Oozie as the default scheduler. However the system is open for integrati
on with other schedulers. Lot of the data processing in hadoop requires scheduling to be based on both data availability as well as time. Apache Oozie currently supports these capabilities off the shelf and hence the choice.</p></div><div class="section"><h4>Control flow<a name="Control_flow"></a></h4><p>Though the actual responsibility of the workflow is with the scheduler (Oozie), Falcon remains in the execution path, by subscribing to messages that each of the workflow may generate. When Falcon generates a workflow in Oozie, it does so, after instrumenting the workflow with additional steps which includes messaging via JMS. Falcon system itself subscribes to these control messages and can perform actions such as retries, handling late input arrival etc.</p></div><div class="section"><h5>Feed Schedule flow<a name="Feed_Schedule_flow"></a></h5><p><img src="../images/FeedSchedule.png" alt="" /></p></div><div class="section"><h5>Process Schedule flow<a name="Process_Schedule_
flow"></a></h5><p><img src="../images/ProcessSchedule.png" alt="" /></p></div><div class="section"><h3>Modes Of Deployment<a name="Modes_Of_Deployment"></a></h3><p>There are two basic components of Falcon set up. Falcon Prism and Falcon Server. As the name suggests Falcon Prism splits the request it gets to the Falcon Servers.More details below:</p></div><div class="section"><h4>Stand Alone Mode: <a name="Stand_Alone_Mode:"></a></h4><p>Stand alone mode is useful when the hadoop jobs and revelant data processing invoves only one hadoop cluster. In this mode there is single Falcon server that contacts with oozie to schedule jobs on Hadoop. All the process / feed request like submit, schedule, suspend , kill are sent to this server only. For running in this mode oen should use the falcon whihc has been built for standalone mode , or build using standalone option if using source code.</p></div><div class="section"><h4>Distributed Mode: <a name="Distributed_Mode:"></a></h4><p>Dis
tributed mode is the mode which you might me using most of the time. This is for orgs which have which have multiple instance of hadoop clusters, and multiple workflow schedulers to handle them. Here we have 2 components: Prism and Server. Both Prism and server have there own setup (runtime and startup properties) and there config localtions. In this mode Prism acts as a contact point for Falcon servers.Below is what all request can be sent tp prism and server in this mode:</p><p>Prism: submit, schedule, submitAndSchdeule, Suspend, Resume, Kill , instance management Server: schedule, suspend, resume, instance management</p><p>As observed above submit and kill are kept exclusively as Prism operations to keep all the config stores in sync and to support feture of idempotency. Request may also be sent from prism but directed to only one specific server, to use that once had to use option "-colo" from CLI or append the same in web request if using API.</p><p>When a c
luster is submitted it is bu default sent to all the servers configured in the prism. When is feed is SUBMIT / SCHEDULED request is only sent to he servers specified in the feed / process definitions. Servers are mentioned in the feed / process via CLUSTER tags in xml definition.</p></div><div class="section"><h5>Prism Setup<a name="Prism_Setup"></a></h5><p><img src="../images/PrismSetup.png" alt="" /></p></div><div class="section"><h4>Configuration Store<a name="Configuration_Store"></a></h4><p>Configuration store is file system based store that the Falcon system maintains where the entity definitions are stored. File System used for the configuration store can either be a local file system or a hdfs file system. It is recommended that to maintain this store outside of the system where Falcon is deployed. This is needed for handling issues relating to disk failures or other permanent failures of the system where Falcon is deployed. Configuration store also maintains an arch
ive location where prior versions of the configuration or deleted configurations are maintained. They are never accessed by the Falcon system and they merely serve to track historical changes to the entity definitions.</p></div><div class="section"><h4>Atomic Actions<a name="Atomic_Actions"></a></h4><p>Often times when Falcon performs entity management actions, it may need to do several individual actions. If one of the action were to fail, then the system could be in an inconsistent state. To avoid this, all individual operations performed are recorded into a transaction journal. This journal is then used to undo the overall user action. In some cases, it is not possible to undo the action. In such cases, Falcon attempts to keep the system in an consistent state.</p></div><div class="section"><h3>Retention<a name="Retention"></a></h3><p>In coherence with it's feed lifecycle management philosophy, Falcon allows the user to retain data in the system for a specific period of
time for a scheduled feed. The user can specify the retention period in the respective feed/data xml in the following manner for each cluster the feed can belong to :</p><div class="source"><pre class="prettyprint">
<clusters>
<cluster name="corp" type="source">
<validity start="2012-01-30T00:00Z" end="2013-03-31T23:59Z"
Modified: incubator/falcon/site/docs/FalconCLI.html
URL: http://svn.apache.org/viewvc/incubator/falcon/site/docs/FalconCLI.html?rev=1491876&r1=1491875&r2=1491876&view=diff
==============================================================================
--- incubator/falcon/site/docs/FalconCLI.html (original)
+++ incubator/falcon/site/docs/FalconCLI.html Tue Jun 11 16:59:54 2013
@@ -1,13 +1,13 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia at May 20, 2013
+ | Generated by Apache Maven Doxia at Jun 11, 2013
| Rendered using Apache Maven Fluido Skin 1.3.0
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20130520" />
+ <meta name="Date-Revision-yyyymmdd" content="20130611" />
<meta http-equiv="Content-Language" content="en" />
<title>Falcon - FalconCLI</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.3.0.min.css" />
@@ -218,7 +218,7 @@
- <li id="publishDate" class="pull-right">Last Published: 2013-05-20</li>
+ <li id="publishDate" class="pull-right">Last Published: 2013-06-11</li>
</ul>
</div>
@@ -227,7 +227,90 @@
<div id="bodyColumn" >
- <div class="section"><h2>FalconCLI<a name="FalconCLI"></a></h2><p>FalconCLI is a interface between user and Falcon. It is a command line utility provided by Falcon. FalconCLI supports Entity Management, Instance Management and Admin operations.There is a set of web services that are used by FalconCLI to interact with Falcon.</p></div><div class="section"><h3>Entity Management Operations<a name="Entity_Management_Operations"></a></h3></div><div class="section"><h4>Submit<a name="Submit"></a></h4><p>Submit option is used to set up entity definition.</p><p>Example: $FALCON_HOME/bin/falcon entity -submit -type cluster -file /cluster/definition.xml</p><p>Note: The url option in the above and all subsequent commands is optional. If not mentioned it will be picked from client.properties file. If the option is not provided and also not set in client.properties, Falcon CLI will fail.</p></div><div class="section"><h4>Schedule<a name="Schedule"></a></h4><p>Once submitted,
an entity can be scheduled using schedule option. Process and feed can only be scheduled.</p><p>Usage: $FALCON_HOME/bin/falcon entity -type [process|feed] -name <<name>> -schedule</p><p>Example: $FALCON_HOME/bin/falcon entity -type process -name sampleProcess -schedule</p></div><div class="section"><h4>Suspend<a name="Suspend"></a></h4><p>Suspend on an entity results in suspension of the oozie bundle that was scheduled earlier through the schedule function. No further instances are executed on a suspended entity. Only schedulable entities(process/feed) can be suspended.</p><p>Usage: $FALCON_HOME/bin/falcon entity -type [feed|process] -name <<name>> -suspend</p></div><div class="section"><h4>Resume<a name="Resume"></a></h4><p>Puts a suspended process/feed back to active, which in turn resumes applicable oozie bundle.</p><p>Usage: $FALCON_HOME/bin/falcon entity -type [feed|process] -name <<name>> -resume</p></div><div class="section"><
h4>Delete<a name="Delete"></a></h4><p>Delete removes the submitted entity definition for the specified entity and put it into the archive.</p><p>Usage: $FALCON_HOME/bin/falcon entity -type [cluster|feed|process] -name <<name>> -delete</p></div><div class="section"><h4>List<a name="List"></a></h4><p>Entities of a particular type can be listed with list sub-command.</p><p>Usage: $FALCON_HOME/bin/falcon entity -type [cluster|feed|process] -list</p></div><div class="section"><h4>Update<a name="Update"></a></h4><p>Update operation allows an already submitted/scheduled entity to be updated. Cluster update is currently not allowed.</p><p>Usage: $FALCON_HOME/bin/falcon entity -type [feed|process] -name <<name>> -update</p></div><div class="section"><h4>Status<a name="Status"></a></h4><p>Status returns the current status of the entity.</p><p>Usage: $FALCON_HOME/bin/falcon entity -type [cluster|feed|process] -name <<name>> -status</p></div><div cl
ass="section"><h4>Dependency<a name="Dependency"></a></h4><p>With the use of dependency option, we can list all the entities on which the specified entity is dependent. For example for a feed, dependency return the cluster name and for process it returns all the input feeds, output feeds and cluster names.</p><p>Usage: $FALCON_HOME/bin/falcon entity -type [cluster|feed|process] -name <<name>> -dependency</p></div><div class="section"><h4>Definition<a name="Definition"></a></h4><p>Definition option returns the entity definition submitted earlier during submit step.</p><p>Usage: $FALCON_HOME/bin/falcon entity -type [cluster|feed|process] -name <<name>> -definition</p></div><div class="section"><h3>Instance Management Options<a name="Instance_Management_Options"></a></h3></div><div class="section"><h4>Kill<a name="Kill"></a></h4><p>Kill sub-command is used to kill all the instances of the specified process whose nominal time is between the given start ti
me and end time.</p><p>Note: 1. For all the instance management sub-commands, if end time is not specified, Falcon will perform the actions on all the instances whose instance time falls after the start time.</p><p>2. The start time and end time needs to be specified in TZ format. Example: 01 Jan 2012 01:00 => 2012-01-01T01:00Z</p><p>3. Process name is compulsory parameter for each instance management command.</p><p>Usage: $FALCON_HOME/bin/falcon instance -type <<feed/process>> -name <<name>> -kill -start "yyyy-MM-dd'T'HH:mm'Z'" -end "yyyy-MM-dd'T'HH:mm'Z'"</p></div><div class="section"><h4>Suspend<a name="Suspend"></a></h4><p>Suspend is used to suspend a instance or instances for the given process. This option pauses the parent workflow at the state, which it was in at the time of execution of this command.</p><p>Usage: $FALCON_HOME/bin/falcon instance -type <<feed/process>> -name <<name>> -suspend
-start "yyyy-MM-dd'T'HH:mm'Z'" -end "yyyy-MM-dd'T'HH:mm'Z'"</p></div><div class="section"><h4>Continue<a name="Continue"></a></h4><p>Continue option is used to continue the failed workflow instance. This option is valid only for process instances in terminal state, i.e. SUCCEDDED, KILLED or FAILED.</p><p>Usage: $FALCON_HOME/bin/falcon instance -type <<feed/process>> -name <<name>> -re-run -start "yyyy-MM-dd'T'HH:mm'Z'" -end "yyyy-MM-dd'T'HH:mm'Z'"</p></div><div class="section"><h4>Rerun<a name="Rerun"></a></h4><p>Rerun option is used to rerun instances of a given process. This option is valid only for process instances in terminal state, i.e. SUCCEDDED, KILLED or FAILED. Optionally, you can specify the properties to override.</p><p>Usage: $FALCON_HOME/bin/falcon instance -type <<feed/process>> -name <<name>> -re-run -start "yyyy-MM-dd'T'HH:mm'Z'" -end "yyyy-MM-dd'T'HH:mm'Z
'" [-file <<properties file>>]</p></div><div class="section"><h4>Resume<a name="Resume"></a></h4><p>Resume option is used to resume any instance that is in suspended state.</p><p>Usage: $FALCON_HOME/bin/falcon instance -type <<feed/process>> -name <<name>> -resume -start "yyyy-MM-dd'T'HH:mm'Z'" -end "yyyy-MM-dd'T'HH:mm'Z'"</p></div><div class="section"><h4>Status<a name="Status"></a></h4><p>Status option via CLI can be used to get the status of a single or multiple instances. If the instance is not yet materialized but is within the process validity range, WAITING is returned as the state. Along with the status of the instance time is also returned. Log location gives the oozie workflow url If the instance is in WAITING state, missing dependencies are listed</p><p>Example : Suppose a process has 3 instance, one has succeeded,one is in running state and other one is waiting, the expected output is:</p><p>{"st
atus":"SUCCEEDED","message":"getStatus is successful","instances":[{"instance":"2012-05-07T05:02Z","status":"SUCCEEDED","logFile":"http://oozie-dashboard-url"},{"instance":"2012-05-07T05:07Z","status":"RUNNING","logFile":"http://oozie-dashboard-url"}, {"instance":"2010-01-02T11:05Z","status":"WAITING"}]</p><p>Usage: $FALCON_HOME/bin/falcon instance -type <<feed/process>> -name <<name>> -status -start "yyyy-MM-dd'T'HH:mm'Z'" -end "yyyy-MM-dd'T'HH:mm'Z'"</p></div><div class="section"><h4>Running<a name="Running"></a></h4><p>Running option provides all the running instances of the mentioned process.</p><p>Usage: $FALCON_HOME/bin/falcon instance -type <<feed/process>> -name <<name>> -running</p></div><div class
="section"><h4>Logs<a name="Logs"></a></h4><p>Get logs for instance actions</p><p>Usage: $FALCON_HOME/bin/falcon instance -type <<feed/process>> -name <<name>> -logs -start "yyyy-MM-dd'T'HH:mm'Z'" [-end "yyyy-MM-dd'T'HH:mm'Z'"] [-runid <<runid>>]</p></div><div class="section"><h3>Admin Options<a name="Admin_Options"></a></h3></div><div class="section"><h4>Help<a name="Help"></a></h4><p>Usage: $FALCON_HOME/bin/falcon admin -version</p></div><div class="section"><h4>Version<a name="Version"></a></h4><p>Version returns the current verion of Falcon installed. Usage: $FALCON_HOME/bin/falcon admin -help</p></div>
+ <div class="section"><h2>FalconCLI<a name="FalconCLI"></a></h2><p>FalconCLI is a interface between user and Falcon. It is a command line utility provided by Falcon. FalconCLI supports Entity Management, Instance Management and Admin operations.There is a set of web services that are used by FalconCLI to interact with Falcon.</p></div><div class="section"><h3>Entity Management Operations<a name="Entity_Management_Operations"></a></h3></div><div class="section"><h4>Submit<a name="Submit"></a></h4><p>Entity submit action allows a new cluster/feed/process to be setup within Falcon. Submitted entity is not scheduled, meaning it would simply be in the configuration store within Falcon. Besides validating against the schema for the corresponding entity being added, the Falcon system would also perform inter-field validations within the configuration file and validations across dependent entities.</p><div class="source"><pre class="prettyprint">
+Example:
+$FALCON_HOME/bin/falcon entity -submit -type cluster -file /cluster/definition.xml
+
+</pre></div><p>Note: The url option in the above and all subsequent commands is optional. If not mentioned it will be picked from client.properties file. If the option is not provided and also not set in client.properties, Falcon CLI will fail.</p></div><div class="section"><h4>Schedule<a name="Schedule"></a></h4><p>Feeds or Processes that are already submitted and present in the config store can be scheduled. Upon schedule, Falcon system wraps the required repeatable action as a bundle of oozie coordinators and executes them on the Oozie scheduler. (It is possible to extend Falcon to use an alternate workflow engine other than Oozie). Falcon overrides the workflow instance's external id in Oozie to reflect the process/feed and the nominal time. This external Id can then be used for instance management functions.</p><div class="source"><pre class="prettyprint">
+Usage:
+$FALCON_HOME/bin/falcon entity -type [process|feed] -name <<name>> -schedule
+
+Example:
+$FALCON_HOME/bin/falcon entity -type process -name sampleProcess -schedule
+
+</pre></div></div><div class="section"><h4>Suspend<a name="Suspend"></a></h4><p>This action is applicable only on scheduled entity. This triggers suspend on the oozie bundle that was scheduled earlier through the schedule function. No further instances are executed on a suspended process/feed.</p><div class="source"><pre class="prettyprint">
+Usage:
+$FALCON_HOME/bin/falcon entity -type [feed|process] -name <<name>> -suspend
+
+</pre></div></div><div class="section"><h4>Resume<a name="Resume"></a></h4><p>Puts a suspended process/feed back to active, which in turn resumes applicable oozie bundle.</p><div class="source"><pre class="prettyprint">
+Usage:
+ $FALCON_HOME/bin/falcon entity -type [feed|process] -name <<name>> -resume
+
+</pre></div></div><div class="section"><h4>Delete<a name="Delete"></a></h4><p>Delete operation on the entity removes any scheduled activity on the workflow engine, besides removing the entity from the falcon configuration store. Delete operation on an entity would only succeed if there are no dependent entities on the deleted entity.</p><div class="source"><pre class="prettyprint">
+Usage:
+$FALCON_HOME/bin/falcon entity -type [cluster|feed|process] -name <<name>> -delete
+
+</pre></div></div><div class="section"><h4>List<a name="List"></a></h4><p>List all the entities within the falcon config store for the entity type being requested. This will include both scheduled and submitted entity configurations.</p><div class="source"><pre class="prettyprint">
+Usage:
+$FALCON_HOME/bin/falcon entity -type [cluster|feed|process] -list
+
+</pre></div></div><div class="section"><h4>Update<a name="Update"></a></h4><p>Update operation allows an already submitted/scheduled entity to be updated. Cluster update is currently not allowed. Feed update can cause cascading update to all the processes already scheduled. The following set of actions are performed in Oozie to realize an update.</p><p></p><ul><li>Suspend the previously scheduled Oozie coordinator. This is prevent any new action from being triggered.</li><li>Update the coordinator to set the end time to "now"</li><li>Resume the suspended coordiantors</li><li>Schedule as per the new process/feed definition with the start time as "now"</li></ul><div class="source"><pre class="prettyprint">
+Usage:
+$FALCON_HOME/bin/falcon entity -type [feed|process] -name <<name>> -update
+
+</pre></div></div><div class="section"><h4>Status<a name="Status"></a></h4><p>Status returns the current status of the entity.</p><div class="source"><pre class="prettyprint">
+Usage:
+$FALCON_HOME/bin/falcon entity -type [cluster|feed|process] -name <<name>> -status
+
+</pre></div></div><div class="section"><h4>Dependency<a name="Dependency"></a></h4><p>Returns the dependencies of the requested entity. Dependency list include both forward and backward dependencies (depends on & is dependent on). For ex, a feed would show process that are dependent on the feed and the clusters that it depends on.'</p><div class="source"><pre class="prettyprint">
+Usage:
+$FALCON_HOME/bin/falcon entity -type [cluster|feed|process] -name <<name>> -dependency
+
+</pre></div></div><div class="section"><h4>Definition<a name="Definition"></a></h4><p>Gets the current entity definition as stored in the configuration store. Please note that user documentations in the entity will not be retained.</p><div class="source"><pre class="prettyprint">
+Usage:
+$FALCON_HOME/bin/falcon entity -type [cluster|feed|process] -name <<name>> -definition
+
+</pre></div></div><div class="section"><h3>Instance Management Options<a name="Instance_Management_Options"></a></h3><p>Instance Manager gives user the option to control individual instances of the process based on their instance start time (start time of that instance). Start time needs to be given in standard TZ format. Example: 01 Jan 2012 01:00 => 2012-01-01T01:00Z</p><p>All the instance management operations (except running) allow single instance or list of instance within a Date range to be acted on. Make sure the dates are valid. i.e are within the start and end time of process itself.</p><p>For every query in instance management the process name is a compulsory parameter.</p><p>Parameters -start and -end are used to mention the date range within which you want the instance to be operated upon.</p><p>-start: using only "-start" without "-end" will conduct the desired operation only on single instance given by date along with start.</p><
p>-end: "-end" can only be used along with "-start" . It corresponds to the end date till which instance need to operated upon.</p><p></p><ul><li>1. <b>status</b>: -status option via CLI can be used to get the status of a single or multiple instances. If the instance is not yet materialized but is within the process validity range, WAITING is returned as the state.Along with the status of the instance log location is also returned.</li></ul><p></p><ul><li>2. <b>running</b>: -running returns all the running instance of the process. It does not take any start or end dates but simply return all the instances in state RUNNING at that given time.</li></ul><p></p><ul><li>3. <b>rerun</b>: -rerun is the option that you will use most often from instance management. As the name suggest this option is used to rerun a particular instance or instances of the process. The rerun option reruns all parent workflow for the instance, which in turn rerun all the sub-workf
lows for it. This option is valid for any instance in terminal state, i.e. KILLED, SUCCEEDED, FAILED. User can also set properties in the request, which will give options what types of actions should be rerun like, only failed, run all etc. These properties are dependent on the workflow engine being used along with falcon.</li></ul><p></p><ul><li>4. <b>suspend</b>: -suspend is used to suspend a instance or instances for the given process. This option pauses the parent workflow at the state, which it was in at the time of execution of this command. This command is similar to SUSPEND process command in functionality only difference being, SUSPEND process suspends all the instance whereas suspend instance suspend only that instance or instances in the range.</li></ul><p></p><ul><li>5. <b>resume</b>: -resume option is used to resume any instance that is in suspended state. (Note: due to a bug in oozie �resume option in some cases may not actually resume the s
uspended instance/ instances)</li><li>6. <b>kill</b>: -kill option can be used to kill an instance or multiple instances</li></ul><p>In all the cases where your request is syntactically correct but logically not, the instance / instances are returned with the same status as earlier. Example: trying to resume a KILLED / SUCCEEDED instance will return the instance with KILLED / SUCCEEDED, without actually performing any operation. This is so because only an instance in SUSPENDED state can be resumed. Same thing is valid for rerun a SUSPENDED or RUNNING options etc.</p></div><div class="section"><h4>Status<a name="Status"></a></h4><p>Status option via CLI can be used to get the status of a single or multiple instances. If the instance is not yet materialized but is within the process validity range, WAITING is returned as the state. Along with the status of the instance time is also returned. Log location gives the oozie workflow url If the instance is in WAITING state, miss
ing dependencies are listed</p><p>Example : Suppose a process has 3 instance, one has succeeded,one is in running state and other one is waiting, the expected output is:</p><p>{"status":"SUCCEEDED","message":"getStatus is successful","instances":[{"instance":"2012-05-07T05:02Z","status":"SUCCEEDED","logFile":"http://oozie-dashboard-url"},{"instance":"2012-05-07T05:07Z","status":"RUNNING","logFile":"http://oozie-dashboard-url"}, {"instance":"2010-01-02T11:05Z","status":"WAITING"}]</p><div class="source"><pre class="prettyprint">
+Usage:
+$FALCON_HOME/bin/falcon instance -type <<feed/process>> -name <<name>> -status -start "yyyy-MM-dd'T'HH:mm'Z'" -end "yyyy-MM-dd'T'HH:mm'Z'"
+
+</pre></div></div><div class="section"><h4>Kill<a name="Kill"></a></h4><p>Kill sub-command is used to kill all the instances of the specified process whose nominal time is between the given start time and end time.</p><p>Note: 1. For all the instance management sub-commands, if end time is not specified, Falcon will perform the actions on all the instances whose instance time falls after the start time.</p><p>2. The start time and end time needs to be specified in TZ format. Example: 01 Jan 2012 01:00 => 2012-01-01T01:00Z</p><p>3. Process name is compulsory parameter for each instance management command.</p><div class="source"><pre class="prettyprint">
+Usage:
+$FALCON_HOME/bin/falcon instance -type <<feed/process>> -name <<name>> -kill -start "yyyy-MM-dd'T'HH:mm'Z'" -end "yyyy-MM-dd'T'HH:mm'Z'"
+
+</pre></div></div><div class="section"><h4>Suspend<a name="Suspend"></a></h4><p>Suspend is used to suspend a instance or instances for the given process. This option pauses the parent workflow at the state, which it was in at the time of execution of this command.</p><div class="source"><pre class="prettyprint">
+Usage:
+$FALCON_HOME/bin/falcon instance -type <<feed/process>> -name <<name>> -suspend -start "yyyy-MM-dd'T'HH:mm'Z'" -end "yyyy-MM-dd'T'HH:mm'Z'"
+
+</pre></div></div><div class="section"><h4>Continue<a name="Continue"></a></h4><p>Continue option is used to continue the failed workflow instance. This option is valid only for process instances in terminal state, i.e. SUCCEDDED, KILLED or FAILED.</p><div class="source"><pre class="prettyprint">
+Usage:
+$FALCON_HOME/bin/falcon instance -type <<feed/process>> -name <<name>> -re-run -start "yyyy-MM-dd'T'HH:mm'Z'" -end "yyyy-MM-dd'T'HH:mm'Z'"
+
+</pre></div></div><div class="section"><h4>Rerun<a name="Rerun"></a></h4><p>Rerun option is used to rerun instances of a given process. This option is valid only for process instances in terminal state, i.e. SUCCEDDED, KILLED or FAILED. Optionally, you can specify the properties to override.</p><div class="source"><pre class="prettyprint">
+Usage:
+$FALCON_HOME/bin/falcon instance -type <<feed/process>> -name <<name>> -re-run -start "yyyy-MM-dd'T'HH:mm'Z'" -end "yyyy-MM-dd'T'HH:mm'Z'" [-file <<properties file>>]
+
+</pre></div></div><div class="section"><h4>Resume<a name="Resume"></a></h4><p>Resume option is used to resume any instance that is in suspended state.</p><div class="source"><pre class="prettyprint">
+Usage:
+$FALCON_HOME/bin/falcon instance -type <<feed/process>> -name <<name>> -resume -start "yyyy-MM-dd'T'HH:mm'Z'" -end "yyyy-MM-dd'T'HH:mm'Z'"
+
+</pre></div></div><div class="section"><h4>Running<a name="Running"></a></h4><p>Running option provides all the running instances of the mentioned process.</p><div class="source"><pre class="prettyprint">
+Usage:
+$FALCON_HOME/bin/falcon instance -type <<feed/process>> -name <<name>> -running
+
+</pre></div></div><div class="section"><h4>Logs<a name="Logs"></a></h4><p>Get logs for instance actions</p><div class="source"><pre class="prettyprint">
+Usage:
+$FALCON_HOME/bin/falcon instance -type <<feed/process>> -name <<name>> -logs -start "yyyy-MM-dd'T'HH:mm'Z'" [-end "yyyy-MM-dd'T'HH:mm'Z'"] [-runid <<runid>>]
+
+</pre></div></div><div class="section"><h3>Admin Options<a name="Admin_Options"></a></h3></div><div class="section"><h4>Help<a name="Help"></a></h4><div class="source"><pre class="prettyprint">
+Usage:
+$FALCON_HOME/bin/falcon admin -version
+
+</pre></div></div><div class="section"><h4>Version<a name="Version"></a></h4><p>Version returns the current verion of Falcon installed.</p><div class="source"><pre class="prettyprint">
+Usage:
+$FALCON_HOME/bin/falcon admin -help
+
+</pre></div></div>
</div>
</div>
Modified: incubator/falcon/site/docs/GettingStarted.html
URL: http://svn.apache.org/viewvc/incubator/falcon/site/docs/GettingStarted.html?rev=1491876&r1=1491875&r2=1491876&view=diff
==============================================================================
--- incubator/falcon/site/docs/GettingStarted.html (original)
+++ incubator/falcon/site/docs/GettingStarted.html Tue Jun 11 16:59:54 2013
@@ -1,13 +1,13 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia at May 20, 2013
+ | Generated by Apache Maven Doxia at Jun 11, 2013
| Rendered using Apache Maven Fluido Skin 1.3.0
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20130520" />
+ <meta name="Date-Revision-yyyymmdd" content="20130611" />
<meta http-equiv="Content-Language" content="en" />
<title>Falcon - Apache Falcon - Data management and processing platform</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.3.0.min.css" />
@@ -218,7 +218,7 @@
- <li id="publishDate" class="pull-right">Last Published: 2013-05-20</li>
+ <li id="publishDate" class="pull-right">Last Published: 2013-06-11</li>
</ul>
</div>
Modified: incubator/falcon/site/docs/InstallationSteps.html
URL: http://svn.apache.org/viewvc/incubator/falcon/site/docs/InstallationSteps.html?rev=1491876&r1=1491875&r2=1491876&view=diff
==============================================================================
--- incubator/falcon/site/docs/InstallationSteps.html (original)
+++ incubator/falcon/site/docs/InstallationSteps.html Tue Jun 11 16:59:54 2013
@@ -1,13 +1,13 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia at May 20, 2013
+ | Generated by Apache Maven Doxia at Jun 11, 2013
| Rendered using Apache Maven Fluido Skin 1.3.0
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20130520" />
+ <meta name="Date-Revision-yyyymmdd" content="20130611" />
<meta http-equiv="Content-Language" content="en" />
<title>Falcon - Building & Packaging Falcon</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.3.0.min.css" />
@@ -218,7 +218,7 @@
- <li id="publishDate" class="pull-right">Last Published: 2013-05-20</li>
+ <li id="publishDate" class="pull-right">Last Published: 2013-06-11</li>
</ul>
</div>
Modified: incubator/falcon/site/docs/OnBoarding.html
URL: http://svn.apache.org/viewvc/incubator/falcon/site/docs/OnBoarding.html?rev=1491876&r1=1491875&r2=1491876&view=diff
==============================================================================
--- incubator/falcon/site/docs/OnBoarding.html (original)
+++ incubator/falcon/site/docs/OnBoarding.html Tue Jun 11 16:59:54 2013
@@ -1,13 +1,13 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia at May 20, 2013
+ | Generated by Apache Maven Doxia at Jun 11, 2013
| Rendered using Apache Maven Fluido Skin 1.3.0
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20130520" />
+ <meta name="Date-Revision-yyyymmdd" content="20130611" />
<meta http-equiv="Content-Language" content="en" />
<title>Falcon - Contents</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.3.0.min.css" />
@@ -218,7 +218,7 @@
- <li id="publishDate" class="pull-right">Last Published: 2013-05-20</li>
+ <li id="publishDate" class="pull-right">Last Published: 2013-06-11</li>
</ul>
</div>
Modified: incubator/falcon/site/images/falcon-logo.png
URL: http://svn.apache.org/viewvc/incubator/falcon/site/images/falcon-logo.png?rev=1491876&r1=1491875&r2=1491876&view=diff
==============================================================================
Binary files - no diff available.
Modified: incubator/falcon/site/index-new.html
URL: http://svn.apache.org/viewvc/incubator/falcon/site/index-new.html?rev=1491876&r1=1491875&r2=1491876&view=diff
==============================================================================
--- incubator/falcon/site/index-new.html (original)
+++ incubator/falcon/site/index-new.html Tue Jun 11 16:59:54 2013
@@ -1,13 +1,13 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia at May 20, 2013
+ | Generated by Apache Maven Doxia at Jun 11, 2013
| Rendered using Apache Maven Fluido Skin 1.3.0
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20130520" />
+ <meta name="Date-Revision-yyyymmdd" content="20130611" />
<meta http-equiv="Content-Language" content="en" />
<title>Falcon - </title>
<link rel="stylesheet" href="./css/apache-maven-fluido-1.3.0.min.css" />
@@ -218,7 +218,7 @@
- <li id="publishDate" class="pull-right">Last Published: 2013-05-20</li>
+ <li id="publishDate" class="pull-right">Last Published: 2013-06-11</li>
</ul>
</div>
Modified: incubator/falcon/site/index.html
URL: http://svn.apache.org/viewvc/incubator/falcon/site/index.html?rev=1491876&r1=1491875&r2=1491876&view=diff
==============================================================================
--- incubator/falcon/site/index.html (original)
+++ incubator/falcon/site/index.html Tue Jun 11 16:59:54 2013
@@ -1,13 +1,13 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia at May 20, 2013
+ | Generated by Apache Maven Doxia at Jun 11, 2013
| Rendered using Apache Maven Fluido Skin 1.3.0
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20130520" />
+ <meta name="Date-Revision-yyyymmdd" content="20130611" />
<meta http-equiv="Content-Language" content="en" />
<title>Falcon - Apache Falcon - Data management and processing platform</title>
<link rel="stylesheet" href="./css/apache-maven-fluido-1.3.0.min.css" />
@@ -218,7 +218,7 @@
- <li id="publishDate" class="pull-right">Last Published: 2013-05-20</li>
+ <li id="publishDate" class="pull-right">Last Published: 2013-06-11</li>
</ul>
</div>
@@ -227,7 +227,7 @@
<div id="bodyColumn" >
- <div class="section"><h2>Apache Falcon - Data management and processing platform<a name="Apache_Falcon_-_Data_management_and_processing_platform"></a></h2><p>Apache Falcon is a data processing and management solution for Hadoop designed for data motion, coordination of data pipelines, lifecycle management, and data discovery. Falcon enables end consumers to quickly onboard their data and its associated processing and management tasks on Hadoop clusters.</p><p>Data Management on Hadoop encompasses data motion, process orchestration, lifecycle management, data discovery, etc. among other concerns. Falcon is a new data processing and management platform for Hadoop that solves this problem and creates additional opportunities by building on existing components within the Hadoop ecosystem without reinventing the wheel.</p><p>Falcon will enable easy data management via declarative mechanism for Hadoop. Users of Falcon platform simply define infrastructure endpoints, da
ta sets and processing rules declaratively. These declarative configurations are expressed in such a way that the dependencies between these configured entities are explicitly described. This information about inter-dependencies between various entities allows Falcon to orchestrate and manage various data management functions.</p><p>Falcon was successfully accepted as an incubation project in April 2013 and is now in apache incubation.</p><p><div id="components" class="carousel slide"> <!-- Carousel items --> <div class="carousel-inner"> <div class="active item"> <div class="hero-unit"> <h3>Provides key services for data processing apps</h3> <p>Complex data processing logic handled by Falcon instead of hard-coded in apps</p> <!-- <p> <a class="btn btn-primary pull-right" href="././docs/GettingStarted.html">Learn more</a> </p> --> </div> </div> <div class="ite
m"> <div class="hero-unit"> <h3>Introduces higher layer of abstractions</h3> <p>Data Set, Infrastructure (Cluster, Database, Filer, etc.), Process</p> </div> </div> <div class="item"> <div class="hero-unit"> <h3>Declarative language for expressing data management functions</h3> <p>Data management expressed as simple directives, instead of verbosely defining it repeatedly</p> </div> </div> <div class="item"> <div class="hero-unit"> <h3>Promotes Separation of Concerns</h3> <p> Allow process owners to keep application/user workflow specific to their application logic than muddy them with the common management functions. </p> </div> </div> <div class="item"> <div class="hero-unit"> <h3>Promotes Polyglot programming</h3> <p> Does not do any heavy
lifting but delegates to tools with in the Hadoop ecosystem, Enhances productivity </p> </div> </div> <div class="item"> <div class="hero-unit"> <h3>Data Motion</h3> <p>Data Import & Export from DBs, Filers into HDFS</p> </div> </div> <div class="item"> <div class="hero-unit"> <h3>Process orchestration</h3> <p> Late Data Handling, Retries, etc. Multi-cluster management to support Local/Global Aggregations, Rollups, etc. <a href="http://oozie.apache.org/">Scheduler</a> integration </p> </div> </div> <div class="item"> <div class="hero-unit"> <h3>Data Lifecycle Management</h3> <p>Retention, Replication/BCP/DR, Anonymization of PII Data, Archival, etc.</p> </div> </div> <div class="item"> <div class="hero-unit">
<h3>Data Discovery</h3> <p>Data Classification, Audit, Lineage.</p> </div> </div> </div> </div></p></div><div class="section"><h3>Getting Involved<a name="Getting_Involved"></a></h3><p>Developers interested in getting involved with Falcon may join the <a href="././mail-lists.html">mailing lists</a>, <a class="externalLink" href="https://issues.apache.org/jira/browse/FALCON">report bugs</a>, retrieve code from the <a href="././source-repository.html">version control system</a>, and make <a href="././wiki/HowToContribute.html">contributions</a>.</p></div>
+ <div class="section"><h2>Apache Falcon - Data management and processing platform<a name="Apache_Falcon_-_Data_management_and_processing_platform"></a></h2><p>Apache Falcon is a data processing and management solution for Hadoop designed for data motion, coordination of data pipelines, lifecycle management, and data discovery. Falcon enables end consumers to quickly onboard their data and its associated processing and management tasks on Hadoop clusters.</p><p>Data Management on Hadoop encompasses data motion, process orchestration, lifecycle management, data discovery, etc. among other concerns. Falcon is a new data processing and management platform for Hadoop that solves this problem and creates additional opportunities by building on existing components within the Hadoop ecosystem without reinventing the wheel.</p><p>Falcon will enable easy data management via declarative mechanism for Hadoop. Users of Falcon platform simply define infrastructure endpoints, da
ta sets and processing rules declaratively. These declarative configurations are expressed in such a way that the dependencies between these configured entities are explicitly described. This information about inter-dependencies between various entities allows Falcon to orchestrate and manage various data management functions.</p><p>Falcon was accepted as an incubation project in April 2013 and is now in apache incubation.</p><p><div id="components" class="carousel slide"> <!-- Carousel items --> <div class="carousel-inner"> <div class="active item"> <div class="hero-unit"> <h3>Provides key services for data processing apps</h3> <p>Complex data processing logic handled by Falcon instead of hard-coded in apps</p> <!-- <p> <a class="btn btn-primary pull-right" href="././docs/GettingStarted.html">Learn more</a> </p> --> </div> </div> <div class="item"> <
div class="hero-unit"> <h3>Introduces higher layer of abstractions</h3> <p>Data Set, Infrastructure (Cluster, Database, Filer, etc.), Process</p> </div> </div> <div class="item"> <div class="hero-unit"> <h3>Declarative language for expressing data management functions</h3> <p>Data management expressed as simple directives, instead of verbosely defining it repeatedly</p> </div> </div> <div class="item"> <div class="hero-unit"> <h3>Promotes Separation of Concerns</h3> <p> Allow process owners to keep application/user workflow specific to their application logic than muddy them with the common management functions. </p> </div> </div> <div class="item"> <div class="hero-unit"> <h3>Promotes Polyglot programming</h3> <p> Does not do any heavy lifting but d
elegates to tools with in the Hadoop ecosystem, Enhances productivity </p> </div> </div> <div class="item"> <div class="hero-unit"> <h3>Data Motion</h3> <p>Data Import & Export from DBs, Filers into HDFS</p> </div> </div> <div class="item"> <div class="hero-unit"> <h3>Process orchestration</h3> <p> Late Data Handling, Retries, etc. Multi-cluster management to support Local/Global Aggregations, Rollups, etc. <a href="http://oozie.apache.org/">Scheduler</a> integration </p> </div> </div> <div class="item"> <div class="hero-unit"> <h3>Data Lifecycle Management</h3> <p>Retention, Replication/BCP/DR, Anonymization of PII Data, Archival, etc.</p> </div> </div> <div class="item"> <div class="hero-unit"> <h3>Data Di
scovery</h3> <p>Data Classification, Audit, Lineage.</p> </div> </div> </div> </div></p></div><div class="section"><h3>Getting Involved<a name="Getting_Involved"></a></h3><p>Developers interested in getting involved with Falcon may join the <a href="././mail-lists.html">mailing lists</a>, <a class="externalLink" href="https://issues.apache.org/jira/browse/FALCON">report bugs</a>, retrieve code from the <a href="././source-repository.html">version control system</a>, and make <a href="././wiki/HowToContribute.html">contributions</a>.</p></div>
</div>
</div>
Modified: incubator/falcon/site/issue-tracking.html
URL: http://svn.apache.org/viewvc/incubator/falcon/site/issue-tracking.html?rev=1491876&r1=1491875&r2=1491876&view=diff
==============================================================================
--- incubator/falcon/site/issue-tracking.html (original)
+++ incubator/falcon/site/issue-tracking.html Tue Jun 11 16:59:54 2013
@@ -1,13 +1,13 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia at May 21, 2013
+ | Generated by Apache Maven Doxia at Jun 11, 2013
| Rendered using Apache Maven Fluido Skin 1.3.0
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20130521" />
+ <meta name="Date-Revision-yyyymmdd" content="20130611" />
<meta http-equiv="Content-Language" content="en" />
<title>Falcon - Issue Tracking</title>
<link rel="stylesheet" href="./css/apache-maven-fluido-1.3.0.min.css" />
@@ -218,7 +218,7 @@
- <li id="publishDate" class="pull-right">Last Published: 2013-05-21</li>
+ <li id="publishDate" class="pull-right">Last Published: 2013-06-11</li>
</ul>
</div>
Modified: incubator/falcon/site/license.html
URL: http://svn.apache.org/viewvc/incubator/falcon/site/license.html?rev=1491876&r1=1491875&r2=1491876&view=diff
==============================================================================
--- incubator/falcon/site/license.html (original)
+++ incubator/falcon/site/license.html Tue Jun 11 16:59:54 2013
@@ -1,13 +1,13 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia at May 21, 2013
+ | Generated by Apache Maven Doxia at Jun 11, 2013
| Rendered using Apache Maven Fluido Skin 1.3.0
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20130521" />
+ <meta name="Date-Revision-yyyymmdd" content="20130611" />
<meta http-equiv="Content-Language" content="en" />
<title>Falcon - Project License</title>
<link rel="stylesheet" href="./css/apache-maven-fluido-1.3.0.min.css" />
@@ -218,7 +218,7 @@
- <li id="publishDate" class="pull-right">Last Published: 2013-05-21</li>
+ <li id="publishDate" class="pull-right">Last Published: 2013-06-11</li>
</ul>
</div>
Modified: incubator/falcon/site/mail-lists.html
URL: http://svn.apache.org/viewvc/incubator/falcon/site/mail-lists.html?rev=1491876&r1=1491875&r2=1491876&view=diff
==============================================================================
--- incubator/falcon/site/mail-lists.html (original)
+++ incubator/falcon/site/mail-lists.html Tue Jun 11 16:59:54 2013
@@ -1,13 +1,13 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia at May 21, 2013
+ | Generated by Apache Maven Doxia at Jun 11, 2013
| Rendered using Apache Maven Fluido Skin 1.3.0
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20130521" />
+ <meta name="Date-Revision-yyyymmdd" content="20130611" />
<meta http-equiv="Content-Language" content="en" />
<title>Falcon - Project Mailing Lists</title>
<link rel="stylesheet" href="./css/apache-maven-fluido-1.3.0.min.css" />
@@ -218,7 +218,7 @@
- <li id="publishDate" class="pull-right">Last Published: 2013-05-21</li>
+ <li id="publishDate" class="pull-right">Last Published: 2013-06-11</li>
</ul>
</div>
Modified: incubator/falcon/site/project-info.html
URL: http://svn.apache.org/viewvc/incubator/falcon/site/project-info.html?rev=1491876&r1=1491875&r2=1491876&view=diff
==============================================================================
--- incubator/falcon/site/project-info.html (original)
+++ incubator/falcon/site/project-info.html Tue Jun 11 16:59:54 2013
@@ -1,13 +1,13 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia at May 21, 2013
+ | Generated by Apache Maven Doxia at Jun 11, 2013
| Rendered using Apache Maven Fluido Skin 1.3.0
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20130521" />
+ <meta name="Date-Revision-yyyymmdd" content="20130611" />
<meta http-equiv="Content-Language" content="en" />
<title>Falcon - Project Information</title>
<link rel="stylesheet" href="./css/apache-maven-fluido-1.3.0.min.css" />
@@ -218,7 +218,7 @@
- <li id="publishDate" class="pull-right">Last Published: 2013-05-21</li>
+ <li id="publishDate" class="pull-right">Last Published: 2013-06-11</li>
</ul>
</div>
Modified: incubator/falcon/site/slides/falcon-overview.html
URL: http://svn.apache.org/viewvc/incubator/falcon/site/slides/falcon-overview.html?rev=1491876&r1=1491875&r2=1491876&view=diff
==============================================================================
--- incubator/falcon/site/slides/falcon-overview.html (original)
+++ incubator/falcon/site/slides/falcon-overview.html Tue Jun 11 16:59:54 2013
@@ -258,16 +258,12 @@
</ul>
</section>
-<!--
<section class="slide" id="case-study-process">
<h2>Case Study: Geographically Distributed Data Processing</h2>
<ul>
- <li>
- TBD
- </li>
+ <li class="slide">Coming Soon....</li>
</ul>
</section>
--->
<section class="slide" id="highlights">
<h2>Falcon Highlights</h2>
Modified: incubator/falcon/site/slides/falcon-user-guide.html
URL: http://svn.apache.org/viewvc/incubator/falcon/site/slides/falcon-user-guide.html?rev=1491876&r1=1491875&r2=1491876&view=diff
==============================================================================
--- incubator/falcon/site/slides/falcon-user-guide.html (original)
+++ incubator/falcon/site/slides/falcon-user-guide.html Tue Jun 11 16:59:54 2013
@@ -32,10 +32,11 @@
<!-- Begin slides. Just make elements with a class of slide. -->
<section class="slide" id="intro">
- <h1>Apache Falcon - User Guide</h1>
+ <h2>Apache Falcon - User Guide</h2>
+ <h3>Coming soon .... </h3>
</section>
-<section class="slide" id="build">
+<!--<section class="slide" id="build">
<h2>Building Apache Falcon</h2>
<ol>
<li>
@@ -44,7 +45,7 @@
</li>
<li>
<p>Compile the project</p>
- <pre><code>mvn -DskipTests clean package</code></pre>
+ <pre><code>mvn -DskipTests clean package verify</code></pre>
</li>
<li>
<p>Optionally run the tests</p>
@@ -93,7 +94,7 @@
<p>TBD: Schedule a sample process</p>
</li>
</ul>
-</section>
+</section>-->
<!-- End slides. -->
Modified: incubator/falcon/site/source-repository.html
URL: http://svn.apache.org/viewvc/incubator/falcon/site/source-repository.html?rev=1491876&r1=1491875&r2=1491876&view=diff
==============================================================================
--- incubator/falcon/site/source-repository.html (original)
+++ incubator/falcon/site/source-repository.html Tue Jun 11 16:59:54 2013
@@ -1,13 +1,13 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia at May 21, 2013
+ | Generated by Apache Maven Doxia at Jun 11, 2013
| Rendered using Apache Maven Fluido Skin 1.3.0
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20130521" />
+ <meta name="Date-Revision-yyyymmdd" content="20130611" />
<meta http-equiv="Content-Language" content="en" />
<title>Falcon - Source Repository</title>
<link rel="stylesheet" href="./css/apache-maven-fluido-1.3.0.min.css" />
@@ -218,7 +218,7 @@
- <li id="publishDate" class="pull-right">Last Published: 2013-05-21</li>
+ <li id="publishDate" class="pull-right">Last Published: 2013-06-11</li>
</ul>
</div>
Modified: incubator/falcon/site/team-list.html
URL: http://svn.apache.org/viewvc/incubator/falcon/site/team-list.html?rev=1491876&r1=1491875&r2=1491876&view=diff
==============================================================================
--- incubator/falcon/site/team-list.html (original)
+++ incubator/falcon/site/team-list.html Tue Jun 11 16:59:54 2013
@@ -1,13 +1,13 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia at May 21, 2013
+ | Generated by Apache Maven Doxia at Jun 11, 2013
| Rendered using Apache Maven Fluido Skin 1.3.0
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20130521" />
+ <meta name="Date-Revision-yyyymmdd" content="20130611" />
<meta http-equiv="Content-Language" content="en" />
<title>Falcon - Team list</title>
<link rel="stylesheet" href="./css/apache-maven-fluido-1.3.0.min.css" />
@@ -218,7 +218,7 @@
- <li id="publishDate" class="pull-right">Last Published: 2013-05-21</li>
+ <li id="publishDate" class="pull-right">Last Published: 2013-06-11</li>
</ul>
</div>
Modified: incubator/falcon/site/wiki/Acknowledgements.html
URL: http://svn.apache.org/viewvc/incubator/falcon/site/wiki/Acknowledgements.html?rev=1491876&r1=1491875&r2=1491876&view=diff
==============================================================================
--- incubator/falcon/site/wiki/Acknowledgements.html (original)
+++ incubator/falcon/site/wiki/Acknowledgements.html Tue Jun 11 16:59:54 2013
@@ -1,13 +1,13 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia at May 20, 2013
+ | Generated by Apache Maven Doxia at Jun 11, 2013
| Rendered using Apache Maven Fluido Skin 1.3.0
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20130520" />
+ <meta name="Date-Revision-yyyymmdd" content="20130611" />
<meta http-equiv="Content-Language" content="en" />
<title>Falcon - Acknowledgements</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.3.0.min.css" />
@@ -218,7 +218,7 @@
- <li id="publishDate" class="pull-right">Last Published: 2013-05-20</li>
+ <li id="publishDate" class="pull-right">Last Published: 2013-06-11</li>
</ul>
</div>
Modified: incubator/falcon/site/wiki/FALCON.html
URL: http://svn.apache.org/viewvc/incubator/falcon/site/wiki/FALCON.html?rev=1491876&r1=1491875&r2=1491876&view=diff
==============================================================================
--- incubator/falcon/site/wiki/FALCON.html (original)
+++ incubator/falcon/site/wiki/FALCON.html Tue Jun 11 16:59:54 2013
@@ -1,13 +1,13 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia at May 20, 2013
+ | Generated by Apache Maven Doxia at Jun 11, 2013
| Rendered using Apache Maven Fluido Skin 1.3.0
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20130520" />
+ <meta name="Date-Revision-yyyymmdd" content="20130611" />
<meta http-equiv="Content-Language" content="en" />
<title>Falcon - Placeholder for Falcon Confluence twiki</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.3.0.min.css" />
@@ -218,7 +218,7 @@
- <li id="publishDate" class="pull-right">Last Published: 2013-05-20</li>
+ <li id="publishDate" class="pull-right">Last Published: 2013-06-11</li>
</ul>
</div>
Modified: incubator/falcon/site/wiki/HowToContribute.html
URL: http://svn.apache.org/viewvc/incubator/falcon/site/wiki/HowToContribute.html?rev=1491876&r1=1491875&r2=1491876&view=diff
==============================================================================
--- incubator/falcon/site/wiki/HowToContribute.html (original)
+++ incubator/falcon/site/wiki/HowToContribute.html Tue Jun 11 16:59:54 2013
@@ -1,13 +1,13 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia at May 20, 2013
+ | Generated by Apache Maven Doxia at Jun 11, 2013
| Rendered using Apache Maven Fluido Skin 1.3.0
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20130520" />
+ <meta name="Date-Revision-yyyymmdd" content="20130611" />
<meta http-equiv="Content-Language" content="en" />
<title>Falcon - How To Contribute</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.3.0.min.css" />
@@ -218,7 +218,7 @@
- <li id="publishDate" class="pull-right">Last Published: 2013-05-20</li>
+ <li id="publishDate" class="pull-right">Last Published: 2013-06-11</li>
</ul>
</div>
Modified: incubator/falcon/site/wiki/IRCChannel.html
URL: http://svn.apache.org/viewvc/incubator/falcon/site/wiki/IRCChannel.html?rev=1491876&r1=1491875&r2=1491876&view=diff
==============================================================================
--- incubator/falcon/site/wiki/IRCChannel.html (original)
+++ incubator/falcon/site/wiki/IRCChannel.html Tue Jun 11 16:59:54 2013
@@ -1,13 +1,13 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia at May 20, 2013
+ | Generated by Apache Maven Doxia at Jun 11, 2013
| Rendered using Apache Maven Fluido Skin 1.3.0
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20130520" />
+ <meta name="Date-Revision-yyyymmdd" content="20130611" />
<meta http-equiv="Content-Language" content="en" />
<title>Falcon - Placeholder for Falcon Confluence twiki</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.3.0.min.css" />
@@ -218,7 +218,7 @@
- <li id="publishDate" class="pull-right">Last Published: 2013-05-20</li>
+ <li id="publishDate" class="pull-right">Last Published: 2013-06-11</li>
</ul>
</div>
Modified: incubator/falcon/site/wiki/News.html
URL: http://svn.apache.org/viewvc/incubator/falcon/site/wiki/News.html?rev=1491876&r1=1491875&r2=1491876&view=diff
==============================================================================
--- incubator/falcon/site/wiki/News.html (original)
+++ incubator/falcon/site/wiki/News.html Tue Jun 11 16:59:54 2013
@@ -1,13 +1,13 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia at May 20, 2013
+ | Generated by Apache Maven Doxia at Jun 11, 2013
| Rendered using Apache Maven Fluido Skin 1.3.0
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20130520" />
+ <meta name="Date-Revision-yyyymmdd" content="20130611" />
<meta http-equiv="Content-Language" content="en" />
<title>Falcon - Apache Falcon - News</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.3.0.min.css" />
@@ -218,7 +218,7 @@
- <li id="publishDate" class="pull-right">Last Published: 2013-05-20</li>
+ <li id="publishDate" class="pull-right">Last Published: 2013-06-11</li>
</ul>
</div>
Modified: incubator/falcon/site/wiki/PoweredBy.html
URL: http://svn.apache.org/viewvc/incubator/falcon/site/wiki/PoweredBy.html?rev=1491876&r1=1491875&r2=1491876&view=diff
==============================================================================
--- incubator/falcon/site/wiki/PoweredBy.html (original)
+++ incubator/falcon/site/wiki/PoweredBy.html Tue Jun 11 16:59:54 2013
@@ -1,13 +1,13 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia at May 20, 2013
+ | Generated by Apache Maven Doxia at Jun 11, 2013
| Rendered using Apache Maven Fluido Skin 1.3.0
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20130520" />
+ <meta name="Date-Revision-yyyymmdd" content="20130611" />
<meta http-equiv="Content-Language" content="en" />
<title>Falcon - Powered By</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.3.0.min.css" />
@@ -218,7 +218,7 @@
- <li id="publishDate" class="pull-right">Last Published: 2013-05-20</li>
+ <li id="publishDate" class="pull-right">Last Published: 2013-06-11</li>
</ul>
</div>
Modified: incubator/falcon/site/wiki/Roadmap.html
URL: http://svn.apache.org/viewvc/incubator/falcon/site/wiki/Roadmap.html?rev=1491876&r1=1491875&r2=1491876&view=diff
==============================================================================
--- incubator/falcon/site/wiki/Roadmap.html (original)
+++ incubator/falcon/site/wiki/Roadmap.html Tue Jun 11 16:59:54 2013
@@ -1,13 +1,13 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia at May 20, 2013
+ | Generated by Apache Maven Doxia at Jun 11, 2013
| Rendered using Apache Maven Fluido Skin 1.3.0
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20130520" />
+ <meta name="Date-Revision-yyyymmdd" content="20130611" />
<meta http-equiv="Content-Language" content="en" />
<title>Falcon - Apache Falcon Roadmap</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.3.0.min.css" />
@@ -218,7 +218,7 @@
- <li id="publishDate" class="pull-right">Last Published: 2013-05-20</li>
+ <li id="publishDate" class="pull-right">Last Published: 2013-06-11</li>
</ul>
</div>
Added: incubator/falcon/trunk/CHANGES.txt
URL: http://svn.apache.org/viewvc/incubator/falcon/trunk/CHANGES.txt?rev=1491876&view=auto
==============================================================================
--- incubator/falcon/trunk/CHANGES.txt (added)
+++ incubator/falcon/trunk/CHANGES.txt Tue Jun 11 16:59:54 2013
@@ -0,0 +1,19 @@
+Apache Falcon Website (incubating) Change log
+
+Trunk (Unreleased)
+
+ INCOMPATIBLE CHANGES
+
+ NEW FEATURES
+
+ IMPROVEMENTS
+
+ FALCON-4 Incorporated the new logo (Srikanth Sundarrajan via Venkatesh Seetharam)
+
+ FALCON-23 Wiki Documentation changes (Srikanth Sundarrajan via Venkatesh Seetharam)
+
+ FALCON-8 First-cut
+
+ OPTIMIZATIONS
+
+ BUG FIXES
Added: incubator/falcon/trunk/src/site/resources/images/falcon-logo.png
URL: http://svn.apache.org/viewvc/incubator/falcon/trunk/src/site/resources/images/falcon-logo.png?rev=1491876&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/falcon/trunk/src/site/resources/images/falcon-logo.png
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Modified: incubator/falcon/trunk/src/site/resources/slides/falcon-overview.html
URL: http://svn.apache.org/viewvc/incubator/falcon/trunk/src/site/resources/slides/falcon-overview.html?rev=1491876&r1=1491875&r2=1491876&view=diff
==============================================================================
--- incubator/falcon/trunk/src/site/resources/slides/falcon-overview.html (original)
+++ incubator/falcon/trunk/src/site/resources/slides/falcon-overview.html Tue Jun 11 16:59:54 2013
@@ -258,16 +258,12 @@
</ul>
</section>
-<!--
<section class="slide" id="case-study-process">
<h2>Case Study: Geographically Distributed Data Processing</h2>
<ul>
- <li>
- TBD
- </li>
+ <li class="slide">Coming Soon....</li>
</ul>
</section>
--->
<section class="slide" id="highlights">
<h2>Falcon Highlights</h2>