Wiki article that references new Zed join docs #1729
Merged
Conversation
This file contains 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
|
Reads great to me @philrz . It reminds me that the app will need some new designs to take advantage of multiple inputs and from multi line scripts. |
jameskerr
approved these changes
Jul 6, 2021
nwt
approved these changes
Jul 6, 2021
Co-authored-by: Noah Treuhaft <noah.treuhaft@gmail.com>
Co-authored-by: Noah Treuhaft <noah.treuhaft@gmail.com>
Co-authored-by: Noah Treuhaft <noah.treuhaft@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Since Brim
v0.25.0won't yet directly use the full Zed Lake API (#1618), the tl;dr onjoinis that the common multi-Pool joins will have to be done from outside the app viazapifor now. Now that we have thejoindocs in the Zed repo, the new article added in this PR points to them and walks through an example that useszapifor such a join, after which the data is pushed back into a Pool for further use within Brim.If you want to see how this doc will look rendered in a GitHub wiki, I've published it at a temporary location at https://github.com/philrz/scratchwiki/wiki.