Simon Luckenuik

My feedback

  1. 1,053 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  16 comments  ·  Service Fabric  ·  Flag idea as inappropriate…  ·  Admin →
    Simon Luckenuik supported this idea  · 
  2. 62 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Service Bus  ·  Flag idea as inappropriate…  ·  Admin →
    Simon Luckenuik supported this idea  · 
  3. 330 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Service Bus  ·  Flag idea as inappropriate…  ·  Admin →
    Simon Luckenuik supported this idea  · 
  4. 33 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Notification Hubs  ·  Flag idea as inappropriate…  ·  Admin →
    Simon Luckenuik supported this idea  · 
  5. 96 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Notification Hubs  ·  Flag idea as inappropriate…  ·  Admin →

    For the notification related events, we can only report if the message was successfully sent to the respective provider’s PNS. The actual delivery of the message is handled by the PNS and we don’t have any direct visibility in this. Where we can add some hooks are instances where maybe the registration expires etc. Let me know if there are any other places you will find this useful.

    Simon Luckenuik supported this idea  · 
  6. 380 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  Azure Search » REST API  ·  Flag idea as inappropriate…  ·  Admin →
    Simon Luckenuik supported this idea  · 
  7. 467 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  Azure Search  ·  Flag idea as inappropriate…  ·  Admin →
    Simon Luckenuik supported this idea  · 
  8. 1,143 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  35 comments  ·  Azure Search » Client SDK  ·  Flag idea as inappropriate…  ·  Admin →
    Simon Luckenuik supported this idea  · 
  9. 261 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Azure Search » Data Types  ·  Flag idea as inappropriate…  ·  Admin →
    Simon Luckenuik supported this idea  · 
  10. 407 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Azure Search » Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
    Simon Luckenuik supported this idea  · 
  11. 601 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Azure Search  ·  Flag idea as inappropriate…  ·  Admin →
    Simon Luckenuik supported this idea  · 
  12. 721 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Azure Search » Indexing  ·  Flag idea as inappropriate…  ·  Admin →
    Simon Luckenuik supported this idea  · 
  13. 148 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    10 comments  ·  Azure Functions  ·  Flag idea as inappropriate…  ·  Admin →

    I’ve gotten a few questions about this item recently, so I just wanted to give a more detailed status. We still have this on the backlog; it hasn’t been forgotten. But we don’t have a clear timeline for when we would get to it right now. The “unplanned” status just means that it can’t be tied to a timeline, but we do think this is a valid request that we would like to have in the product.
    - Matthew

    Simon Luckenuik supported this idea  · 
  14. 3,825 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    80 comments  ·  Azure Cosmos DB » SQL API  ·  Flag idea as inappropriate…  ·  Admin →
    Simon Luckenuik supported this idea  · 
  15. 3,803 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    126 comments  ·  Azure Cosmos DB  ·  Flag idea as inappropriate…  ·  Admin →

    Reopening this user voice item as our support for Skip/Take (Offset/Limit) was only limited to single partition queries.

    Update.

    The newly released .NET SDK v3 now includes support for x-partition queries using Offset/Limit. You can learn more about v3 SDK and try it and provide feedback on our github repo here.
    github.com/azure/azure-cosmos-dotnet-v3

    We will also be back-porting this functionality to our .NET v2 SDK. This work will begin shortly and we anticipate it to be released in September.

    Once that is released we will mark this feature as complete.

    Thank you for your patience and votes.

    Simon Luckenuik supported this idea  · 
  16. 1,138 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    18 comments  ·  Signup and Billing  ·  Flag idea as inappropriate…  ·  Admin →
    Simon Luckenuik supported this idea  · 
1 3 Next →

Feedback and Knowledge Base