You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Gordon Sim (Jira)" <ji...@apache.org> on 2019/09/18 20:47:00 UTC

[jira] [Commented] (DISPATCH-1420) Support server side filtering of entities

    [ https://issues.apache.org/jira/browse/DISPATCH-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16932824#comment-16932824 ] 

Gordon Sim commented on DISPATCH-1420:
--------------------------------------

[~lulf] If you just want a specific entity, you can already do READ rather than a QUERY, and specify the name of the object you want. 

> Support server side filtering of entities
> -----------------------------------------
>
>                 Key: DISPATCH-1420
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-1420
>             Project: Qpid Dispatch
>          Issue Type: Improvement
>    Affects Versions: 1.8.0
>            Reporter: Ulf Lilleengen
>            Assignee: Ganesh Murthy
>            Priority: Major
>
> In order to inspect a specific connection or a specific link on a connection, one has to query all connections and all links and do the filtering client side. For deployments with a lot of entities, this consumes an unnecessary amount of bandwith as well as complexity for clients.
>  
> This load could be reduced if the router management had the capability to specify filters along with the query, and the ability to do the filtering in the router before returning the result. Depending on the underlying datastructure, it could be possible to query more efficiently doing lookup by id for instance.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org