This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The following ARE installed at: 'C:\Program Files\dotnet' | |
• .NET SDK 5.0.100-rc.1.20452.10 | |
• .NET Runtime 5.0.0-rc.1.20451.14 | |
• ASP.NET Core Runtime 5.0.0-rc.1.20451.17 | |
• .NET Windows Desktop Runtime 5.0.0-rc.1.20452.2 | |
This product collects usage data | |
• More information and opt-out https://aka.ms/dotnet-cli-telemetry | |
Resources |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Archi Scripts for jArchi: Search "#jarchi extension:ajs" to find them. | |
jArchi – Scripting for Archi | |
Version 0.8.0 | |
This is an extension to Archi that allows scripting using the JavaScript language. The jArchi scripting API has access to the components of an Archi model so that you can construct your own tasks and queries to achieve things that you might not be able to do easily via the user interface. For example you could write a jArchi script to: | |
Generate reports | |
Create heat maps |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
~curated (~wordlist or ~lexicon or ~corpus or knowledgebase? or ~ontology or ~ontologies or ~taxonomies or ~vocabularies or ~wordnets or ~terms) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SCHEDULING AND COORDINATING OOZIE WORKFLOWS IN HADOOP | |
After you’ve created a set of workflows, you can use a series of Oozie coordinator jobs to schedule when they’re executed. You have two scheduling options for execution: a specific time and the availability of data in conjunction with a certain time. Thanks to Dirk deRoos for this. | |
TIME-BASED SCHEDULING FOR OOZIE COORDINATOR JOBS | |
Oozie coordinator jobs can be scheduled to execute at a certain time, but after they’re started, they can then be configured to run at specified intervals. The following example shows a coordinator job that starts running at a specified start time and date: | |
<coordinator-app name="sampleCoordinator" | |
frequency="${coord:days(1)}" | |
start="2014-06-01T00:01Z " |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
RC1 RC3 RC2 | |
1 -0.115809947 -0.2872409815 -0.1115327498 | |
2 0.0328793034 -0.1818357952 -0.0365915223 | |
3 -0.1681882923 0.2334541608 -0.4065658 | |
4 -0.062899395 -0.7111277644 0.5238386002 | |
5 -0.1332390577 -0.3205176188 -0.1681859864 | |
6 0.2592573907 -1.0031687789 0.8770709735 | |
7 0.1154351112 -0.0992644 -0.3934878741 | |
8 -0.0032770758 -0.7939226678 1.6313446307 | |
9 0.083367581 -0.4209482972 -0.4183281259 |