Conversation
|
🚀 Build success! Latest successful preview: https://6686e5de61200e53271152aa--unruffled-blackwell-31bfb2.netlify.app Commit SHA: b00fb83
|
Contributor
|
@goodroot is this good to me merged? |
jerrinot
approved these changes
Jul 15, 2024
Contributor
Author
|
@jerrinot Yes! Minor edits took place in transit. 💥 |
bluestreak01
added a commit
that referenced
this pull request
Jan 12, 2026
- Add frame_start and frame_end syntax definitions to syntax.md - Add syntax synopsis section to overview.md for newcomers - Fix incorrect RANGE frame limitation description (issue #5177) Co-Authored-By: Claude Opus 4.5 <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
From original @jerrinot PR:
This PR documents the new properties to enable HTTP Basic Auth in QuestDB Open Source.
Besides this, it also:
nmoption introduced in feat(http): add support fornm=truequery parameter in text export (/exp) to exclude metadata questdb#4639 - it's unrelated to security, but it's a tiny change so I squeezed it into this PR.jose,jqand what not. We recommend ILP@HTTP for new users. Authentication in ILP@TCP in QuestDB OSS is convoluted. With the introduction of HTTP Basic Auth in QuestDB there is no good reason why anyone should use ILP@TCP.I feel we are still missing a guide on "security hardening": Explaining how to secure QuestDB for production usage, the difference between OSS and EE, etc.
src: https://github.com/questdb/questdb.io/pull/2352/