If data is fairly complicated, it makes sense to build your own parsing rules in the Flow to cleanse the data.
chris
> --
> You received this message because you are subscribed to the Google Groups "cascading-user" group.
> To post to this group, send email to cascadi...@googlegroups.com.
> To unsubscribe from this group, send email to cascading-use...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/cascading-user?hl=en.
>
--
Chris K Wensel
ch...@concurrentinc.com
http://concurrentinc.com
--
You received this message because you are subscribed to the Google Groups "cascading-user" group.
To post to this group, send email to cascadi...@googlegroups.com.
To unsubscribe from this group, send email to cascading-use...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/cascading-user?hl=en.
Kendo you know if its faster than TextDelimited by any margin?
I'm unlikely to add any more edge cases to the current regex (see below), so I need more time to evaluate the impact of the change.
chris
> For more options, visit this group at http://groups.google.com/group/cascading-user?hl=en.
It would be wonderful if you packaged that up and put it on the conjars.org maven repo, i'll then link to it from the .org site.
Or just stick it in github and I can link it.
chris
> For more options, visit this group at http://groups.google.com/group/cascading-user?hl=en.