Code: Select all
|.|Custom Delimiters
Moderators: chulett, rschirm, roy
Custom Delimiters
I get a few log files which have delimiters like
Is there a simple way of parsing the records, or do we have to go to the regular expression route?
Narasimha Kade
Finding answers is simple, all you need to do is come up with the correct questions.
Finding answers is simple, all you need to do is come up with the correct questions.
If you mean column delimiter, then you could try using the pipe '|' character as the delimiter, and ignore the columns with just the decimals. Treat them as marker fields, just ignore them.
Kenneth Bland
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
Nothing inherent to the Sequential File stage. Off the top of my head, you may be able to leverage the Filter option with perhaps 'tr' or some other command to translate your 'multiple character delimiter' into a single character. 
Or go old school and bring in the record as one long string and then use something like Field to bust it up. I'm not saying that the Field command supports multi-character delimiters, I've never had to deal with anything like that, but it would be interesting to investigate the possibility.
Probably best to stick with Ken's approach, it seems the most... straight-forward.
Or go old school and bring in the record as one long string and then use something like Field to bust it up. I'm not saying that the Field command supports multi-character delimiters, I've never had to deal with anything like that, but it would be interesting to investigate the possibility.
Probably best to stick with Ken's approach, it seems the most... straight-forward.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Your right Craig, Ken's approach does give me the desired results.
I was looking into other possibilities, like - works perfectly on the OS level, but it complains when I put it in the Filter Command.
I was looking into other possibilities, like -
Code: Select all
sed -e 's/|.|/|/g'Narasimha Kade
Finding answers is simple, all you need to do is come up with the correct questions.
Finding answers is simple, all you need to do is come up with the correct questions.
I get the error
Code: Select all
LogFile..Copy_of_Sequential_File_0.DSLink3: ds_seqopen() - Error in filter command "/usr/bin/sed -e 's/" -
sed: Function s/ cannot be parsed.
LogFile..Copy_of_Sequential_File_0.DSLink3: DSD.SEQOpen GCI $DS.SEQOPEN error 11.Narasimha Kade
Finding answers is simple, all you need to do is come up with the correct questions.
Finding answers is simple, all you need to do is come up with the correct questions.
