-
Notifications
You must be signed in to change notification settings - Fork 35
Drop extents syntax change #442
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
Conversation
66948bb to
d6c5178
Compare
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.
Pull Request Overview
This PR updates the Kusto command syntax for dropping extent tags to include the table name in the command, changing from .drop async extent tags to .drop async table $tableName extent tags. This appears to align with updated Kusto API requirements.
- Command syntax updated to include table name in extent tags drop operation
- Code formatting improvements (added braces to single-line if-else statements for consistency)
- GitHub Actions workflow enhanced with timeout and batch mode for Maven
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| connector/src/main/scala/com/microsoft/kusto/spark/utils/CslCommandsGenerator.scala | Updated extent tags drop command syntax to include table name; reformatted if-else statements with explicit braces |
| .github/workflows/build.yml | Added 40-minute timeout and batch mode flag to Maven verify step |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
connector/src/main/scala/com/microsoft/kusto/spark/utils/CslCommandsGenerator.scala
Show resolved
Hide resolved
# Conflicts: # connector/src/main/scala/com/microsoft/kusto/spark/utils/CslCommandsGenerator.scala
d6c5178 to
4605600
Compare
Co-authored-by: Ramachandran A G <[email protected]>
* * Fix syntax for V11 engine for extents drop (#442)
Pull Request Description
[Add a description of your pull request here]
Future Release Comment
[Add description of your change, to include in the next release]
[Delete any or all irrelevant sections, e.g. if your change does not warrant a release comment at all]
Breaking Changes:
Features:
Fixes: