You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 22, 2019. It is now read-only.
As an alternative to throwing exception on encountering unknown/extra column values; or for just ignorign them, it would be good to be able to simply assign them dynamically generated name like "unknown1", "unknown2" and so on.
Name should be templatizable using String.format(...) with 1-based index; for example to get name mentioned above, one could define template as unknown%d. It would also be legal to specify un-templatized name (no %), which would just use same name; this may or may not work for data-binding, but could be useful when using Streaming API directly.
Configuration should be done by one of:
Specify feature and template via CsvFactory, as baseline to use for all CsvParsers
Specify feature and template on individual CsvParser instances (replaces whatever default was used)
(if supported by ObjectReader/future CsvReader -- separate work items) Allow per-call override via CsvReader instance, to be passed as an override for CsvParser constructed.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As an alternative to throwing exception on encountering unknown/extra column values; or for just ignorign them, it would be good to be able to simply assign them dynamically generated name like "unknown1", "unknown2" and so on.
Name should be templatizable using
String.format(...)
with 1-based index; for example to get name mentioned above, one could define template asunknown%d
. It would also be legal to specify un-templatized name (no%
), which would just use same name; this may or may not work for data-binding, but could be useful when using Streaming API directly.Configuration should be done by one of:
CsvFactory
, as baseline to use for allCsvParser
sCsvParser
instances (replaces whatever default was used)ObjectReader
/futureCsvReader
-- separate work items) Allow per-call override viaCsvReader
instance, to be passed as an override forCsvParser
constructed.The text was updated successfully, but these errors were encountered: