Corrected abnormal conversion of Livy SQL interpreters string display.
What is this PR for?
When performing SQL queries using Livy interpreters, the strings returned by Livy are transformed by the Livy interpreters. This transformation can be disastrous for ETL processes because without seeing the data in its original form, it becomes difficult to handle the data properly.
What type of PR is it?
Improvement
Todos
- [ ] - Task
What is the Jira issue?
- Open an issue on Jira https://issues.apache.org/jira/browse/ZEPPELIN/
- Put link here, and add [ZEPPELIN-Jira number] in PR title, eg. [ZEPPELIN-533]
How should this be tested?
- Strongly recommended: add automated unit tests for any new or changed behavior
- Outline any manual steps to test the PR here.
Screenshots (if appropriate)
Questions:
- Does the license files need to update? N
- Is there breaking changes for older versions? N
- Does this needs documentation? N
cc @pan3793
Sorry, I don't have the power to approve the CI workflow.
For the case you mentioned, what's the output for
- spark-shell
- spark-sql
- Zeppelin Livy interpreter with
zeppelin.livy.tableWithUTFCharacterenabled - Zeppelin Livy interpreter before/after your patch
cc @jongyoul
@myongyun I'm also a bit worried about the purpose of the original code.
@zhangxiaoping I think you're the original author. Could you please check it?
cc/ @zjffdu Could you also please check the logic?
This pull request has been inactive for over a year. If no further activity occurs within the next 30 days, it will be automatically closed. If you believe this PR is still relevant, please feel free to leave a comment or make an update. Thank you!
This pull request has been automatically closed due to prolonged inactivity (over one year without updates). If you feel this was done in error or would like to continue the discussion, feel free to reopen it. Thank you for your contributions!