Module: check_mk Branch: master Commit: 6d4ea28831ab3a5fa0d8c79816497137abdbe883 URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=6d4ea28831ab3a… Author: Mathias Kettner <mk(a)mathias-kettner.de> Date: Sun Jan 30 13:49:38 2011 +0100 Updated bug entries --- .bugs/117 | 30 ++++++++++++++++++++++++++++++ 1 files changed, 30 insertions(+), 0 deletions(-) diff --git a/.bugs/117 b/.bugs/117 new file mode 100644 index 0000000..8cb430b --- /dev/null +++ b/.bugs/117 @@ -0,0 +1,30 @@ +Title: Change handling of undefined columns +Component: livestatus +Benefit: 3 +State: open +Cost: 2 +Date: 2011-01-30 13:45:33 +Class: feature + +We can introduce a livestatus option that affects the handling of +unknown columns. The problem is that if in a new version of Livestatus +are introduced columns and new versions of addons use them that +old versions of Livestatus will not be compatible. If the old +versions would not crash but simply output empty columns in that +case, the problem could be tackled. + +Proposition for a parameter: + +unused_columns=warn ---> Log a warning in that case +unused_columns=fail ---> Query fails (current behavious) +unused_columns=ignore ---> Do not log + +In case of warn/ignore a default value will be sent for +the unknown columns, e.g. None/null in python/json mode and +an empty column in CVS. + +We could make 'warn' into a default. + +Multisite must then be aware of the possibility that a columns +value is None. This is easier than just querying a livestatus +version and make a switch.