The underlying CSV library only supports a single-character delimiter,
so it would be a bit of work to allow multi-char delimiters. Another
solution is to use | as your delimiter and simply account for that in
your file header. Everything is mapped by name, so you'd just have a
bunch of columns named "" and it should work fine otherwise.
That may not work if your delimiter is || because you might have | in
your data, though. If that's the case, then I'd go with the suggestion
from Joe to replace "||" with a single-character delimiter that you
won't see in the data, like ☃.
rb
On 02/04/2016 06:50 AM, Joe Witt wrote:
Not a direct answer but:
With NIFI-210 arriving in the upcoming NiFi 0.5.0 release you will
have a great option in scripting (Lua, Python, Ruby, Groovy,
Javascript) that will let you rapidly get past these hurdles without
having to build your own custom processor until you are sure what you
need.
Thanks
Joe
On Thu, Feb 4, 2016 at 6:48 AM, Tony Kurc <[email protected]> wrote:
With that processor alone it doesn't appear so. The validator for that
property requires it to be one character.
On Feb 3, 2016 1:01 AM, "shweta" <[email protected]> wrote:
Hi All,
It seems "ConvertCSVtoAvro" only support single character as delimiter in
Nifi. Is there a way to specify "||"
delimiter.
Thanks,
Shweta
--
View this message in context:
http://apache-nifi-developer-list.39713.n7.nabble.com/ConvertCSVtoAvro-support-for-delimiter-tp7116.html
Sent from the Apache NiFi Developer List mailing list archive at
Nabble.com.
--
Ryan Blue
Software Engineer
Cloudera, Inc.
