Hitachi Vantara Pentaho Community Wiki
Child pages
  • Pentaho Software Architecture

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


This section discusses high level cross cutting software architectures and use cases.

Version Control

At this time, Pentaho utilizes a combination of SVN and GIT for managing the source.  Here are some related articles:|../../../../../../../../../display/PEOpen/Advanced+Git+Topics|\

Metadata Definitions

As we continue to build a community of projects, it's important that they share terminology and common metadata.  Here's the beginnings of capturing shared metadata to be used across all Pentaho projects:|../../../../../../../../../display/COM/Standard+MetaStore+Element+types|\

Detailed Software Listing


  Source Path
  Architectural Owner
  Architectural Area

Third Party Maintained Forks

It is Pentaho's intention to avoid having to fork and maintain third party open source software, but on a few occasions it has been necessary.  The following list is of the current third party maintained forks that Pentaho includes in our product.

 Kettle-VFS (Fork of Apache VFS) (MattC)
 Hive JDBC (Will)
 Pentaho OFC4J (Will)


Kettle VFS is a maintained fork of Apache Commons VFS


 Hive JDBC (Will)

 Pentaho OFC4J (Will)

Common Components