JDBC generic interpreter #608
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…into jdbc_interpreter
Contributor
Author
|
Hi @jongyoul, tested:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is this PR for?
JDBC generic interpreter based on PostgresInterpreter (@tzolov)
What type of PR is it?
Feature
Is there a relevant Jira issue?
How should this be tested?
In the file zeppelin-daemon.sh add:
ZEPPELIN_CLASSPATH+=":${ZEPPELIN_HOME}/jdbc/jars/jdbc jar"
add interpreter and properties. See screenshots.
Screenshots (if appropriate)
zeppelin-daemon.sh add jars
Interpreter properties (@jongyoul thanks)
for use in paragraph:
Questions:
It's finished? no,we will review it and discuss it
Does the licenses files need update? no
Is there breaking changes for older versions? no
Does this needs documentation? documentation will follow