[MXS-1025] qc_sqlite always reports " Statement was parsed, but not classified" Created: 2016-11-23 Updated: 2020-08-25 Resolved: 2016-11-23 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | qc_sqlite |
| Affects Version/s: | 2.0.1 |
| Fix Version/s: | 2.0.5, 2.1.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | Mars Ma | Assignee: | Johan Wikman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | plugins | ||
| Environment: |
Linux db2 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux |
||
| Description |
|
The following logs are reported all the time qc_sqlite: Statement was parsed, but not classified: "SAVEPOINT sa_savepoint_1" |
| Comments |
| Comment by Johan Wikman [ 2016-11-23 ] |
|
Unfortunately, in 2.0.1, there is no way to suppress that logging. In 2.1.0 also that logging is behind the log_unrecognized_statements setting so that it is suppressed by default. However, it is actually quite puzzling that you see that error. Namely, the message claims that the statement was parsed completely but not classfied, and qc_sqlite is definitely not capable of parsing a statement like "SAVEPOINT sa_savepoint_1". |
| Comment by Mars Ma [ 2016-11-24 ] |
|
@Johan Wikman thanks for your comment ! you mean that the logging is not suppressed, but it doesn't affect maxscale working, so I can ignore the "not classified logs", right ? |
| Comment by Johan Wikman [ 2016-11-24 ] |
|
Yes, you can safely ignore those messages. If a statement cannot be classified it will be sent to the master and that's where those statements should go. The puzzling thing is that according to the logged message, the statement was parsed, but not classified. I would have expected an error message like Statement was neither parsed nor recognized from keywords (Sqlite3 error: ...). Indeed, that's the only message I was able to produce (and that's not logged by default). |