*emphasized text*i was defining a macro search
writing the search each pipe in one line like:
xxxx
|aaa
|bbb
|ccc
it failed to work.
but when i put them all in one line: xxxx|aaa|bbb|ccc, it worked
the error information was:
"Error in 'eval' command: Failed to parse the provided arguments. Usage: eval dest_key = expression"
i tried to locate the problem, maybe a subsearch caused this error:
xxxx
|eval [search xxx
|return i]
|xxxx
which writing in one line will result as "xxxx|eval i=something|xxxx"
but "i" was not actually returned in multi-line mode.
is that bug? or macro search is not suggested to multiline way?
There is a bug in the macro when it is saved in the config file, unable to handle the linebreak char after a function. Go oneliner or finish the line with a pipe.
There is a bug in the macro when it is saved in the config file, unable to handle the linebreak char after a function. Go oneliner or finish the line with a pipe.
This is planned to be fixed in next patch version (likely 6.0.1 and 5.0.6). See SPL-72399 in the changelog once released for details.
Is this bug ever going to be fixed?
I have some very complex macros that are much easier to read and edit when they are split over multiple lines?
Edit: I tried the finish each line with a pipe but that didnt seem to work.
Thank you.
by the way, "xxx|bucket _time span=30m|xxx" works well in oneline, but goes wrong in multi lines, unless change it a little: "xxx|bucket span=30m _time|xxx"