Roger Johnson

My feedback

  1. 13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Stream Analytics  ·  Flag idea as inappropriate…  ·  Admin →
    Roger Johnson supported this idea  · 
  2. 13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Stream Analytics  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Roger Johnson commented  · 

    One use case involves being able to control (from a single source) the window parameters for a group of queries. The thinking here is to manage all related queries time windows via a common configuration setting.

    Also, this use case could not be satisfied with joined reference data.

    Example:
    Job Query 1:

    SELECT
    System.TimeStamp AS PointTime,
    COUNT(SessionId) AS Count
    FROM [inputhub] TIMESTAMP BY EventTime
    GROUP BY
    SessionId, TUMBLINGWINDOW(minute, CONFIGVALUE(‘QueryWindowTime’))

    Job Query 2:

    SELECT
    System.TimeStamp AS PointTime,
    AVG(WaitTime) AS Count
    FROM [inputhub]
    GROUP BY
    SessionId, TUMBLINGWINDOW(minute, CONFIGVALUE(‘QueryWindowTime’))

    Other use cases like filtering on an input query field could be done via reference data, but again I would prefer that option to be supported by configuration settings as well.

    Roger Johnson supported this idea  · 
    Roger Johnson shared this idea  · 
  3. 32 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  4 comments  ·  Stream Analytics  ·  Flag idea as inappropriate…  ·  Admin →
    Roger Johnson supported this idea  · 
    An error occurred while saving the comment
    Roger Johnson commented  · 

    The recent changes to have multiple SELECTS in a single job to target multiple outputs is good, though I would still like to group jobs to de-clutter the view at the top level Stream Analytics portal page.

    An error occurred while saving the comment
    Roger Johnson commented  · 

    I stated mostly a UI problem at the time, because it could have been an Azure Portal UI change to display a group of jobs in a new higher level object like a JobGroup object or JobDeployment object. I think it would be a cleaner UI path to only see the top high level job groups in Azure. and clicking on one of these would take you into a Job list view like you currently have today at the subscription level -- except it would only show those jobs that were created under that JobDeployment, not all the jobs for the subscription. Hope this makes sense.

    Roger Johnson shared this idea  · 

Feedback and Knowledge Base