Ticket 10686

Summary: sacct parsable output fields are not quoted
Product: Slurm Reporter: Greg Wickham <greg.wickham>
Component: AccountingAssignee: Unassigned Developer <dev-unassigned>
Status: OPEN --- QA Contact:
Severity: 5 - Enhancement    
Priority: ---    
Version: 20.02.2   
Hardware: Linux   
OS: Linux   
Site: KAUST Alineos Sites: ---
Atos/Eviden Sites: --- Confidential Site: ---
Coreweave sites: --- Cray Sites: ---
DS9 clusters: --- HPCnow Sites: ---
HPE Sites: --- IBM Sites: ---
NOAA SIte: --- NoveTech Sites: ---
Nvidia HWinf-CS Sites: --- OCF Sites: ---
Recursion Pharma Sites: --- SFW Sites: ---
SNIC sites: --- Tzag Elita Sites: ---
Linux Distro: --- Machine Name:
CLE Version: Version Fixed:
Target Release: --- DevPrio: ---
Emory-Cloud Sites: ---

Description Greg Wickham 2021-01-25 04:22:01 MST 
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
Comment 1 Tim Wickberg 2021-01-25 17:45:27 MST 
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
Comment 2 Greg Wickham 2021-01-26 04:41:23 MST 
I've learnt something new today . . off to look at slurmrestd