-
Notifications
You must be signed in to change notification settings - Fork 88
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
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
99079ac
f9c97e1
a01fc32
d9eaff0
f6ea242
c85afa3
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
|
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @rishikeshdevsot may i get your approval for the modifications in this docs if they look good to you? |
|
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @davemarco may i get your approval for the modifications in this docs if they look good to you?
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 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
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 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
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @davemarco / @kirkrodrigues could you check if the latest proposal would address those concerns of users using non-standard ports |
| Original file line number | Diff line number | Diff line change | ||||||
|---|---|---|---|---|---|---|---|---|
|
|
@@ -57,14 +57,13 @@ Using Presto with CLP requires: | |||||||
| retention_period: null | ||||||||
| ``` | ||||||||
|
|
||||||||
| * 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 | ||||||||
|
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||||
| values if necessary. | ||||||||
|
|
||||||||
| ```yaml | ||||||||
| presto: | ||||||||
| host: "<ip-address>" | ||||||||
| port: <port> | ||||||||
| host: "localhost" | ||||||||
| port: 8889 | ||||||||
|
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||||
| ``` | ||||||||
|
|
||||||||
| :::{note} | ||||||||
|
|
||||||||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧹 Nitpick | 🔵 Trivial
Inconsistent placeholder style compared to
mcp_serversection.Lines 108–109 for
mcp_servershow 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
This would also avoid leaving invalid YAML tokens (
<...>) that would cause a parse error if a user uncomments the block without replacing them.📝 Committable suggestion
🤖 Prompt for AI Agents