[
https://issues.apache.org/jira/browse/AMQ-9541?focusedWorklogId=946279&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-946279
]
ASF GitHub Bot logged work on AMQ-9541:
---------------------------------------
Author: ASF GitHub Bot
Created on: 02/Dec/24 05:33
Start Date: 02/Dec/24 05:33
Worklog Time Spent: 10m
Work Description: kenliao94 commented on PR #1275:
URL: https://github.com/apache/activemq/pull/1275#issuecomment-2510617536
@jeanouii i Sorry, not following this logic here. Isn't this.limitQuery a
no-ops? It just returns the original query (line 1188)
Issue Time Tracking
-------------------
Worklog Id: (was: 946279)
Time Spent: 1h 20m (was: 1h 10m)
> Missing limit on expensive queries.
> -----------------------------------
>
> Key: AMQ-9541
> URL: https://issues.apache.org/jira/browse/AMQ-9541
> Project: ActiveMQ Classic
> Issue Type: Bug
> Affects Versions: 5.18.5, 6.1.2
> Reporter: Jean-Louis Monteiro
> Priority: Major
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> https://issues.apache.org/jira/browse/AMQ-6049 did add the ability to limit
> the size of the records returned by the database.
>
> Some queries do not apply the limit even though the limit is applied on the
> Java side.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
