Having a default ParseSpec implementation is bad for users, because it masks problems specifying the format. Two common problems masked by this are specifying the "format" at the wrong level of the JSON, and specifying a format that Druid doesn't support. In both cases, having a default implementation means that users will get the delimited parser rather than an error, and then be confused when, later on, their data failed to parse.
Marked release notes since this is a user visible behavior change. Someone relying on the above behaviors would need to start specifying "delimited" explicitly. [ Full content available at: https://github.com/apache/incubator-druid/pull/6310 ] This message was relayed via gitbox.apache.org for [email protected]
