Context
As documented in PR #1310, the current Presto integration requires users to set database.host to a non-localhost hostname/IP because the Presto containers run on a Docker network while CLP's database runs on the host network. This mitigation is practical but inconvenient for users operating in diverse network environments.
Long-term Solution
Integrate the Presto services into the CLP Package Docker Compose project introduced in #1178. The tools/deployment/presto-clp directory is only 132 KB in size, so this integration would not significantly increase the package size while substantially improving user convenience.
Benefits
- Eliminates the need for non-localhost hostname configuration
- Provides a unified deployment experience
- Simplifies network connectivity between CLP and Presto services
References
Context
As documented in PR #1310, the current Presto integration requires users to set
database.hostto a non-localhost hostname/IP because the Presto containers run on a Docker network while CLP's database runs on the host network. This mitigation is practical but inconvenient for users operating in diverse network environments.Long-term Solution
Integrate the Presto services into the CLP Package Docker Compose project introduced in #1178. The
tools/deployment/presto-clpdirectory is only 132 KB in size, so this integration would not significantly increase the package size while substantially improving user convenience.Benefits
References