[MXS-1211] maxrows should be configurable to return error when limit has been exceeded Created: 2017-03-29  Updated: 2017-04-03  Resolved: 2017-03-31

Status: Closed
Project: MariaDB MaxScale
Component/s: maxrows
Affects Version/s: None
Fix Version/s: 2.1.3

Type: Task Priority: Major
Reporter: Johan Wikman Assignee: Massimiliano Pinto (Inactive)
Resolution: Fixed Votes: 0
Labels: None


 Description   

It should be possible to configure maxrows to return an error when the maximum has been reached instead of a resultset of 0 rows.

There should, for instance, be a configuration setting like:

return=empty|error|ok

with empty being the default.

 Comments   
Comment by Massimiliano Pinto (Inactive) [ 2017-03-30 ]

Currently working on the new feature:

MySQL [(none)]> select * from test.t4;
ERROR 1415 (0A000): Row limit/size exceeded for query: select * from test.t4
MySQL [(none)]> select repeat('a', 1000000);
ERROR 1415 (0A000): Row limit/size exceeded for query: select repeat('a', 1000000)
MySQL [(none)]>

Note:

error message "ERROR 1415 (0A000): Row limit/size exceeded for query: "
+
input query

Comment by Massimiliano Pinto (Inactive) [ 2017-03-30 ]

New parameter for maxsrows filter:

max_resultset_return=empty|error|ok
Default, 'empty' is to return an empty set, as the current implementation.

'err' will return an ERR reply with the input SQL statement
'ok' will return an OK packet

Generated at Thu Feb 08 04:05:02 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.