Grant Ingersoll wrote:
If I'm understanding correctly...
What about a SinkTokenizer that is backed by a Reader/Field instead of
the current one that stores it all in a List? This is more or less the
use case for the Tee/Sink implementations, w/ the exception that we
didn't plan for the Sink
If I'm understanding correctly...
What about a SinkTokenizer that is backed by a Reader/Field instead of
the current one that stores it all in a List? This is more or less
the use case for the Tee/Sink implementations, w/ the exception that
we didn't plan for the Sink being too large, but
Hi all,
I recently had a situation where I had to pass some metadata information
to Analyzer. This metadata was specific to a Document instance (short
story is that the analysis of some fields depended on data coming from
other fields, and the number of possible values was too big to use
sepa
