-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parse JSON into org.embulk.spi.json.JsonValue, not org.msgpack.value.Value #8
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM👍 (Please check the one comment)
if (task.getFlattenJsonArray()) { | ||
if (!value.isArrayValue()) { | ||
if (!value.isJsonArray()) { | ||
throw new JsonRecordValidateException( | ||
String.format( | ||
"A Json record must represent array value with '__experimental__flatten_json_array' option, but it's %s", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Offtopic: __experimental__flatten_json_array
-> flatten_json_array
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your good catch! Exactly. Fixed it in: b8039b4
Thanks! |
As commented in
embulk-util-json
, we are going to releaseembulk-parser-json:0.11.1
just with dropping use oforg.msgpack.value.Value
, but without one-path parsing.This pull request includes :
JsonParser
to newJsonValueParser
, with replacing use oforg.msgpack.value.Value
toorg.embulk.spi.json.JsonValue
org.embulk.spi.json.JsonValue
, withoutorg.msgpack.value.Value
Each step is tested as an independent commit on CI.
embulk-parser-json:0.11.1
would be released with this, and also Embulk v0.11.1.