We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
How could we query the Properties field of type map in U-SQL statement when using the Avro extractor as shown below:
The Properties field is required to differentiate between different type of records being stored.
@rs = EXTRACT EnqueuedTimeUtc string, SequenceNumber long, Offset string, Body byte[]
FROM @input_file **USING new Microsoft.Analytics.Samples.Formats.ApacheAvro.AvroExtractor**(@" { ""type"": ""record"", ""name"": ""EventData"", ""namespace"": ""Microsoft.ServiceBus.Messaging"", ""fields"": [ { ""name"": ""SequenceNumber"", ""type"": ""long"" }, { ""name"": ""Offset"", ""type"": ""string"" }, { ""name"": ""EnqueuedTimeUtc"", ""type"": ""string"" }, { ""name"": ""SystemProperties"", ""type"": { ""type"": ""map"", ""values"": [ ""long"", ""double"", ""string"", ""bytes"" ] } }, { ""name"": ""**Properties**"", ""type"": { ""type"": ""map"", ""values"": [ ""long"", ""double"", ""string"", ""bytes"", ""null"" ] } }, { ""name"": ""Body"", ""type"": [ ""null"", ""bytes"" ] } ]
} ");
The text was updated successfully, but these errors were encountered:
Could you please let me know if you have any update on the above request?
Sorry, something went wrong.
Please take a look at #147. This PR should solve the issue.
No branches or pull requests
How could we query the Properties field of type map in U-SQL statement when using the Avro extractor as shown below:
The Properties field is required to differentiate between different type of records being stored.
@rs =
EXTRACT
EnqueuedTimeUtc string,
SequenceNumber long,
Offset string,
Body byte[]
}
");
The text was updated successfully, but these errors were encountered: