[
https://issues.apache.org/jira/browse/AMQ-6049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15010855#comment-15010855
]
ASF subversion and git services commented on AMQ-6049:
------------------------------------------------------
Commit 78c959a5c44e51d3591987962897e04fc81b06f0 in activemq's branch
refs/heads/master from [~dejanb]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=78c959a ]
https://issues.apache.org/jira/browse/AMQ-6049 - limit query results
> Add option to limit results from expensive queries
> --------------------------------------------------
>
> Key: AMQ-6049
> URL: https://issues.apache.org/jira/browse/AMQ-6049
> Project: ActiveMQ
> Issue Type: Improvement
> Components: JDBC
> Affects Versions: 5.12.0
> Reporter: Dejan Bosanac
> Assignee: Dejan Bosanac
> Fix For: 5.13.0
>
>
> When using priority messages with JDBC store, a query that recovers messages
> from the db can be very expensive due to the sorting it has to do. The best
> way I found to improve the performance of that query is to limit the sorting
> set by limiting the number of entries expected from the query. This assumes
> changing the actual query and is vendor specific.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
