[hotfix] Fix SELECT statement in http.md#37
Merged
davidradl merged 2 commits intoapache:mainfrom Mar 31, 2026
Merged
Conversation
davidradl
reviewed
Mar 27, 2026
Contributor
|
nit: the title should be statement not statment |
sofie204
changed the title
Contributor
Author
Thank you for pointing that out @davidradl. Both changes have been made and the spelling has been modified. |
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.
The
SELECTexample in the HTTP lookup source docs usesc.isActiveandc.balance, but the table schema defines these fields nested inside a details ROW. This causes NULL results when users follow the example. The fix is to usec.details.isActiveandc.details.nestedDetails.balance.