Cleaned up qlafilter, topfilter and namedserverfilter instance creation

The change fixes a crash when no filebase parameter is given for the filter.

The instance creation functions of these filters had spossible memory leaks in
case errors in the configuration occurred. In addition to these, they would be
successfully created even if unexpected parameters were given.
This commit is contained in:
Markus Makela 2016-02-23 21:35:45 +02:00
parent 3eb0b9814f
commit 92f8aa9965
2 changed files with 4 additions and 4 deletions

View File

@ -43,11 +43,11 @@ anymore and the `filebase` parameter should be used instead.
## Filter Parameters
The QLA filter accepts a number of optional parameters, these were introduced in the 1.0 release of MaxScale.
The QLA filter has one mandatory parameter, `filebase`, and a number of optional parameters. These were introduced in the 1.0 release of MaxScale.
### Filebase
The basename of the output file created for each session. A session index is added to the filename for each file written.
The basename of the output file created for each session. A session index is added to the filename for each file written. This is a mandatory parameter.
```
filebase=/tmp/SqlQueryLog

View File

@ -40,11 +40,11 @@ options=case,extended
## Filter Parameters
The top filter accepts a number of optional parameters.
The top filter has one mandatory parameter, `filebase`, and a number of optional parameters.
### Filebase
The basename of the output file created for each session. A session index is added to the filename for each file written.
The basename of the output file created for each session. A session index is added to the filename for each file written. This is a mandatory parameter.
```
filebase=/tmp/SqlQueryLog