With sacct there is a '--delimiter' parameter however this requires the user knowing ahead of time which characters isn't in the returned data. While most of the output fields aren't an issue, fields with user selectable data can cause issues (specifically 'constraints' and 'jobname' spring to mind). Desired behavior: any presence of the delimiter in the data fields is quoted
Hey Greg - I don't have an immediate plan to change this - any adjustment to the output formats is fraught with peril - and our focus has pivoted to making this data easier to consume through REST, or possibly providing the same json/yaml output formats directly through the other CLI tools. I'll leave this as an open enhancement, but short of broader interest - or community submitted patch - I'd rather focus our attention elsewhere at the moment. - Tim
I've learnt something new today . . off to look at slurmrestd