Doc: update the project name to Apache Cloudberry

Rename the Cloudberry Database to Apache Cloudberry to address the lastest project name change.
apache · Feb 14, 2025 · 189bd60 · 189bd60
1 parent 3d4b736
commit 189bd60
Show file tree

Hide file tree

Showing 6 changed files with 75 additions and 75 deletions.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -47,7 +47,7 @@ You can participate by:
 * [Reporting security issues](./SECURITY.md).
 * Testing code, testing releases.
 * Creating educational content (Blog posts, tutorials, videos, etc.)
-* Spreading the word about Cloudberry Database on social media(eg,
+* Spreading the word about Apache Cloudberry on social media(eg,
   Twitter, LinkedIn).
 * ...
 * More things to make Cloudberry better.

diff --git a/README.md b/README.md
@@ -4,7 +4,7 @@
   <picture>
     <source media="(prefers-color-scheme: light)" srcset="./.github/full_color_black.svg">
     <source media="(prefers-color-scheme: dark)" srcset="./.github/full_color_white.svg">
-    <img alt="Cloudberry Database Logo" src="./.github/full_color_black.svg" width="400px">
+    <img alt="Apache Cloudberry Logo" src="./.github/full_color_black.svg" width="400px">
   </picture>
 </p>
 
@@ -68,7 +68,7 @@ feedback, and chat:
 | Slack | [Click to Join](https://inviter.co/apache-cloudberry) the real-time chat on Slack for QA, Dev, Events, and more. Don't miss out! Check out the [Slack guide](https://cloudberry.apache.org/community/slack) to learn more. |
 | Q&A | Ask for help when running/developing Cloudberry, visit [GitHub Discussions - QA](https://github.com/apache/cloudberry/discussions/categories/q-a). |
 | New ideas / Feature Requests | Share ideas for new features, visit [GitHub Discussions - Ideas](https://github.com/apache/cloudberry/discussions/categories/ideas-feature-requests).  |
-| Report bugs | Problems and issues in Apache Cloudberry core. If you find bugs, welcome to submit them [here](https://github.com/apache/cloudberrydb/issues).  |
+| Report bugs | Problems and issues in Apache Cloudberry core. If you find bugs, welcome to submit them [here](https://github.com/apache/cloudberry/issues).  |
 | Report a security vulnerability | View our [security policy](https://github.com/apache/cloudberry/security/policy) to learn how to report and contact us.  |
 | Community events | Including meetups, webinars, conferences, and more events, visit the [Events page](https://cloudberry.apache.org/community/events) and subscribe events calendar.  |
 | Documentation | [Official documentation](https://cloudberry.apache.org/docs/) for Cloudberry. You can explore it to discover more details about us. |
@@ -91,10 +91,10 @@ with the contribution.
 ## Roadmap
 
 You can check our [Cloudberry Roadmap
-2024](https://github.com/orgs/cloudberrydb/discussions/369) out to see the
-product plans and goals we want to achieve in 2024. Welcome to share your
-thoughts and ideas to join us in shaping the future of Apache Cloudberry
-(Incubating). (We will update the Roadmap after entering the Incubator.)
+](https://github.com/apache/cloudberry/discussions/868) out to see the product
+plans and goals we want to achieve. Welcome to share your thoughts and ideas
+to join us in shaping the future of Apache Cloudberry (Incubating). (We will
+update the Roadmap after entering the Incubator.)
 
 ## Acknowledgment
 

diff --git a/deploy/README.md b/deploy/README.md
@@ -20,7 +20,7 @@ Before you begin your automation build, make sure the following preparation work
 1. Download the Cloudberry Database source code into your local machine:
 
     ```bash
-    git clone git@github.com:cloudberrydb/cloudberrydb.git
+    git clone https://github.com/apache/cloudberry.git
     ```
 
 2. Install the required [Vagrant](https://developer.hashicorp.com/vagrant/docs/installation) or [Docker](https://docs.docker.com/desktop/install/mac-install/) in your local environment, depending on your deployment preference.
@@ -32,7 +32,7 @@ Before you begin your automation build, make sure the following preparation work
 2. Start the automatic compilation and deployment process.
 
     ```
-    $ cd /cloudberrydb/deploy/vagrant
+    $ cd /cloudberry/deploy/vagrant
     $ vagrant up
     ```
 

diff --git a/deploy/build/README.Linux.md b/deploy/build/README.Linux.md
@@ -1,21 +1,21 @@
-# Compile and Install Cloudberry Database on Linux
+# Compile and Install Apache Cloudberry on Linux
 
-This document shares how to compile and install Cloudberry Database on Linux systems (CentOS 7, RHEL, and Ubuntu). Note that this document is for developers to try out Cloudberry Database in a single-node environments. DO NOT use this document for production environments.
+This document shares how to compile and install Apache Cloudberry on Linux systems (CentOS 7, RHEL, and Ubuntu). Note that this document is for developers to try out Apache Cloudberry in a single-node environments. DO NOT use this document for production environments.
 
 Take the following steps to set up the development environments:
 
 1. [Clone the GitHub repo](#step-1-clone-the-github-repo).
 2. [Install dependencies](#step-2-install-dependencies).
 3. [Perform prerequisite platform tasks](#step-3-perform-prerequisite-platform-tasks).
-4. [Build Cloudberry Database](#step-4-build-cloudberry-database).
+4. [Build Apache Cloudberry](#step-4-build-apache-cloudberry).
 5. [Verify the cluster](#step-5-verify-the-cluster).
 
 ## Step 1. Clone the GitHub repo
 
-Clone the GitHub repository `cloudberrydb/cloudberrydb` to the target machine:
+Clone the GitHub repository `apache/cloudberry` to the target machine:
 
 ```shell
-git clone https://github.com/cloudberrydb/cloudberrydb.git
+git clone https://github.com/apache/cloudberry.git
 ```
 
 ## Step 2. Install dependencies
@@ -33,10 +33,10 @@ Enter the repository and install dependencies according to your operating system
 
 The following steps work on CentOS 7. For other CentOS versions, these steps might work but are not guaranteed to work.
 
-1. Run the bash script `README.CentOS.bash` in the `deploy/build` directory of the `cloudberrydb/cloudberrydb` repository. To run this script, password is required. Then, some required dependencies will be automatically downloaded.
+1. Run the bash script `README.CentOS.bash` in the `deploy/build` directory of the `apache/cloudberry` repository. To run this script, password is required. Then, some required dependencies will be automatically downloaded.
 
     ```bash
-    cd cloudberrydb/deploy/build
+    cd cloudberry/deploy/build
     ./README.CentOS.bash
     ```
 
@@ -84,7 +84,7 @@ The following steps work on CentOS 7. For other CentOS versions, these steps mig
 3. Install more dependencies by running the `README.Rhel-Rocky.bash` script.
 
     ```bash
-    ~/cloudberrydb/deploy/build/README.Rhel-Rocky.bash
+    ~/cloudberry/deploy/build/README.Rhel-Rocky.bash
     ```
 
 ### For Ubuntu 18.04 or later
@@ -93,7 +93,7 @@ The following steps work on CentOS 7. For other CentOS versions, these steps mig
 
     ```shell
     # You need to enter your password to run.
-    sudo ~/cloudberrydb/deploy/build/README.Ubuntu.bash
+    sudo ~/cloudberry/deploy/build/README.Ubuntu.bash
     ```
 
     > [!Note]
@@ -112,7 +112,7 @@ The following steps work on CentOS 7. For other CentOS versions, these steps mig
 
 ## Step 3. Perform prerequisite platform tasks
 
-After you have installed all the dependencies for your operating system, it is time to do some prerequisite platform tasks before you go on building Cloudberry Database. These operations include manually running `ldconfig`, creating the `gpadmin` user, and setting up a password to start the Cloudberry Database and test.
+After you have installed all the dependencies for your operating system, it is time to do some prerequisite platform tasks before you go on building Apache Cloudberry. These operations include manually running `ldconfig`, creating the `gpadmin` user, and setting up a password to start the Apache Cloudberry and test.
 
 1. Make sure that you add `/usr/local/lib` and `/usr/local/lib64` to the `/etc/ld.so.conf` file.
 
@@ -145,22 +145,22 @@ After you have installed all the dependencies for your operating system, it is t
         exit
         ```
 
-## Step 4. Build Cloudberry Database
+## Step 4. Build Apache Cloudberry
 
-After you have installed all the dependencies and performed the prerequisite platform tasks, you can start to build Cloudberry Database. Run the following commands in sequence.
+After you have installed all the dependencies and performed the prerequisite platform tasks, you can start to build Apache Cloudberry. Run the following commands in sequence.
 
-1. Configure the build environment. Enter the `cloudberrydb` directory and run the `configure` script.
+1. Configure the build environment. Enter the `cloudberry` directory and run the `configure` script.
 
     ```bash
-    cd cloudberrydb
-    ./configure --with-perl --with-python --with-libxml --with-gssapi --prefix=/usr/local/cloudberrydb
+    cd cloudberry
+    ./configure --with-perl --with-python --with-libxml --with-gssapi --prefix=/usr/local/cloudberry
     ```
 
     > [!Note]
-    > CloudberryDB is built with GPORCA by default. If you want to build CBDB without GPORCA, add the `--disable-orca` flag in the `./configure` command.
+    > Cloudberry is built with GPORCA by default. If you want to build Cloudberry without GPORCA, add the `--disable-orca` flag in the `./configure` command.
     >
     > ```bash
-    > ./configure --disable-orca --with-perl --with-python --with-libxml --prefix=/usr/local/cloudberrydb
+    > ./configure --disable-orca --with-perl --with-python --with-libxml --prefix=/usr/local/cloudberry
     > ```
 
 2. Compile the code and install the database.
@@ -174,12 +174,12 @@ After you have installed all the dependencies and performed the prerequisite pla
 
     ```bash
     cd ..
-    cp -r cloudberrydb/ /home/gpadmin/
+    cp -r cloudberry/ /home/gpadmin/
     cd /home/gpadmin/
-    chown -R gpadmin:gpadmin cloudberrydb/
+    chown -R gpadmin:gpadmin cloudberry/
     su - gpadmin
-    cd cloudberrydb/
-    source /usr/local/cloudberrydb/greenplum_path.sh
+    cd cloudberry/
+    source /usr/local/cloudberry/greenplum_path.sh
     ```
 
 4. Start the demo cluster.
@@ -214,7 +214,7 @@ After you have installed all the dependencies and performed the prerequisite pla
     ps -ef | grep postgres
     ```
 
-2. Connect to the Cloudberry Database and see the active segment information by querying the system table `gp_segement_configuration`. For detailed description of this table, see the Greenplum document [here](https://docs.vmware.com/en/VMware-Greenplum/6/greenplum-database/ref_guide-system_catalogs-gp_segment_configuration.html).
+2. Connect to the Apache Cloudberry and see the active segment information by querying the system table `gp_segement_configuration`. For detailed description of this table, see the Greenplum document [here](https://docs.vmware.com/en/VMware-Greenplum/6/greenplum-database/ref_guide-system_catalogs-gp_segment_configuration.html).
 
     ```sql
     $ psql -p 7000 postgres
@@ -224,19 +224,19 @@ After you have installed all the dependencies and performed the prerequisite pla
     postgres=# select version();
                                                                                             version                                                                                         
     -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-    PostgreSQL 14.4 (Cloudberry Database 1.0.0+1c0d6e2224 build dev) on x86_64( GCC 13.2.0) 13.2.0, 64-bit compiled on Sep 22 2023 10:56:01
+    PostgreSQL 14.4 (Apache Cloudberry 1.0.0+1c0d6e2224 build dev) on x86_64( GCC 13.2.0) 13.2.0, 64-bit compiled on Sep 22 2023 10:56:01
     (1 row)
     
     postgres=# select * from gp_segment_configuration;
      dbid | content | role | preferred_role | mode | status | port |  hostname  |  address   |                                   datadir                                    | warehouseid 
     ------+---------+------+----------------+------+--------+------+------------+------------+------------------------------------------------------------------------------+-------------
-        1 |      -1 | p    | p              | n    | u      | 7000 | i-6wvpa9wt | i-6wvpa9wt | /home/gpadmin/cloudberrydb/gpAux/gpdemo/datadirs/qddir/demoDataDir-1         |           0
-        8 |      -1 | m    | m              | s    | u      | 7001 | i-6wvpa9wt | i-6wvpa9wt | /home/gpadmin/cloudberrydb/gpAux/gpdemo/datadirs/standby                     |           0
-        3 |       1 | p    | p              | s    | u      | 7003 | i-6wvpa9wt | i-6wvpa9wt | /home/gpadmin/cloudberrydb/gpAux/gpdemo/datadirs/dbfast2/demoDataDir1        |           0
-        6 |       1 | m    | m              | s    | u      | 7006 | i-6wvpa9wt | i-6wvpa9wt | /home/gpadmin/cloudberrydb/gpAux/gpdemo/datadirs/dbfast_mirror2/demoDataDir1 |           0
-        2 |       0 | p    | p              | s    | u      | 7002 | i-6wvpa9wt | i-6wvpa9wt | /home/gpadmin/cloudberrydb/gpAux/gpdemo/datadirs/dbfast1/demoDataDir0        |           0
-        5 |       0 | m    | m              | s    | u      | 7005 | i-6wvpa9wt | i-6wvpa9wt | /home/gpadmin/cloudberrydb/gpAux/gpdemo/datadirs/dbfast_mirror1/demoDataDir0 |           0
-        4 |       2 | p    | p              | s    | u      | 7004 | i-6wvpa9wt | i-6wvpa9wt | /home/gpadmin/cloudberrydb/gpAux/gpdemo/datadirs/dbfast3/demoDataDir2        |           0
-        7 |       2 | m    | m              | s    | u      | 7007 | i-6wvpa9wt | i-6wvpa9wt | /home/gpadmin/cloudberrydb/gpAux/gpdemo/datadirs/dbfast_mirror3/demoDataDir2 |           0
+        1 |      -1 | p    | p              | n    | u      | 7000 | i-6wvpa9wt | i-6wvpa9wt | /home/gpadmin/cloudberry/gpAux/gpdemo/datadirs/qddir/demoDataDir-1         |           0
+        8 |      -1 | m    | m              | s    | u      | 7001 | i-6wvpa9wt | i-6wvpa9wt | /home/gpadmin/cloudberry/gpAux/gpdemo/datadirs/standby                     |           0
+        3 |       1 | p    | p              | s    | u      | 7003 | i-6wvpa9wt | i-6wvpa9wt | /home/gpadmin/cloudberry/gpAux/gpdemo/datadirs/dbfast2/demoDataDir1        |           0
+        6 |       1 | m    | m              | s    | u      | 7006 | i-6wvpa9wt | i-6wvpa9wt | /home/gpadmin/cloudberry/gpAux/gpdemo/datadirs/dbfast_mirror2/demoDataDir1 |           0
+        2 |       0 | p    | p              | s    | u      | 7002 | i-6wvpa9wt | i-6wvpa9wt | /home/gpadmin/cloudberry/gpAux/gpdemo/datadirs/dbfast1/demoDataDir0        |           0
+        5 |       0 | m    | m              | s    | u      | 7005 | i-6wvpa9wt | i-6wvpa9wt | /home/gpadmin/cloudberry/gpAux/gpdemo/datadirs/dbfast_mirror1/demoDataDir0 |           0
+        4 |       2 | p    | p              | s    | u      | 7004 | i-6wvpa9wt | i-6wvpa9wt | /home/gpadmin/cloudberry/gpAux/gpdemo/datadirs/dbfast3/demoDataDir2        |           0
+        7 |       2 | m    | m              | s    | u      | 7007 | i-6wvpa9wt | i-6wvpa9wt | /home/gpadmin/cloudberry/gpAux/gpdemo/datadirs/dbfast_mirror3/demoDataDir2 |           0
     (8 rows)
     ```