KQL fixes #127
Open
KQL fixes #127
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
updated KQL table name to lowercase to match setup instructions
Removed sql and buggy kql from the script to make it run smoothly
|
@microsoft-github-policy-service agree |
1 similar comment
|
@microsoft-github-policy-service agree |
updated Script to create an Eventhouse instead of just a KQLDB
|
Just realised that my follow up committs also landed in this pull request. will work with cleaner branching next time. This pull request now includes documentation changes for streaming datasets and a bug fix where the realtime app kept failing to deploy properly. This pull request adds some clarity and stability to the use of realtime data to the project. |
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.
Small fixes to the kql scripts to make them run smoothly during a demo. table name needs to be in lowercase, as that's what created during setup. also, sql scripts have no place in kql querysets. if you want to keep them, I suggest to comment them out.