活动介绍
file-type

Greenplum6在CentOS7上的安装指南

ZIP文件

下载需积分: 1 | 66.11MB | 更新于2024-10-05 | 114 浏览量 | 0 下载量 举报 收藏
download 立即下载
Greenplum6是该系列的第六个主要版本,其设计目标是为企业级用户提供高性能的数据分析功能。Greenplum6对CentOS7的支持表明,它能够在这个较新的Linux操作系统版本上运行,这对于想要构建高性能数据仓库的用户来说是一个好消息。 CentOS(Community ENTerprise Operating System)是一个基于Red Hat Enterprise Linux(RHEL)构建的免费企业级Linux发行版,它提供了一个稳定且高效的操作系统环境。由于CentOS7是目前广泛使用的稳定版本,Greenplum选择支持CentOS7,意味着它可以在大多数生产环境中稳定运行。 根据压缩包中的文件名称列表,我们可以分析出以下知识点: 1. host.ini文件通常用于存储配置信息,包括Greenplum集群中各个节点的配置信息。在Greenplum安装过程中,这个文件用于指导安装器如何设置主机和端口信息,以及如何分配资源。 2. LICENSE文件包含了Greenplum软件的授权协议信息。在使用Greenplum之前,用户需要了解和遵守相应的软件许可协议,以确保合法使用软件。 3. makefile文件是用于管理程序编译过程的脚本文件。在Greenplum的源代码目录中,makefile文件指导make工具如何编译源代码,生成可执行文件或库文件。Greenplum的makefile还可能包含特定于CentOS7的编译指令,确保软件能够适应这个系统的环境。 4. start.sh文件是一个脚本文件,通常用于启动和初始化Greenplum数据库。在安装完成后,用户可以通过执行start.sh脚本来启动Greenplum集群。该脚本文件中会包含环境设置、配置加载、服务启动等命令。 5. readme.txt文件通常包含了关于软件的基本介绍、安装指南、使用方法以及注意事项等。这个文件对于Greenplum的初学者尤为重要,因为它是学习如何安装和配置Greenplum的第一个文档资源。 6. src目录包含了Greenplum的源代码。对于开发者和高级用户来说,了解源代码结构和编写方式是进行个性化开发、问题诊断和性能调优的重要前提。在CentOS7环境下安装Greenplum,用户可以深入src目录,根据自己的需求修改和扩展功能。 综合以上信息,我们可以看出,Greenplum6与CentOS7的结合提供了一个稳定、高效且具有高度可扩展性的环境,可以用于搭建大规模的数据分析平台。在实际应用中,用户需要遵循相应的授权协议,正确配置host.ini文件,使用start.sh脚本启动集群,并且参考readme.txt文件进行安装和操作。对于需要深入了解或定制Greenplum的用户,源代码目录(src)则是一个宝贵的资源。"

相关推荐

filetype
greenplum-db-6.2.1-rhel7-x86_64.rpm Pivotal Greenplum 6.2 Release Notes This document contains pertinent release information about Pivotal Greenplum Database 6.2 releases. For previous versions of the release notes for Greenplum Database, go to Pivotal Greenplum Database Documentation. For information about Greenplum Database end of life, see Pivotal Greenplum Database end of life policy. Pivotal Greenplum 6 software is available for download from the Pivotal Greenplum page on Pivotal Network. Pivotal Greenplum 6 is based on the open source Greenplum Database project code. Important: Pivotal Support does not provide support for open source versions of Greenplum Database. Only Pivotal Greenplum Database is supported by Pivotal Support. Release 6.2.1 Release Date: 2019-12-12 Pivotal Greenplum 6.2.1 is a minor release that includes new features and resolves several issues. New Features Greenplum Database 6.2.1 includes these new features: Greenplum Database supports materialized views. Materialized views are similar to views. A materialized view enables you to save a frequently used or complex query, then access the query results in a SELECT statement as if they were a table. Materialized views persist the query results in a table-like form. Materialized view data cannot be directly updated. To refresh the materialized view data, use the REFRESH MATERIALIZED VIEW command. See Creating and Managing Materialized Views. Note: Known Issues and Limitations describes a limitation of materialized view support in Greenplum 6.2.1. The gpinitsystem utility supports the --ignore-warnings option. The option controls the value returned by gpinitsystem when warnings or an error occurs. If you specify this option, gpinitsystem returns 0 if warnings occurred during system initialization, and returns a non-zero value if a fatal error occurs. If this option is not specified, gpinitsystem returns 1 if initialization completes with warnings, and returns value of 2 or greater if a fatal error occurs. PXF version 5.10.0 is included, which introduces several new and changed features and bug fixes. See PXF Version 5.10.0 below. PXF Version 5.10.0 PXF 5.10.0 includes the following new and changed features: PXF has improved its performance when reading a large number of files from HDFS or an object store. PXF bundles newer tomcat and jackson libraries. The PXF JDBC Connector now supports pushdown of OR and NOT logical filter operators when specified in a JDBC named query or in an external table query filter condition. PXF supports writing Avro-format data to Hadoop and object stores. Refer to Reading and Writing HDFS Avro Data for more information about this feature. PXF is now certified with Hadoop 2.x and 3.1.x and Hive Server 2.x and 3.1, and bundles new and upgraded Hadoop libraries to support these versions. PXF supports Kerberos authentication to Hive Server 2.x and 3.1.x. PXF supports per-server user impersonation configuration. PXF supports concurrent access to multiple Kerberized Hadoop clusters. In previous releases of Greenplum Database, PXF supported accessing a single Hadoop cluster secured with Kerberos, and this Hadoop cluster must have been configured as the default PXF server. PXF introduces a new template file, pxf-site.xml, to specify the Kerberos and impersonation property settings for a Hadoop or JDBC server configuration. Refer to About Kerberos and User Impersonation Configuration (pxf-site.xml) for more information about this file. PXF now supports connecting to Hadoop with a configurable Hadoop user identity. PXF previously supported only proxy access to Hadoop via the gpadmin Greenplum user. PXF version 5.10.0 deprecates the following configuration properties. Note: These property settings continue to work. The PXF_USER_IMPERSONATION, PXF_PRINCIPAL, and PXF_KEYTAB settings in the pxf-env.sh file. You can use the pxf-site.xml file to configure Kerberos and impersonation settings for your new Hadoop server configurations. The pxf.impersonation.jdbc property setting in the jdbc-site.xml file. You can use the pxf.service.user.impersonation property to configure user impersonation for a new JDBC server configuration. Note: If you have previously configured a PXF JDBC server to access Kerberos-secured Hive, you must upgrade the server definition. See Upgrading PXF in Greenplum 6.x for more information. Changed Features Greenplum Database 6.2.1 includes these changed features: Greenplum Stream Server version 1.3.1 is included in the Greenplum distribution. Resolved Issues Pivotal Greenplum 6.2.1 is a minor release that resolves these issues: 29454 - gpstart During Greenplum Database start up, the gpstart utility did not report when a segment instance failed to start. The utility always displayed 0 skipped segment starts. This issue has been resolved. gpstart output was also enhanced to provide additional warnings and summary information about the number of skipped segments. For example: [WARNING]:-********