docs(clp-config): Add commented out default values to nullable mcp_server and presto in clp-config.yaml; Clarify configuration steps in the manuals.#1635
Conversation
…erver` and `presto` in `clp-config.yaml`; Clarify configuration steps in the manuals.
WalkthroughDocumentation and configuration templates were updated to provide explicit MCP server and Presto client host/port examples; guides now show direct configuration entries and clarify behavior when the mcp_server section is commented or null. Template files add commented host/port placeholders for mcp_server and presto. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Tip Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
@rishikeshdevsot may i get your approval for the modifications in this docs if they look good to you?
There was a problem hiding this comment.
@davemarco may i get your approval for the modifications in this docs if they look good to you?
There was a problem hiding this comment.
I think haiqi originally did not want to put the "default" port since there is no error when starting the package if the port is incorrect. Like he wanted to force the user to input their specific port
There was a problem hiding this comment.
hmm.. even if we ask users to provide a port, if we don't do any checks (i guess we really can't), there is no guarantee that the port is valid?
fwiw, i believe providing a default helps avoid collision with ports of other services in the CLP package / other well-known ports
There was a problem hiding this comment.
@davemarco / @kirkrodrigues could you check if the latest proposal would address those concerns of users using non-standard ports
junhaoliao
left a comment
There was a problem hiding this comment.
@davemarco / @kirkrodrigues could you check if the latest proposal would address those concerns of users using non-standard ports
| * Update the `presto` key with the host and port of the Presto cluster. If you follow the | ||
| [Setting up Presto](#setting-up-presto) section, the host is `localhost` and the port is | ||
| `8889`. | ||
| * Update the `presto` key with the `host` and `port` of the Presto cluster. Replace the default |
There was a problem hiding this comment.
| * Update the `presto` key with the `host` and `port` of the Presto cluster. Replace the default | |
| * Update the `presto` key with the `host` and `port` of the Presto coordinator. Replace the default |
| host: "<ip-address>" | ||
| port: <port> | ||
| host: "localhost" | ||
| port: 8889 |
There was a problem hiding this comment.
| port: 8889 | |
| host: <presto-coordinator-ip> # default: "localhost" | |
| port: <presto-coordinator-port> # default: 8889 |
| ## host: "localhost" | ||
| ## port: 8889 |
There was a problem hiding this comment.
| ## host: "localhost" | |
| ## port: 8889 | |
| ## host: <presto-coordinator-ip> # default: "localhost" | |
| ## port: <presto-coordinator-port> # default: 8889 |
There was a problem hiding this comment.
@davemarco / @kirkrodrigues could you check if the latest proposal would address those concerns of users using non-standard ports
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
components/package-template/src/etc/clp-config.template.json.yaml (1)
107-107:⚠️ Potential issue | 🟡 MinorMissing
mcp_serverhost/port comments in this template.The PR objective states that commented example fields for
hostandportshould be added to both themcp_serverandprestosections. Thetext.yamltemplate has them (lines 90–91), but this file does not. This looks like an oversight.Proposed fix
`#mcp_server`: null +## host: "localhost" +## port: 8000 #🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@components/package-template/src/etc/clp-config.template.json.yaml` at line 107, The template is missing commented example host/port fields for the mcp_server and presto sections; update the clp-config.template.json.yaml to mirror the text.yaml examples by adding commented lines like "# host: example.com" and "# port: 1234" under both the mcp_server and presto keys (ensure comments are YAML-style and placed immediately beneath the mcp_server and presto entries so they serve as clear usage examples).
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Outside diff comments:
In `@components/package-template/src/etc/clp-config.template.json.yaml`:
- Line 107: The template is missing commented example host/port fields for the
mcp_server and presto sections; update the clp-config.template.json.yaml to
mirror the text.yaml examples by adding commented lines like "# host:
example.com" and "# port: 1234" under both the mcp_server and presto keys
(ensure comments are YAML-style and placed immediately beneath the mcp_server
and presto entries so they serve as clear usage examples).
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@components/package-template/src/etc/clp-config.template.json.yaml`:
- Around line 160-162: The presto section uses angle-bracket placeholders that
are inconsistent with the mcp_server section and can create invalid YAML; change
the presto block (keys: presto.host and presto.port) to show the actual default
values (e.g., "localhost" and 8889) as the values (not angle-bracket tokens) and
keep a short inline comment indicating they can be replaced, mirroring how
mcp_server is represented so uncommenting the block won't introduce invalid
tokens.
| #presto: null | ||
| ## host: <presto-coordinator-ip> # default: "localhost" | ||
| ## port: <presto-coordinator-port> # default: 8889 |
There was a problem hiding this comment.
🧹 Nitpick | 🔵 Trivial
Inconsistent placeholder style compared to mcp_server section.
Lines 108–109 for mcp_server show actual default values ("localhost", 8000), while here angle-bracket placeholders are used with defaults relegated to trailing comments. Consider using the same pattern for both sections — i.e., showing the actual defaults directly and noting they can be replaced:
Suggested diff
`#presto`: null
-## host: <presto-coordinator-ip> # default: "localhost"
-## port: <presto-coordinator-port> # default: 8889
+## host: "localhost"
+## port: 8889This would also avoid leaving invalid YAML tokens (<...>) that would cause a parse error if a user uncomments the block without replacing them.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| #presto: null | |
| ## host: <presto-coordinator-ip> # default: "localhost" | |
| ## port: <presto-coordinator-port> # default: 8889 | |
| `#presto`: null | |
| ## host: "localhost" | |
| ## port: 8889 |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@components/package-template/src/etc/clp-config.template.json.yaml` around
lines 160 - 162, The presto section uses angle-bracket placeholders that are
inconsistent with the mcp_server section and can create invalid YAML; change the
presto block (keys: presto.host and presto.port) to show the actual default
values (e.g., "localhost" and 8889) as the values (not angle-bracket tokens) and
keep a short inline comment indicating they can be replaced, mirroring how
mcp_server is represented so uncommenting the block won't introduce invalid
tokens.
Description
This PR updates configuration comments and user documentation for both the MCP server and Presto:
hostandportexample fields (commented out) to themcp_serverandprestosections inclp-config.yaml.guides-mcp-server, emphasizing uncommenting the block and replacing defaults when needed.localhost,8889) and clarifies that users may replace them if needed.These changes improve clarity for users configuring CLP components.
Checklist
breaking change.
Validation performed
task docs:serveand inspected the docs.Summary by CodeRabbit