Request for Reviews: Cloudberry Logo Variations

Hi everyone, Following the discussion in [this thread][1], we have created several derivative versions of the Cloudberry logo. You can view them on Figma at https://www.figma.com/design/ZZWHO4jxaXH8UFSaGK1qzl/Apache-Cloudberry-Logo-Files. These logo versions can be used for different use cases. W

Review needed to unblock Cloudberry GitHub workflow builds.

Can someone assist with PR #719 approvals to help unblock the workflow builds. https://github.com/apache/cloudberry/pull/719 Thank you, -=e -- Ed Espino Apache Cloudberry (incubating) & MADlib

HEADS UP: Apache Cloudberry Workflow build issue

There is a build issue with the newly added Github Workflow. I have quite easily reproduced it. I am trying to track it down now. Sorry for the inconvenience, -=e -- Ed Espino Apache Cloudberry (incubating) & MADlib

Re: HEADS UP: Apache Cloudberry Workflow build issue

Please rebase your branches to get the latest workflow build fix from main. PR #719 has been merged: https://github.com/apache/cloudberry/pull/719 -=e On Wed, Nov 20, 2024 at 12:59 AM Ed Espino wrote: > There is a build issue with the newly added Github Workflow. I have quite > easily reproduc

Re: Request for Reviews: Cloudberry Logo Variations

Hey! Loving how this is all coming together. My only feedback is, is there a reason we have the TM trademark symbol as part of the logo? I don’t see any other Apache projects that have this and it feels a bit distracting (as well as making the vertical versions of the logo feel slightly off cent

Re: [DISCUSS] Enabling previously disabled test suites with increased container shared memory

Dear Espino, I found that ic-good-opt-on pipeline failed to explain. You can set PGOPTIONS='-c optimizer=on' explicitly. Hope to solve this. Thank you for your time and support. Ed Espino 于2024年11月21日周四 12:40写道： > I've identified a solution for running our previously disabled test suites > (

Re: [DISCUSS] Enabling previously disabled test suites with increased container shared memory

Please: you can call me Ed (艾德) I thought Orca (optimizer) was enabled by default. Is that not the case with Cloudberry? -=e On Wed, Nov 20, 2024 at 10:51 PM 杨江华 wrote: > Dear Espino, > > I found that ic-good-opt-on pipeline failed to explain. You can set > PGOPTIONS='-c > optimizer=on' expl

[DISCUSS] Enabling previously disabled test suites with increased container shared memory

I've identified a solution for running our previously disabled test suites ( cbdb_parallel and instr_in_shmem_verify) in the GitHub Actions CI environment. By increasing the container shared memory using the --shm-size=2gb parameter, these test suites are now passing consistently. I'm currently co

Re: [DISCUSS] Enabling previously disabled test suites with increased container shared memory

Yang Jianghua, Thank you for your feedback. On the core file front, I will experiment with creating core dumps in the GitHub hosted runner container environments. I am familiar with the configuration challenges having core dumps available in containers. I hope after my experimentation, we can get

Re: [DISCUSS] Enabling previously disabled test suites with increased container shared memory

Thank you for sharing this. I am familiar with the previous Cloudberry workflow file and the use of it for "icw-orca-test". Again, I thought the default optimizer setting is "on". In this case, is there a need to even set it? Notice after creating the demo cluster, the optimizer is set to "on". h

Re: [DISCUSS] Enabling previously disabled test suites with increased container shared memory

Hi, Ed refer to cloudberry : https://github.com/apache/cloudberry/blob/1.5.4/.github/workflows/build.yml ```c++ icw-orca-test: needs: build runs-on: [self-hosted, example] env: MAKE_TEST_COMMAND: "-k PGOPTIONS='-c optimizer=on' installcheck-world" TEST_OS: "centos" DUM