[Why] Enables more flexible monitoring conditions. When I use "monitor job.*=", will get "query=>{"job":{"*":null}}". It's not what I want. I want "query=>{"job.*": null}".
Signed-off-by: Wu Zhende wuzhende666@163.com --- lib/monitor.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/monitor.rb b/lib/monitor.rb index 56283e10..67c2389a 100755 --- a/lib/monitor.rb +++ b/lib/monitor.rb @@ -51,7 +51,7 @@ class Monitor def merge_overrides return if @overrides.empty?
- revise_hash(@query, @overrides, true) + @query.merge!(@overrides) end
def field_check
On Mon, Nov 09, 2020 at 03:18:05PM +0800, Wu Zhende wrote:
[Why]
There is no need add "why", unless you have "how" or something.
Thanks, Xueliang
Enables more flexible monitoring conditions. When I use "monitor job.*=", will get "query=>{"job":{"*":null}}". It's not what I want. I want "query=>{"job.*": null}".
Signed-off-by: Wu Zhende wuzhende666@163.com
lib/monitor.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/monitor.rb b/lib/monitor.rb index 56283e10..67c2389a 100755 --- a/lib/monitor.rb +++ b/lib/monitor.rb @@ -51,7 +51,7 @@ class Monitor def merge_overrides return if @overrides.empty?
- revise_hash(@query, @overrides, true)
@query.merge!(@overrides) end
def field_check
-- 2.23.0
-
Cao Xueliang -
Wu Zhende