Is it safe to choose "string" as a default type with Avro? I'm trudging
through some really dirty data right now and that seems to behave fine when
I I do something like this:
Flowfile content:
{
"x": 1
}
Avro field definition:
{ "name": "x", "type": ["null", "string"] }
Where sometimes X is an int and others it's a string (don't ask me why, I
didn't set up ETL on this data).
I did a simple flow that did just this and it **seemed** to work great, but
I thought I'd get a second opinion before spending my client's time
building something big around it.
Thanks,
Mike
