Skip to content
IMPORTANT - Issue tracking has been migrated to JIRA - use your github ID and password reset mechanism to log in http://track.hpccsystems.com
C++ ECL JavaScript XSLT CMake Yacc Other
Find file
Latest commit 6f89305 @richardkchapman richardkchapman Merge pull request #8073 from AttilaVamos/HPCC-14749-improvement
HPCC-14749 Ensure HPCC generates core dump if abort condition sensed.

Reviewed-By: Mark Kelly <mark.kelly@lexisnexis.com>
Reviewed-By: Richard Chapman <rchapman@hpccsystems.com>
Failed to load latest commit information.
build_utils HPCC-13448 Source Code needs Marca Registrada next to HPCC Systems®
charm HPCC-11289 Add README file for HPCC Juju Charm Development
clienttools HPCC-13448 Source Code needs Marca Registrada next to HPCC Systems®
cmake_modules Merge branch 'candidate-5.6.0' into candidate-6.0.0
common Merge branch 'candidate-5.6.0' into candidate-6.0.0
dali Merge branch 'candidate-5.6.0' into candidate-6.0.0
deploy HPCC-13448 Source Code needs Marca Registrada next to HPCC Systems®
deployment HPCC-14684 ConfigMgr - Add alias attribute to Cluster section in Topo…
docs Merge branch 'candidate-5.6.0' into candidate-6.0.0
ecl Merge pull request #8073 from AttilaVamos/HPCC-14749-improvement
ecllibrary HPCC-14559 Add WorkunitServices function to set application values
esp Merge branch 'candidate-5.6.0' into candidate-6.0.0
githooks Merge remote-tracking branch 'origin/candidate-3.10.x'
initfiles Merge branch 'candidate-5.6.0' into candidate-6.0.0
lib2 HPCC-14118 Update third party libraries and settings to support VS2015
misc HPCC-9508 Add eclipse code layout settings file to project
plugins Merge branch 'candidate-5.6.0' into candidate-6.0.0
roxie Merge pull request #8073 from AttilaVamos/HPCC-14749-improvement
rtl Merge pull request #8183 from ghalliday/issue14849b
services Merge branch 'candidate-5.4.0'
system Merge pull request #8073 from AttilaVamos/HPCC-14749-improvement
testing Merge branch 'candidate-5.6.0' into candidate-6.0.0
thorlcr Merge branch 'candidate-5.6.0' into candidate-6.0.0
tools Merge pull request #8092 from rpastrana/HPCC-14758-Publishbindingcrash
.gitattributes Issue #254 Switches template reading to use jlib
.gitignore Minor code cleaup to avoid false positives from Eclipse
.gitmodules HPCC-14393 New Kafka plugin for Thor and Roxie
.travis.yml HPCC-13601 Travis-CI
BUILD_ME.md HPCC-13515 A proper README.md, moving old README.md -> BUILD_ME.md
CMakeLists.txt Merge pull request #8100 from Michael-Gardner/HPCC-8401
CNAME Add CNAME entry for GitHub pages redirection
CONTRIBUTORS HPCC-13448 Source Code needs Marca Registrada next to HPCC Systems®
FUTURE Initial version of FUTURE document
LICENSE.txt HPCC-13448 Source Code needs Marca Registrada next to HPCC Systems®
R-LICENSE.txt HPCC-14457 Split R plugin to its own package
README.md HPCC-13515 A proper README.md, moving old README.md -> BUILD_ME.md
VERSIONS Preparation for 6.0.0-beta1 release
baseaddr.txt HPCC-13448 Source Code needs Marca Registrada next to HPCC Systems®
build-config.h.cmake HPCC-9902 Use the build version as the ecl version reported by eclcc
sourcedoc.xml HPCC-13448 Source Code needs Marca Registrada next to HPCC Systems®
version.cmake Split off 6.0.0 branch

README.md

Description / Rationale

HPCC Systems offers an enterprise ready, open source supercomputing platform to solve big data problems. As compared to Hadoop, the platform offers analysis of big data using less code and less nodes for greater efficiencies and offers a single programming language, a single platform and a single architecture for efficient processing. HPCC Systems is a technology division of LexisNexis Risk Solutions.

Getting Started

Architecture

The HPCC Systems architecture incorporates the Thor and Roxie clusters as well as common middleware components, an external communications layer, client interfaces which provide both end-user services and system management tools, and auxiliary components to support monitoring and to facilitate loading and storing of filesystem data from external sources. An HPCC environment can include only Thor clusters, or both Thor and Roxie clusters. Each of these cluster types is described in more detail in the following sections below the architecture diagram.

Thor

Thor (the Data Refinery Cluster) is responsible for consuming vast amounts of data, transforming, linking and indexing that data. It functions as a distributed file system with parallel processing power spread across the nodes. A cluster can scale from a single node to thousands of nodes.

  • Single-threaded
  • Distributed parallel processing
  • Distributed file system
  • Powerful parallel processing programming language (ECL)
  • Optimized for Extraction, Transformation, Loading, Sorting, Indexing and Linking
  • Scales from 1-1000s of nodes

Roxie

Roxie (the Query Cluster) provides separate high-performance online query processing and data warehouse capabilities. Roxie (Rapid Online XML Inquiry Engine) is the data delivery engine used in HPCC to serve data quickly and can support many thousands of requests per node per second.

  • Multi-threaded
  • Distributed parallel processing
  • Distributed file system
  • Powerful parallel processing programming language (ECL)
  • Optimized for concurrent query processing
  • Scales from 1-1000s of nodes

ECL

ECL (Enterprise Control Language) is the powerful programming language that is ideally suited for the manipulation of Big Data.

  • Transparent and implicitly parallel programming language
  • Non-procedural and dataflow oriented
  • Modular, reusable, extensible syntax
  • Combines data representation and algorithm implementation
  • Easily extend using C++ libraries
  • ECL is compiled into optimized C++

ECL IDE

ECL IDE is a modern IDE used to code, debug and monitor ECL programs.

  • Access to shared source code repositories
  • Complete development, debugging and testing environment for developing ECL dataflow programs
  • Access to the ECLWatch tool is built-in, allowing developers to watch job graphs as they are executing
  • Access to current and historical job workunits

ESP

ESP (Enterprise Services Platform) provides an easy to use interface to access ECL queries using XML, HTTP, SOAP and REST.

  • Standards-based interface to access ECL functions
Something went wrong with that request. Please try again.