Richard Chapman
1c717508b2
Merge pull request #15946 from kenrowland/HPCC-27425
|
3 éve | |
|---|---|---|
| .devcontainer | 3 éve | |
| .github | 3 éve | |
| build_utils | 9 éve | |
| charm | 10 éve | |
| clienttools | 6 éve | |
| cmake_modules | 3 éve | |
| common | 3 éve | |
| configuration | 3 éve | |
| dali | 3 éve | |
| deploy | 7 éve | |
| deployment | 3 éve | |
| devdoc | 3 éve | |
| devel | 5 éve | |
| dockerfiles | 3 éve | |
| docs | 3 éve | |
| ecl | 3 éve | |
| ecllibrary | 3 éve | |
| esp | 3 éve | |
| fs | 3 éve | |
| githooks | 12 éve | |
| helm | 3 éve | |
| initfiles | 3 éve | |
| lib2 | 3 éve | |
| misc | 12 éve | |
| package | 8 éve | |
| plugins | 3 éve | |
| roxie | 3 éve | |
| rtl | 3 éve | |
| services | 6 éve | |
| system | 3 éve | |
| testing | 3 éve | |
| thorlcr | 3 éve | |
| tools | 3 éve | |
| vcpkg @ af3a974a09 | 3 éve | |
| .gitattributes | 8 éve | |
| .gitignore | 3 éve | |
| .gitmodules | 3 éve | |
| BUILD_ME.md | 5 éve | |
| CMakeLists.txt | 3 éve | |
| CNAME | 13 éve | |
| CONTRIBUTORS | 8 éve | |
| FUTURE | 13 éve | |
| LICENSE.txt | 9 éve | |
| R-LICENSE.txt | 9 éve | |
| README.md | 6 éve | |
| VERSIONS | 9 éve | |
| baseaddr.txt | 9 éve | |
| build-config.h.cmake | 11 éve | |
| cmake-vs2015.bat | 6 éve | |
| cmake_uninstall.cmake.in | 8 éve | |
| hpcc.png | 5 éve | |
| vcpkg.json | 3 éve | |
| vcpkg.md | 3 éve | |
| version.cmake | 3 éve |
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
Developer documentation
The following links describe the structure of the system and detail some of the key components:
- An overview of workunits and the different stages in executing a query
- An introduction to the code generator - eclcc
- The memory manager used by roxie and thor
- The structure of the initialization scripts
- Outline of ecl-bundle
- The structure and some details of the cmake files
- Building the documentation