Another option (for Beam) was passing a custom content handler via the
serialized lambda expression - which sounds like a black magic to ne at
the moment but I'm curious :-)
I thought, assuming TikaConfig is only used once to bootstrap, then
passing a ContentHandler class name might work. You are right, the
headers are better suited for the dynamic cases...
On 28/09/17 22:35, Chris Mattmann wrote: