Partition key not set in Event hub output


i have following query in stream analytics:

select p2.gatewayid gatewayid,p2.deviceid, 'powerminute' property , p2.time, p2.value 
output1 powerreading p2 timestamp time ...

"output1" configured output event hub , have set "partition key column" gatewayid. yet, when @ messages in event hub, partitionkey null. message in event hub json , contains gatewayid element expected. ideas why partition key not set?

and follow-up: message event hub array, contains 1 item, in cases, e.g. after stopping job , restarting start time being "last stopped time", there more 1 item in array. in test case gatewayid same, if there more 1 gatewayid in array, how partitionkey selected? reason doesn't work , there way fix it?

do mean eventdata.partitionkey value in output event hub messages ? long gatewayid values being used hash , distribute events different eh partitions, need partitionkey set reason ? 

this design way asa sends data output eh . when configure asa eh partitionkey - best write throughput, asa doesn't use eh client partitioning , spraying events different partitions (eh client needs partitionkey set distribution) , internally hashes partitionkey , distributes events parallel eh senders write each partition directly. 

to avoid ambiguous behavior in arrays, please try explicitly specify item need use partitionkey ( see getarrayelement). 

cheers !

[disclaimer] posting provided "as is" no warranties, , confers no rights. user assumes all.



Microsoft Azure  >  Azure Stream Analytics



Comments

Post a Comment

Popular posts from this blog

Azure DocumentDB Owner resource does not exist

having same error microsoft.azure.documents.documentclientexception: message: {"errors":["owner resource not exist"]} , scenario. when deployed webapp azure , try document docdb throws error. docdb exists in azure , contains document looking for. weird local machine(running vs) works fine. i'm using same settings in azure , local. have , idea this. thanks Microsoft Azure  >  Azure Cosmos DB
Read more

job syspolicy_purge_history job fail in sqlserver 2008

Image
hello guys, when installed sqlserver,it automatically created 1 job name job syspolicy_purge_history. but failed @ step 1. the reason is: date                11/6/2010 2:00:00 am log                job history (syspolicy_purge_history) step id                1 server                mxosv-otsdb01 job name                syspolicy_purge_history step name                verify automation enabled. duration                00:00:00 sql severity                16 sql message id                34022 operator emailed                operator net sent                operator paged                retries attempted                0 message executed user: nt authority\system. policy automation turned off. [sqlstate 42000] (error 34022).  the step failed. have run statement: select msdb.dbo.fn_syspolicy_is_automation_enabled the returned valus 0. what can resolve it? or can delete job manually.   thanks in advance. if haven't things want,be
Read more

Trying to register with public marketplace error with 'Get-AzureStackStampInformation'

when trying register against public azure adfs azure stack error below. logs can found at: c:\maslogs\azurestack.azureregistration.2017-10-12.01-31-23.log  and  \\azs-ercs01\c$\maslogs error occurred checking stamp information: system.management.automation.remoteexception: term 'get-azurestackstampinformation' not recognized name of cmdlet, function, script file, or operable program. check spelling of name, or if path included, verify path correct , try again. @ c:\azurestack-tools-master\registration\registerwithazure.psm1:1106 char:5 +     throw "logs can found at: $global:azureregistrationlog  and  \ ... +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + categoryinfo          : operationstopped: (logs can fou... , try again.:string) [], runtimeexception     + fullyqualifiederrorid : logs can found at: c:\maslogs\azurestack.azureregistration.2017-10-12.01-31-23.log  a    nd  \\azs-ercs01\c$\maslogs error occurred chec
Read more