10/5/2017 2:41:54 PM
flows (#1511)
The broken graph attached to the bug #1508 happens because animatePolylineEdge fails: it assumes that each edge has always a number of edge.oldpoints equals to the number of newPoints, which sometimes fails.
newPoints is fed by the moveNodeEdges: it iterates through all the edge.guides (the segments composing the lines connecting the graph nodes) and adds the starting and ending points; this makes sense, because the assumption edge.guides.length == edge.points.length - 2 should always hold.
The bug happens because this assumption is broken: in layoutGraph we sometimes add a new segment to edge.guides but we forget to update the points accordingly.
This patch fixes the problem: when a new segment is added to an edge (see the code after the // Add gap comment) we also add an extra point, therefore assuring the assumption holds, and allowing the animatePolylineEdge to work properly.
|
10/5/2017 2:41:04 PM
were ignored, but now enabled are:
* testFailedRun
* testCancelRun
* testDelayedExecutionJob
|
10/5/2017 12:19:40 PM
(#1524)
This is the platform part of the earlier PR #1332 which was reverted.
Summary:
With this change, support for reporting events of interest from Azkaban has been provided.
Users should provide an implementation of the AzkabanEventReporter interface.
To begin with, the following events are reported. 1. FLOW_STARTED 2. FLOW_FINISHED 3. JOB_STARTED 4. JOB_FINISHED
In future, this can be easily extended to report other events.
Configuration changes:
Note: All changes must be applied to the executor server or the solo-server if in solo mode.
// Property is used to enable/disable event reporting with the default being false.
azkaban.event.reporting.enabled=false
// Implementations of the reporter to be specified using this property.
azkaban.event.reporting.class=com.foo.EventReporterImpl
// Kafka topic name for the default implementation.
azkaban.event.reporting.kafka.topic=TestTopicName
// Kafka broker list for the default implementation.
azkaban.event.reporting.kafka.brokers=hostname.com:port_num
// Schema registry server for the default Kafka implementation.
azkaban.event.reporting.kafka.schema.registry.url=schemaRegistryUrl.com:port/schema
|
10/4/2017 2:37:31 PM
ajax action name 'loadFlow' for backward compatibility.
This resolves issue #1506.
|
10/2/2017 9:01:10 PM
to Metastores in HA mode (#1491)
The logic that Azkaban uses to get the delegation token from ‘other_hcat_locations’ is trying to connect to all hcat servers in that field, and getting the delegation token from each hcat server. This is could cause delegation token confusion problems. Thus, we decide to introduce a new property field called “other_hcat_clusters”, which can also be set in the “properties” field in the workflow file. This field requires users to group the hcat servers to different clusters, in the form as “cluster1hcat01, cluster1cat02;cluster2hcat01,cluster2hcat02”. In our implementation, this string will be split by semicolon, and each group(cluster) will be traversed until we can get the delegation token from one of the machines in that cluster.
|
9/29/2017 6:49:41 PM
3.36.0
not run at all, but it has been marked as killed, the right thing to do is set the status to KILLED. Otherwise the flow would get stuck because this job would send the JOB_FINISHED event with the unfinished status: KILLING.
|
9/29/2017 1:38:21 PM
back "New status: KILLING (#1172)"
This reverts commit 92aff731f4e852674154c2a2d2ebf7bb1d9c03ec.
After `git revert 92aff731f4e852674154c2a2d2ebf7bb1d9c03ec`, resolved conflicts in:
azkaban-common/src/main/java/azkaban/executor/ExecutorManager.java
azkaban-common/src/test/java/azkaban/executor/InteractiveTestJob.java
azkaban-exec-server/src/main/java/azkaban/execapp/FlowRunner.java
azkaban-exec-server/src/main/java/azkaban/execapp/JobRunner.java
azkaban-web-server/src/main/resources/azkaban/webapp/servlet/velocity/historypage.vm
azkaban-web-server/src/web/js/azkaban/view/exflow.js
* Fix test compilation
The method signature of assertFlowStatus had changed in the meanwhile.
|
9/29/2017 1:23:33 PM
(#1510)
* Update dev guide with intellij inserting new line configuration
* Address comments
|
9/29/2017 1:23:09 PM
in #1466 (#1500)
* Create directory flow loader for yaml files.
* Added test case for loading multiple flow yaml files.
* Address comments
* Fix potential inconsistency between project cache and DB during uploading.
|
9/29/2017 2:13:37 AM
reverts commit be6972a146ab769fa535a1788f6cc82c0c7b87ce.
Reason: Unable to release within LinkedIn due to licensing issues emerged from using gobblin-library.
|
