-
Notifications
You must be signed in to change notification settings - Fork 66
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
Rename function and class containing from_json
#2327
Conversation
Signed-off-by: Nghia Truong <nghiat@nvidia.com>
Signed-off-by: Nghia Truong <nghiat@nvidia.com>
Signed-off-by: Nghia Truong <nghiat@nvidia.com>
Signed-off-by: Nghia Truong <nghiat@nvidia.com>
build |
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.
The change looks fine. My main concern is that we are going to break the plugin. Could you please keep MapUtils.java with the extractRawMapFromJsonString
but have it call into JSONUtils.java's extractRawMapFromJsonString
? But because of how the plugin works we cannot deprecate the MapUtils API. But we can delete it as soon as the plugin is updated to use the new API.
build |
That sounds good. Now we have |
This includes a few changes for
from_json
function:from_json
intofrom_json_to_raw_map
, since the current implementation is not a full-featurefrom_json
.MapUtils
intoJSONUtils
, since JSON is more relevant than map.Moving away from
Map*
intoJSON*
is necessary for further development offrom_json
to support more output data types other than just map.To avoid breaking changes in the Spark plugin, the function
MapUtils#extractRawMapFromJsonString
is redirected toJSONUtils#extractRawMapFromJsonString
. The entire classMapUtils
will be removed in the follow up work.