Uh oh!
There was an error while loading. Please reload this page.
Siddharthvipul/parsers - #38
Conversation
siddharthvipul
commented
Jun 4, 2018
- empty directories (holders) for other tools
- add smallfile parser
- add sample output of smallfile (read and write)
- add sample output of the parser
| log to stderr? : False | ||
| ext.attr.size : 0 | ||
| ext.attr.count : 0 | ||
| host = dhcp37-55.lab.eng.blr.redhat.com,thr = 00,elapsed = 22.428904,files = 1000,records = 1000,status = ok |
There was a problem hiding this comment.
Remove all references to internal IPs in public code.
| @@ -0,0 +1,84 @@ | |||
| #!/usr/bin/python3 | |||
There was a problem hiding this comment.
make parsers a python module and fix names appropriately.
| attr = [] | ||
| with open(file_name) as fobj: | ||
| data_file = fobj.read().split("\n") | ||
| for line in data_file: |
There was a problem hiding this comment.
Have you looked at whether smallfile already outputs CSV and if you can use that instead?
There was a problem hiding this comment.
With th option --output-json smallfile will output JSON data, this maybe more useful from a parsing standpoint.
smallfile does output csv, but that is more for when we give --response-times option, and records response times for each operation. Noting that here. Also, we possibly do not need that.
I would prefer parsing JSON in this case, rather than CLI output.