ostinru commented on issue #63: URL: https://github.com/apache/cloudberry-pxf/issues/63#issuecomment-3890394081
> export GOPROXY=https://goproxy.cn,direct I would assume that we don't need golang and pxf-cli inside `pxf-cbdb-dev` container. > ~/.gradle/init.gradle Alternatevly I can imagine following redising of automation tests: Currently we run automation(java) + PXF inside docker: ```mermaid block-beta columns 1 block:Docker["docker"] columns 1 block:Batch Cloudberry PXF block:Storage columns 1 Hadoop S3 end end space Automation end Cloudberry --> PXF PXF --> Hadoop PXF --> S3 ``` And, I think that we can reorganize it to run Automation on host, Possibly run PXF as embedded to automation (so, debug became trivial). Then, Cloudberry / Hadoop / S3 / other services under management of TestContainer. ```mermaid block-beta columns 1 block:Docker["Host"] columns 1 block:Batch["Docker"] Cloudberry space block:Storage columns 1 Hadoop S3 end end space block:Dom0 Automation PXF end end Cloudberry --> PXF PXF --> Hadoop PXF --> S3 ``` In this case gradle will use you host's configuration. However it also has downsides - in tests we will run PXF with all dependencies. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
