[GitHub] [pulsar] svabra added a comment to the discussion: [Bug] Failed to pull-up docker-compose for broker, bookie, zk and pulsar-sql
GitHub user svabra added a comment to the discussion: [Bug] Failed to pull-up docker-compose for broker, bookie, zk and pulsar-sql @tisonkun thanks for having a look. Yes, as Java Developer I know. But, think of it not for me, but for people new to Pulsar and PulsarSQL. Why are we not preparing a Standalone edition, which also includes the PulsarSQL/Trino with REST/8081? And this Docker-Compose should run out of the box without tinkering. Without adapting the pulsar.properties or any classpaths/libraries. Otherwise, folks will always immediately switch to Flink and Flink SQL for pull and push queries. GitHub link: https://github.com/apache/pulsar/discussions/20054#discussioncomment-5573473 This is an automatically sent email for commits@pulsar.apache.org. To unsubscribe, please send an email to: commits-unsubscr...@pulsar.apache.org
[GitHub] [pulsar] svabra added a comment to the discussion: [Bug] Failed to pull-up docker-compose for broker, bookie, zk and pulsar-sql
GitHub user svabra added a comment to the discussion: [Bug] Failed to pull-up docker-compose for broker, bookie, zk and pulsar-sql I was wondering. If the CLI is triggering the Gateway, which includes the REST service according to this [presentation](https://youtu.be/DnXu0Q0mvTM?t=962), then only the exposition of the port 8081 should be done. Should we not address this in the deployment documentation? GitHub link: https://github.com/apache/pulsar/discussions/20054#discussioncomment-5569227 This is an automatically sent email for commits@pulsar.apache.org. To unsubscribe, please send an email to: commits-unsubscr...@pulsar.apache.org
