azureservicebus - What is the purpose of "EnableSubscriptionPartitioning" property in an Azure Service Bus Topic? -


when comes partitioning in azure service bus topic, there 2 properties: enablepartitioning , enablesubscriptionpartitioning.

it clear me enablepartitioning property does. based on understanding of property, when property set true, topic in question partitioned across multiple message brokers.

what not able find concrete information on enablesubscriptionpartitioning property. documentation looked @ describes property as:

value indicates whether partitioning enabled or disabled.

furthermore when create topic property set true (and enable partitioning property set false) topic created me 118784 mb in size (maxsizeinmegabytes property). here's response xml when fetch topic's properties.

<entry xml:base="https://namespace.servicebus.windows.net/$resources/topics?api-version=2016-07">   <id>https://namespace.servicebus.windows.net/gauravtesttopic?api-version=2016-07</id>   <title type="text">gauravtesttopic</title>   <published>2017-08-18t02:00:12z</published>   <updated>2017-08-18t02:00:18z</updated>   <author><name>namespace</name></author>   <link rel="self" href="../gauravtesttopic?api-version=2016-07"/>   <content type="application/xml">     <topicdescription xmlns="http://schemas.microsoft.com/netservices/2010/10/servicebus/connect" xmlns:i="http://www.w3.org/2001/xmlschema-instance">       <defaultmessagetimetolive>p10675199dt2h48m5.4775807s</defaultmessagetimetolive>       <maxsizeinmegabytes>118784</maxsizeinmegabytes>       <requiresduplicatedetection>false</requiresduplicatedetection>       <duplicatedetectionhistorytimewindow>pt10m</duplicatedetectionhistorytimewindow>       <enablebatchedoperations>true</enablebatchedoperations>       <sizeinbytes>0</sizeinbytes>       <filteringmessagesbeforepublishing>false</filteringmessagesbeforepublishing>       <isanonymousaccessible>false</isanonymousaccessible>       <authorizationrules></authorizationrules>       <status>active</status>       <createdat>2017-08-18t02:00:11.5270915z</createdat>       <updatedat>2017-08-18t02:00:18.087z</updatedat>       <accessedat>0001-01-01t00:00:00z</accessedat>       <supportordering>true</supportordering>       <countdetails xmlns:d2p1="http://schemas.microsoft.com/netservices/2011/06/servicebus">         <d2p1:activemessagecount>0</d2p1:activemessagecount>         <d2p1:deadlettermessagecount>0</d2p1:deadlettermessagecount>         <d2p1:scheduledmessagecount>0</d2p1:scheduledmessagecount>         <d2p1:transfermessagecount>0</d2p1:transfermessagecount>         <d2p1:transferdeadlettermessagecount>0</d2p1:transferdeadlettermessagecount>       </countdetails>       <subscriptioncount>0</subscriptioncount>       <autodeleteonidle>p10675199dt2h48m5.4775807s</autodeleteonidle>       <enablepartitioning>false</enablepartitioning>       <isexpress>false</isexpress>       <entityavailabilitystatus>available</entityavailabilitystatus>       <enablesubscriptionpartitioning>true</enablesubscriptionpartitioning>       <enableexpress>false</enableexpress>     </topicdescription>   </content> </entry> 

the problem run when try update topic, error message service complaining invalid size. because topic not partitioned, size should 1 of following: 1gb, 2gb, 3gb, 4gb or 5gb.

any insights highly appreciated.


Comments

Popular posts from this blog

Is there a better way to structure post methods in Class Based Views -

performance - Why is XCHG reg, reg a 3 micro-op instruction on modern Intel architectures? -

jquery - Responsive Navbar with Sub Navbar -