Users/ramacg/add doc and format code#466
Users/ramacg/add doc and format code#466ag-ramachandran wants to merge 2 commits intofeature/IngestV2from
Conversation
ag-ramachandran
had a problem deploying
to
build
GitHub Actions
Error
ag-ramachandran
had a problem deploying
to
build
GitHub Actions
Error
ag-ramachandran
had a problem deploying
to
build
GitHub Actions
Failure
ag-ramachandran
had a problem deploying
to
build
GitHub Actions
Failure
|
Can you explain how did you format? |
| @@ -0,0 +1,807 @@ | |||
| # Kusto Ingest-V2 Architecture Documentation | |||
There was a problem hiding this comment.
I assume that this document is generated by copilot
To me, it's not very useful - it shows a lot of type hierarchies in a way that is really not helpful for the user.
There is some useful information, but it doesn't explain the basics - what is an source, ingestor, uploader, etc and how they work together.
I think it should be structred as more of a guide, have comparison to v1, and explain why more
| - `getOperationSummaryAsync(operation)`: Returns aggregated status counts | ||
| - `getOperationDetailsAsync(operation)`: Returns detailed status with individual file/blob details | ||
|
|
||
| **Note**: Streaming ingestion operations cannot be tracked. Calling tracking methods on streaming operations will return empty results with a warning. |
There was a problem hiding this comment.
Is this true for your code? it shouldn't be
In C#, streaming gets the results immediately and saves them inside, so you can call these methods on them and they will work.
|
|
||
| **Operation Tracking**: | ||
|
|
||
| Queued ingestion returns an `IngestionOperation` that can be used to track the ingestion status: |
There was a problem hiding this comment.
No mention that you need to turn on Operation Tracking via ingestion properties.
Infact, the properties aren't explained or defined anywhere
2 participants
No description provided.